Comment 22 for bug 103210

More information on the latency bug - it seems clear after more use that the issue is one of latency on each initial connection.

Each connection is fine once it is established but there is some 2-20 second delay in initiated the connection (or even getting a ping back).

For example, on a system connected physically to the ethernet:
ski@deskaheh:~$ time sudo ping -f -c 10 google.com
PING google.com (64.233.187.99) 56(84) bytes of data.

--- google.com ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 119ms
rtt min/avg/max/mdev = 57.694/67.463/95.618/11.344 ms, pipe 6, ipg/ewma 13.309/67.140 ms

real 0m0.200s
user 0m0.000s
sys 0m0.004s

But on a system connected via ipw3945 (and affected by the bug):

ski@ganiodayo:~$ time sudo ping -f -c 10 google.com
PING google.com (72.14.207.99) 56(84) bytes of data.

--- google.com ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 30423ms
rtt min/avg/max/mdev = 52.250/68.772/92.240/11.990 ms, pipe 6, ipg/ewma 3380.390/72.389 ms

real 0m55.716s
user 0m0.004s
sys 0m0.008s

What's more, ping cannot be interrupted via control-C on the affected system.

However, thruput is fine (circa 2.2MBps).