I can confirm the latency problem. Here is a sample ping:
PING web.de (217.72.195.42) 56(84) bytes of data.
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=1 ttl=248 time=1006 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=2 ttl=248 time=81.1 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=3 ttl=248 time=1010 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=4 ttl=248 time=82.9 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=5 ttl=248 time=1008 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=6 ttl=248 time=82.3 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=7 ttl=248 time=1006 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=8 ttl=248 time=81.1 ms
I can confirm the latency problem. Here is a sample ping:
PING web.de (217.72.195.42) 56(84) bytes of data.
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=1 ttl=248 time=1006 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=2 ttl=248 time=81.1 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=3 ttl=248 time=1010 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=4 ttl=248 time=82.9 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=5 ttl=248 time=1008 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=6 ttl=248 time=82.3 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=7 ttl=248 time=1006 ms
64 bytes from ha-42.web.de (217.72.195.42): icmp_seq=8 ttl=248 time=81.1 ms
--- web.de ping statistics --- 544.866/ 1010.397/ 462.961 ms, pipe 2
8 packets transmitted, 8 received, 0% packet loss, time 7068ms
rtt min/avg/max/mdev = 81.143/
I'm running 2.6.15-23-686.
Why is the status of the bug still "unconfirmed"?