While diagnosing a local networking problem I found that prettyping doesn't handle duplicate ping messages. With the base ping tool I was periodically seeing output like this:
64 bytes from 0.0.0.0: icmp_seq=56890 ttl=64 time=1.174 ms (DUP!)
During this time I had prettyping running side by side in another window. It showed no indication of duplicate responses happening.
Note that I saw this comment in the script:
# TODO? How will prettyping behave if it receives a duplicate response?
I think the current answer is that prettyping does not handle duplicate responses.
It looks like ping considers duplicates a warning. But searching online seems to indicate that duplicates are unexpected, and often associated with link level problems.
It seems like prettyping should recognize duplicates, possibly as an error, and somehow display them.
While diagnosing a local networking problem I found that
prettypingdoesn't handle duplicate ping messages. With the basepingtool I was periodically seeing output like this:During this time I had
prettypingrunning side by side in another window. It showed no indication of duplicate responses happening.Note that I saw this comment in the script:
I think the current answer is that
prettypingdoes not handle duplicate responses.It looks like
pingconsiders duplicates a warning. But searching online seems to indicate that duplicates are unexpected, and often associated with link level problems.It seems like
prettypingshould recognize duplicates, possibly as an error, and somehow display them.