An miserable attempt to implement basic ping functionality and extend it with more features. Written solely for educational purposes and not for production use. Probably contain many bugs and horrible code style :-) You are welcome to report them or just leave some feedback.
ping forever until it crashes due to some bug :-)
./ping google-public-dns-a.google.com. -c -1
--- ping google-public-dns-a.google.com. (8.8.8.8) ttl=32; count=-1; timeout=5s ---
src=8.8.8.8 rtt=73.95ms ttl=51 seq=1 type=echoreply code=null
...
set packet TTL to find next hop (router) address (this is how tracert, traceroute, tracepath, mtr are works)
./ping google-public-dns-a.google.com. -T 1 -c 3
--- ping google-public-dns-a.google.com. (8.8.8.8) ttl=1; count=3; timeout=5s ---
src=10.1.0.1 rtt=3.48ms ttl=64 seq=0 type=time_exceeded code=exc_ttl
src=10.1.0.1 rtt=3.47ms ttl=64 seq=0 type=time_exceeded code=exc_ttl
src=10.1.0.1 rtt=3.51ms ttl=64 seq=0 type=time_exceeded code=exc_ttl
--- ping google-public-dns-a.google.com. (8.8.8.8) statistics ---
min rtt=3.47ms; max rtt=3.51ms; avg rtt=3.49ms; sent=3; recv=3; lost=0
an example of tracing route path to 5.255.255.60 (yandex.ru)
for x in {1..16};do echo [$x] - $(./ping 5.255.255.60 -T ${x} -c 1 -t 3 | grep -Eo "src=\S+\s+rtt=\S+" | sed -e 's/src=//g' -e 's/rtt=/- /'g); done
1 - 192.168.10.1 - 4.21ms
2 -
3 -
4 - 212.179.37.1 - 14.46ms
5 - 10.250.0.162 - 20.13ms
6 - 212.25.77.2 - 15.99ms
7 - 62.219.189.6 - 72.52ms
8 - 195.66.226.69 - 73.09ms
9 - 213.180.213.95 - 100.90ms
10 - 213.180.213.91 - 105.79ms
11 - 84.201.142.235 - 124.09ms
12 -
13 - 5.255.255.60 - 101.36ms
14 - 5.255.255.60 - 100.58ms
15 - 5.255.255.60 - 101.58ms
16 - 5.255.255.60 - 101.24ms