Strange set of Duet Wifi connection issues cant wrap head around
-
@dhmclean Have you tried just using the fixed IP address from your iOS or Android device, instead of using the name of the Duet? Is your Windows device connected by WiFi to the router?
-
Can you test the Duet in Access Point mode where it creates an SSID of it's own that you connect to with your device?
https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m589-configure-access-point-parameters
-
@markz I do use the IP address rather than name. One Windows device is connected by WiFi the other is not, but both can connect no problem. I will try switching back and forth on my desktop machine between WiFi and Ethernet to see if that makes any difference.
-
@Phaedrux I tried before I updated all my firmware from RRF 2 and it made no difference, but I will try it again now that I am on RRF 3.
-
@dhmclean Given your symptoms I think the odds of it being your Duet are vanishingly small and it's almost certainly the router.
-
@markz It does seem like that, but out of the 32 clients connected to the router this is the only one I haven't been able to get working correctly with regards to things like port forwarding , firewalls, DHCP Manual IP reserves etc. so I guess I just need to know what to do with my router for the Duet to get it to work? It is almost like the issue when you upload a large file when the WiFi stops responding, except I checked the SD card cluster size (it's 64kb) and 512 byte sectors. So I thought that it was going to be the card, because that sounded exactly like that behavior, everything works great for a time after a reboot, but SOMETHING causes SOMETHING to limit connectivity to the Duet on mobile first.
-
@Phaedrux said in Strange set of Duet Wifi connection issues cant wrap head around:
Can you test the Duet in Access Point mode where it creates an SSID of it's own that you connect to with your device?
https://docs.duet3d.com/en/User_manual/Reference/Gcodes#m589-configure-access-point-parameters
Have you tested this yet?
-
@dhmclean the apparent symptoms->
a) Everything works fine after a router reboot. This removes most of the possible causes since at one point in time things are perfect.
b) Over time the android/ios devices - only - stop being able to find the Duet by IP address. (Did you mean iPad there?)
c) During that same time frame the Windows WiFi and hardwired devices still find the Duet by IP address.I'm not sure what you mean by 'can't find' but assume that means you can't even ping the IP address.
I have five Asus routers running here and the ones running the latest firmware require occasional reboots. iOS, in particular, stops connecting reliably to the WiFi while Android rarely fails. iOS messages "Unable to Join Network" randomly.
But, you should definitely try what @Phaedrux suggested using AP to test. It could be a network problem.
And, to be clear, you've made sure that your DHCP server fixed address range doesn't conflict with your DHCP grant range so it isn't serving the Duet IP address to someone else during the day.
-
@markz said in Strange set of Duet Wifi connection issues cant wrap head around:
I have five Asus routers running here and the ones running the latest firmware require occasional reboots. iOS, in particular, stops connecting reliably to the WiFi while Android rarely fails. iOS messages "Unable to Join Network" randomly.
So your Asus routers with the latest firmware are the most troublesome?
But, you should definitely try what @Phaedrux suggested using AP to test. It could be a network problem.
I will try this again
And, to be clear, you've made sure that your DHCP server fixed address range doesn't conflict with your DHCP grant range so it isn't serving the Duet IP address to someone else during the day.
I have ensured this is the case. Thank you for these suggestions, I will try these things in the next couple of days.
-
@dhmclean Yes, I have two older Asus routers that run 24/7 for months whereas my latest 3 (two mesh and one standard set into the mesh) flake over time fairly consistently. Admittedly the older firmware was comparatively basic.
