attributes responses to the wrong host after a while (Debian #525431) about fping

[alexanderkjeldaas]

I am seeing this as well. When using fping on a list of 300k hosts, this basically happens for all hosts after a while.

After 50798 hosts, fping starts pinging the host from the beginning of the list and additionally messes with the loss/return statistics.

0.0.0.0 : [0], 96 bytes, 0.10 ms (0.10 avg, 0% loss) [<- 127.0.0.1]
100.0.198.71 : [0], 96 bytes, 86.8 ms (86.8 avg, 0% loss)
100.0.198.79 : [0], 96 bytes, 91.3 ms (91.3 avg, 0% loss)
100.42.208.126 : [0], 96 bytes, 158 ms (158 avg, 0% loss)
... <skipping ~50000 hosts>
188.165.20.134 : [0], 96 bytes, 17.3 ms (17.3 avg, 0% loss)
188.165.20.166 : [0], 96 bytes, 18.1 ms (18.1 avg, 0% loss)
188.165.20.177 : [0], 96 bytes, 15.9 ms (15.9 avg, 0% loss)
188.165.201.77 : [0], 96 bytes, 17.3 ms (17.3 avg, 0% loss)
188.165.202.144 : [0], 96 bytes, 15.6 ms (15.6 avg, 0% loss)
188.165.20.235 : [0], 96 bytes, 13.0 ms (13.0 avg, 0% loss)
188.165.203.141 : [0], 96 bytes, 17.4 ms (17.4 avg, 0% loss)
0.0.0.0 : [0], 96 bytes, 16.3 ms (8.22 avg, 200% return) [<- 188.165.203.148]
100.0.198.71 : [0], 96 bytes, 17.3 ms (52.0 avg, 200% return) [<- 188.165.203.157]
100.0.198.79 : [0], 96 bytes, 17.6 ms (54.5 avg, 200% return) [<- 188.165.20.38]
10.0.0.207 : [0], 96 bytes, 18.0 ms (18.0 avg, 0% loss) [<- 188.165.203.92]
10.0.0.244 : [0], 96 bytes, 17.5 ms (17.5 avg, 0% loss) [<- 188.165.204.138]
10.0.0.4 : [0], 96 bytes, 17.6 ms (17.6 avg, 0% loss) [<- 188.165.204.207]

You can see that fping gets confused about which host it is actually pinging. It seems to ping the correct host, but the 200% return and the "wrong ip" data looks wrong.

[schweikert]

#48 also reported this, but also found out that it is a integer boundary issue. An experimental fix is in the "seqmap" branch. Please test.