WiFi Unreliable
-
@stuartofmt here's the results of that test:
destinybonavita@MacBook-Pro ~ % traceroute 10.0.0.201 traceroute to 10.0.0.201 (10.0.0.201), 64 hops max, 52 byte packets 1 10.0.0.201 (10.0.0.201) 8.712 ms 13.885 ms 5.475 ms destinybonavita@MacBook-Pro ~ % ping 10.0.0.201 PING 10.0.0.201 (10.0.0.201): 56 data bytes 64 bytes from 10.0.0.201: icmp_seq=0 ttl=255 time=13.169 ms 64 bytes from 10.0.0.201: icmp_seq=1 ttl=255 time=11.783 ms 64 bytes from 10.0.0.201: icmp_seq=2 ttl=255 time=34.763 ms 64 bytes from 10.0.0.201: icmp_seq=3 ttl=255 time=6.772 ms 64 bytes from 10.0.0.201: icmp_seq=4 ttl=255 time=51.055 ms 64 bytes from 10.0.0.201: icmp_seq=5 ttl=255 time=9.359 ms 64 bytes from 10.0.0.201: icmp_seq=6 ttl=255 time=12.984 ms 64 bytes from 10.0.0.201: icmp_seq=7 ttl=255 time=8.528 ms 64 bytes from 10.0.0.201: icmp_seq=8 ttl=255 time=23.638 ms Request timeout for icmp_seq 9 64 bytes from 10.0.0.201: icmp_seq=10 ttl=255 time=15.351 ms 64 bytes from 10.0.0.201: icmp_seq=11 ttl=255 time=18.995 ms Request timeout for icmp_seq 12 64 bytes from 10.0.0.201: icmp_seq=13 ttl=255 time=34.696 ms 64 bytes from 10.0.0.201: icmp_seq=14 ttl=255 time=52.520 ms 64 bytes from 10.0.0.201: icmp_seq=15 ttl=255 time=4.912 ms 64 bytes from 10.0.0.201: icmp_seq=16 ttl=255 time=21.125 ms 64 bytes from 10.0.0.201: icmp_seq=17 ttl=255 time=13.998 ms 64 bytes from 10.0.0.201: icmp_seq=18 ttl=255 time=36.809 ms ^C --- 10.0.0.201 ping statistics --- 19 packets transmitted, 17 packets received, 10.5% packet loss round-trip min/avg/max/stddev = 4.912/21.792/52.520/14.487 ms -
@dessiverse said in WiFi Unreliable:
here's the results of that test
Don't like the timeouts on a LAN ... What happens when you ping the router ? Do you see time out's occurring there ?
-
@stuartofmt nope
destinybonavita@MacBook-Pro ~ % ping 10.0.0.1 PING 10.0.0.1 (10.0.0.1): 56 data bytes 64 bytes from 10.0.0.1: icmp_seq=0 ttl=64 time=5.392 ms 64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=7.069 ms 64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=4.732 ms 64 bytes from 10.0.0.1: icmp_seq=3 ttl=64 time=5.586 ms 64 bytes from 10.0.0.1: icmp_seq=4 ttl=64 time=4.150 ms 64 bytes from 10.0.0.1: icmp_seq=5 ttl=64 time=3.499 ms 64 bytes from 10.0.0.1: icmp_seq=6 ttl=64 time=4.984 ms 64 bytes from 10.0.0.1: icmp_seq=7 ttl=64 time=10.994 ms 64 bytes from 10.0.0.1: icmp_seq=8 ttl=64 time=10.078 ms 64 bytes from 10.0.0.1: icmp_seq=9 ttl=64 time=1.937 ms 64 bytes from 10.0.0.1: icmp_seq=10 ttl=64 time=3.131 ms 64 bytes from 10.0.0.1: icmp_seq=11 ttl=64 time=3.873 ms 64 bytes from 10.0.0.1: icmp_seq=12 ttl=64 time=11.292 ms 64 bytes from 10.0.0.1: icmp_seq=13 ttl=64 time=5.367 ms 64 bytes from 10.0.0.1: icmp_seq=14 ttl=64 time=4.908 ms 64 bytes from 10.0.0.1: icmp_seq=15 ttl=64 time=10.782 ms 64 bytes from 10.0.0.1: icmp_seq=16 ttl=64 time=4.683 ms 64 bytes from 10.0.0.1: icmp_seq=17 ttl=64 time=2.373 ms 64 bytes from 10.0.0.1: icmp_seq=18 ttl=64 time=2.985 ms 64 bytes from 10.0.0.1: icmp_seq=19 ttl=64 time=2.831 ms 64 bytes from 10.0.0.1: icmp_seq=20 ttl=64 time=4.145 ms 64 bytes from 10.0.0.1: icmp_seq=21 ttl=64 time=5.388 ms 64 bytes from 10.0.0.1: icmp_seq=22 ttl=64 time=12.284 ms 64 bytes from 10.0.0.1: icmp_seq=23 ttl=64 time=5.878 ms 64 bytes from 10.0.0.1: icmp_seq=24 ttl=64 time=9.148 ms 64 bytes from 10.0.0.1: icmp_seq=25 ttl=64 time=10.261 ms ^C --- 10.0.0.1 ping statistics --- 26 packets transmitted, 26 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 1.937/6.067/12.284/3.055 ms destinybonavita@MacBook-Pro ~ % -
Do you have access to any xfinity router config pages?
Can you contact the ISP for some support?
Do you have a separate router you can setup as an access point to test with? -
@phaedrux I have access to the config pages. If I contact the ISP they'll definitely say it's a problem with this device since everything else on the network runs flawlessly.
-
Is it creating a separate 2.4ghz network SSID or are they combined?
Do you see any options for band steering or whatever name they give it which tries to shunt devices to the 5ghz network? -
@phaedrux said in WiFi Unreliable:
band steering
I have the setting for this. It’s also one combined SSID for 2.4 and 5 due to the extenders.
-
I would try setting up a separate 2.4ghz SSID with the router itself, no extender, and just see if the performance is better. Try and isolate where the issue lies.
-
@dessiverse said in WiFi Unreliable:
@stuartofmt nope
Ok - so it may have something to do with the Duet itself.
The only thing I can suggest at this stage, network-wise, is to eliminate variables. Getting the Duet and the machine that you wish to download from directly connected to the router (i.e. no repeater in the picture) would be a good start.
P.S. the results you got from the M122 P104 test look almost exactly the same as on my Duet2 Wifi. Downloading a gcode file that is 25MB takes about a minute, the same if I upload it from Prusa Slicer. The .dummy test seems about 10 sec quicker for the same file.
-
@phaedrux I originally had it like that and it was the same. I changed it a few days after.
-
@stuartofmt I had this issue before I got the repeaters and when I had the networks separated. I also tried with the duet being the only one on the 2.4GHz network and had the same issue. I really think it's a problem with the duet itself.
-
@dessiverse said in WiFi Unreliable:
I really think it's a problem with the duet itself.
Yet the speeds are fine when connecting to the Duet in AP mode. It seems more an issue of the local router not playing well with the Duet.
-
@dessiverse said in WiFi Unreliable:
I really think it's a problem with the duet itself.
How about trying a file transfer using FTP? As @Phaedrux said, its strange that when configured as an AP it works well. Maybe testing as an AP and as part of the desired network and compare the results.
I'm only suggesting FTP as a way of taking the Duet Code out of the equation and gathering additional data. Again - it may tell something or nothing ... -
I put the duet right on top of one of the WiFi nodes, and now it's working fine, but if I move it a foot or two away, it stops working. It's working, but there's gotta be a hardware issue here restricting its signal. The antenna is plugged in. Is there a gcode to ensure it's being used?
-
@dessiverse have you tried using a different WiFi channel? We've noticed that the ESP module in the Duet works better on some channels than others. This may be due to interference on some channels from other 2.4GHz devices (e.g. cordless phones and leaky microwave ovens) or possibly from the Duet itself (e.g. a harmonic of one of the clock frequencies).
Duet WiFi hardware designer and firmware engineer
Please do not ask me for Duet support via PM or email, use the forum
http://www.escher3d.com, https://miscsolutions.wordpress.com -
@dc42 I'll have to try to see if I can change just the 2.4GHz channel. Is there a list of recommended channels?
-
See https://www.metageek.com/training/resources/why-channels-1-6-11.html. There are smartphone apps that can show you which channels are being used by WiFi access points already.
-
I doubt it will help at all, because you've all got a pretty solid grasp on what's going on.
My laptop and printer will repeatedly disconnect from my router when my cellphone is in the immediate area. The issues stop if I tether my phone to my laptop (weird, I know). As soon as I unplug my cell from the laptop, I almost immediately start having disconnect issues.
I am not trying to hijack this post, or look for a solution. Just suggesting to look for outside interference sources.
-
@dessiverse said in WiFi Unreliable:
I put the duet right on top of one of the WiFi nodes, and now it's working fine, but if I move it a foot or two away, it stops working. It's working,
Its sounding more and more like a router issue (just a gut feeling). In addition to @dc42 suggestion of finding a clear channel - take a look at the QoS settings in the router. If enabled (I'm suspecting they are) then try temporarily disabling. Given that the router is provided by your ISP and likely intended for use with VOIP etc. it's possible there is something there that may be throttling the LAN "streaming" speeds. I suspect this is unlikely the case - of and by itself - but may be a contributing factor, especially if the connectivity is marginal for other reasons.
-
@stuartofmt The reason why I'm very hesitant to say it's a router issue is because I have no issues communicating between any devices on the network besides the duet. The duet is the absolute only one to have any issues, so it doesn't make sense to ignore all other devices and say it's a router issue because of this one device. I do ask again, is there a gcode to check that the antenna is working as it should? Because that right there could be the issue.
EDIT: I also want to note I tried inSSIDer and saw that both my networks, 2.4 and 5GHz, are running on the most unused channels in the area. So that's probably not it either.
