Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DUP false positive #50

Open
rcgoodfellow opened this issue Oct 15, 2019 · 0 comments
Open

DUP false positive #50

rcgoodfellow opened this issue Oct 15, 2019 · 0 comments

Comments

@rcgoodfellow
Copy link

The following

hping3 -1 <address> -i u100

reports non-existent duplicates packets for icmp_seq=65200. This happens at exactly the point when the icmp_seq counter rolls over. This does not happen in our testing every time, but it does happen most times.

example output log

[snip]
len=28 ip=172.30.0.2 ttl=64 id=59018 icmp_seq=65198 rtt=5.8 ms
len=28 ip=172.30.0.2 ttl=64 id=59019 icmp_seq=65199 rtt=5.6 ms
len=28 ip=172.30.0.2 ttl=64 id=59020 icmp_seq=65200 rtt=5.5 ms
len=28 ip=172.30.0.2 ttl=64 id=59021 icmp_seq=65201 rtt=5.4 ms
len=28 ip=172.30.0.2 ttl=64 id=59022 icmp_seq=65202 rtt=5.3 ms
[snip]
len=28 ip=172.30.0.2 ttl=64 id=59354 icmp_seq=65534 rtt=6.9 ms
len=28 ip=172.30.0.2 ttl=64 id=59355 icmp_seq=65535 rtt=6.8 ms
DUP! len=28 ip=172.30.0.2 ttl=64 id=59356 icmp_seq=65200 rtt=45.5 ms
len=28 ip=172.30.0.2 ttl=64 id=59357 icmp_seq=1 rtt=0.0 ms
len=28 ip=172.30.0.2 ttl=64 id=59358 icmp_seq=2 rtt=0.0 ms
len=28 ip=172.30.0.2 ttl=64 id=59359 icmp_seq=3 rtt=0.0 ms
[snip]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant