-
Notifications
You must be signed in to change notification settings - Fork 244
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Cannot connect to hidden network #4438
Comments
Hello, are you sure that this is due to the wi-fi being hidden? We have some users reporting not being able to connect for temaple to 2PA2/3 mode wi-fis (#3908). |
The network has a hidden ssid, meaning it doesn't broadcast anything unless it gets the credentials including the name before hand. Also I'm pretty sure we use different wifi modules, than temaple |
I know what a hidden SSID is. I was just asking a question whether it would connect to that wi-fi even if the SSID was not hidden. |
My MK4 has FW 6.2.0-RC1+8787 |
All right, so it's not like our printers don't work on hidden networks in general. Thanks for checking this @3d-gussner |
I think I may have found the problem, the wifi we have is only 5ghz, and the printer's wifi module only works at 2.4ghz. I'll figure out if I can use a different module, but if that doesn't work, it's not the firmware's fault. I will close this issue with this comment |
Printer model
MK4, XL, probably MK4S
Firmware version
Latest stable build
Upgrades and modifications
No response
Printing from...
USB, want prusalink/prusa connect
Describe the bug
I am at a school that has pretty heavy network restrictions (and signin restricions), however the robotics lab has a hidden network that has no restrictions. Our prusas will not seem to connect to the hidden network, and the internet. I am not sure if this is a bug or a missing feature. Also as extra info the network name has only numbers.
How to reproduce
Expected behavior
Connect to the internnet
Files
wifi config.ini.zip
If I get time, I'll dump the network config too.
The text was updated successfully, but these errors were encountered: