search

google-code-export / openeve

Automatically exported from code.google.com/p/openeve
0 stars 1 forks source link

Extremely high wifi ping times to device (experimental) #165

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. ping from a remote system to the device
2. notice that the wifi connection has significant latency

PING 192.168.1.70 (192.168.1.70) 56(84) bytes of data.
64 bytes from 192.168.1.70: icmp_req=1 ttl=64 time=889 ms
64 bytes from 192.168.1.70: icmp_req=2 ttl=64 time=11.3 ms
64 bytes from 192.168.1.70: icmp_req=3 ttl=64 time=213 ms
64 bytes from 192.168.1.70: icmp_req=4 ttl=64 time=38.7 ms
64 bytes from 192.168.1.70: icmp_req=5 ttl=64 time=361 ms
64 bytes from 192.168.1.70: icmp_req=6 ttl=64 time=384 ms
64 bytes from 192.168.1.70: icmp_req=7 ttl=64 time=301 ms
64 bytes from 192.168.1.70: icmp_req=8 ttl=64 time=227 ms
64 bytes from 192.168.1.70: icmp_req=9 ttl=64 time=454 ms
64 bytes from 192.168.1.70: icmp_req=10 ttl=64 time=376 ms

(wifi is currently even a bigger problem, it just stopped working on the device 
itself...)

Original issue reported on code.google.com by ste...@konink.de on 4 Sep 2011 at 9:01

GoogleCodeExporter commented 9 years ago 
Did some more investigation. Although external to internal result in high 
times. Pings from the device, are moderately normal.

64 bytes from 192.168.1.254: icmp_seq=382 ttl=64 time=25.6 ms
64 bytes from 192.168.1.254: icmp_seq=383 ttl=64 time=8.18 ms
64 bytes from 192.168.1.254: icmp_seq=384 ttl=64 time=11.6 ms
64 bytes from 192.168.1.254: icmp_seq=385 ttl=64 time=6.26 ms
64 bytes from 192.168.1.254: icmp_seq=386 ttl=64 time=8.52 ms
64 bytes from 192.168.1.254: icmp_seq=387 ttl=64 time=175 ms
64 bytes from 192.168.1.254: icmp_seq=388 ttl=64 time=91.7 ms
64 bytes from 192.168.1.254: icmp_seq=389 ttl=64 time=3.87 ms
64 bytes from 192.168.1.254: icmp_seq=390 ttl=64 time=8.13 ms

I got my wifi to work again to reducing the txpower. But this doesn't affect 
the external to internal ping time.

Original comment by ste...@konink.de on 4 Sep 2011 at 9:28

GoogleCodeExporter commented 9 years ago 
This is mine. Wifi is work perfectly for me.

PING 192.168.10.7 (192.168.10.7) 56(84) bytes of data.
64 bytes from 192.168.10.7: icmp_req=3 ttl=64 time=12.2 ms
64 bytes from 192.168.10.7: icmp_req=4 ttl=64 time=10.0 ms
64 bytes from 192.168.10.7: icmp_req=5 ttl=64 time=92.3 ms
64 bytes from 192.168.10.7: icmp_req=6 ttl=64 time=2.16 ms
64 bytes from 192.168.10.7: icmp_req=7 ttl=64 time=10.3 ms
64 bytes from 192.168.10.7: icmp_req=8 ttl=64 time=2.60 ms
64 bytes from 192.168.10.7: icmp_req=9 ttl=64 time=88.6 ms
64 bytes from 192.168.10.7: icmp_req=10 ttl=64 time=114 ms
64 bytes from 192.168.10.7: icmp_req=11 ttl=64 time=31.1 ms
64 bytes from 192.168.10.7: icmp_req=12 ttl=64 time=56.6 ms
64 bytes from 192.168.10.7: icmp_req=13 ttl=64 time=78.5 ms
64 bytes from 192.168.10.7: icmp_req=14 ttl=64 time=100 ms
64 bytes from 192.168.10.7: icmp_req=15 ttl=64 time=128 ms
64 bytes from 192.168.10.7: icmp_req=16 ttl=64 time=40.3 ms
64 bytes from 192.168.10.7: icmp_req=17 ttl=64 time=63.3 ms
64 bytes from 192.168.10.7: icmp_req=18 ttl=64 time=85.3 ms
64 bytes from 192.168.10.7: icmp_req=19 ttl=64 time=100 ms
64 bytes from 192.168.10.7: icmp_req=20 ttl=64 time=31.8 ms

Original comment by wkp...@gmail.com on 4 Sep 2011 at 9:29

GoogleCodeExporter commented 9 years ago

Original comment by wkp...@gmail.com on 4 Sep 2011 at 10:17