Comment 19 for bug 1315575
Revision history for this message
| rob loranger (robjloranger) wrote Re: poor wireless connection with current kernel | #19 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
here is a quick example pinging my router:
64 bytes from 192.168.0.1: icmp_seq=65 ttl=64 time=1.26 ms
64 bytes from 192.168.0.1: icmp_seq=66 ttl=64 time=1.24 ms
64 bytes from 192.168.0.1: icmp_seq=67 ttl=64 time=1.27 ms
64 bytes from 192.168.0.1: icmp_seq=68 ttl=64 time=1.24 ms
64 bytes from 192.168.0.1: icmp_seq=69 ttl=64 time=1.24 ms
64 bytes from 192.168.0.1: icmp_seq=70 ttl=64 time=1488 ms
64 bytes from 192.168.0.1: icmp_seq=71 ttl=64 time=2701 ms
64 bytes from 192.168.0.1: icmp_seq=72 ttl=64 time=1701 ms
64 bytes from 192.168.0.1: icmp_seq=73 ttl=64 time=701 ms
64 bytes from 192.168.0.1: icmp_seq=74 ttl=64 time=1.17 ms
64 bytes from 192.168.0.1: icmp_seq=75 ttl=64 time=1.23 ms
64 bytes from 192.168.0.1: icmp_seq=76 ttl=64 time=1.25 ms
64 bytes from 192.168.0.1: icmp_seq=77 ttl=64 time=1.33 ms
64 bytes from 192.168.0.1: icmp_seq=78 ttl=64 time=1.25 ms
64 bytes from 192.168.0.1: icmp_seq=79 ttl=64 time=1.25 ms
~~
64 bytes from 192.168.0.1: icmp_seq=186 ttl=64 time=1.25 ms
64 bytes from 192.168.0.1: icmp_seq=187 ttl=64 time=1.27 ms
64 bytes from 192.168.0.1: icmp_seq=188 ttl=64 time=1.25 ms
64 bytes from 192.168.0.1: icmp_seq=189 ttl=64 time=1.25 ms
64 bytes from 192.168.0.1: icmp_seq=190 ttl=64 time=2016 ms
64 bytes from 192.168.0.1: icmp_seq=191 ttl=64 time=1009 ms
64 bytes from 192.168.0.1: icmp_seq=192 ttl=64 time=1.69 ms
64 bytes from 192.168.0.1: icmp_seq=193 ttl=64 time=1.25 ms
64 bytes from 192.168.0.1: icmp_seq=194 ttl=64 time=1.25 ms
64 bytes from 192.168.0.1: icmp_seq=195 ttl=64 time=2.59 ms
64 bytes from 192.168.0.1: icmp_seq=196 ttl=64 time=1.13 ms
64 bytes from 192.168.0.1: icmp_seq=197 ttl=64 time=1.24 ms
It seems to occur in fairly regular cycles.