Add support for Ping records

[tkoch96]

The README says 'can read all basic Warts data types (ping, traceroute)' but I don't see a Ping result reader? Granted it doesn't throw an error when I load Ping results. Please let me know if I'm misunderstanding this statement or have missed the Ping result reading functionality.

[jonglezb]

Hi, you are totally right, it seems that I never implemented support for the Ping type:

$ scamper -c ping -O warts -o ping-example.warts -i 1.1.1.1
$ ./parse_from_stdin.py < ping-example.warts
List(name="default", auto_id=1, manual_id=0)
CycleStart(auto_id=1, manual_id=0)
INFO:warts.base:Ignoring unknown record Unknown(type=7, length=201)
Unknown(type=7, length=201)
CycleStop(cycle_id=1, stop-time=1615819926)

I only used traceroutes in my research, and when I wrote the README I was probably thinking I would also implement ping, but in the end I didn't.

[jonglezb]

I won't have time to add support for this in the near term.

If you are a bit comfortable with Python, it shouldn't be too hard to do: it has the same basic structure as Traceroute. Instead of a Traceroute record + a list of TracerouteHop records, you'd have a Ping record + a list of PingResult records.

I'll happily review a pull request implementing this.

[jonglezb]

For documentation, run man ./scamper/warts.5 in scampers' source tree. The PDF on CAIDA's website is outdated, there have been new flags added since then.

I just notice that in both cases (PDF and latest source tree), the documentation is missing the format of ping results, the doc ends with this:

Ping response records are written in series. Each record takes the following form: