Comment 20 for bug 103210

I'm having this problem too.

ipw3945 is slow and unreliable to point of not being usable.

even ping is slow, and seems to be caught in some uninterruptable state as ^C doesn't kill it for a second or two. The odd thing is once a tcp connection is established, things seem more or less okay - for example, I can watch movies over sshfs just fine.

If I shell into a machine on my lan *over the wireless*, and ping normally, but while simultaneously pinging from my laptop, the difference in speed is stark. ganiodayo is my laptop, deskaheh is my desktop machine (both running gutsy amd64). note that, although the lateny reported from each packet isn't significantly different, the total elapsed time on the laptop is 4 times slower. I've tried with similar results on 2 other networks - same results.

ski@ganiodayo:/var/cache/apt/archives$ date ; ping -c 10 google.com ; date
Tue Nov 13 18:30:23 EST 2007
PING google.com (64.233.187.99) 56(84) bytes of data.
64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=1 ttl=240 time=64.7 ms
64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=2 ttl=240 time=93.2 ms
64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=3 ttl=240 time=148 ms
64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=4 ttl=240 time=59.7 ms
64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=5 ttl=240 time=60.2 ms
64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=6 ttl=240 time=59.4 ms
64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=7 ttl=240 time=80.7 ms
64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=9 ttl=240 time=117 ms
64 bytes from jc-in-f99.google.com (64.233.187.99): icmp_seq=10 ttl=240 time=89.6 ms

--- google.com ping statistics ---
10 packets transmitted, 9 received, 10% packet loss, time 41975ms
rtt min/avg/max/mdev = 59.493/85.931/148.386/28.802 ms
Tue Nov 13 18:31:15 EST 2007

ski@deskaheh:~$ date ; ping -c 10 google.com ; date
Tue Nov 13 18:30:24 EST 2007
PING google.com (72.14.207.99) 56(84) bytes of data.
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=1 ttl=242 time=221 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=2 ttl=242 time=299 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=3 ttl=242 time=46.9 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=4 ttl=242 time=56.0 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=5 ttl=242 time=52.4 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=6 ttl=242 time=384 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=7 ttl=242 time=86.9 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=8 ttl=242 time=47.5 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=9 ttl=242 time=47.7 ms
64 bytes from eh-in-f99.google.com (72.14.207.99): icmp_seq=10 ttl=242 time=52.4 ms

--- google.com ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9003ms
rtt min/avg/max/mdev = 46.998/129.559/384.575/118.986 ms
Tue Nov 13 18:30:33 EST 2007