[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(usagi-users 00534) Bug in ping6



Hi,

after receiving 1024 echo-replies from the ping target, all subsequent
echo-replies are considered as dupes, although they are absolutely
valid (and unique) replies. The ICMP sequence is incremented
correctly.

---------- snip ----------
PING xena.myipv6.de(2001:658:210:1::1) from 2001:658:210:4242:201:2ff:fe04:a7fe : 56 data bytes
...
64 bytes from 2001:658:210:1::1: icmp_seq=1022 hops=63 time=512.000 usec
64 bytes from 2001:658:210:1::1: icmp_seq=1023 hops=63 time=519.000 usec
64 bytes from 2001:658:210:1::1: icmp_seq=1024 hops=63 time=606.000 usec
64 bytes from 2001:658:210:1::1: icmp_seq=1025 hops=63 time=574.000 usec (DUP!)
64 bytes from 2001:658:210:1::1: icmp_seq=1026 hops=63 time=502.000 usec (DUP!)
64 bytes from 2001:658:210:1::1: icmp_seq=1027 hops=63 time=512.000 usec (DUP!)
...
---------- snip ----------

Tested with the ping6 from 20010514 snapshot. ping6 from RedHat
iputils-20001010-1.6x or Debian netbase 3.18-4 does not show this
behaviour.

Andreas
-- 
The number of computer scientists in a room is inversely proportional
to the number of bugs in their code.