On Sep 25, 2021, at 8:44 PM, Valdis Klētnieks <valdis.kletni...@vt.edu> wrote: > > On Sat, 25 Sep 2021 23:20:26 +0200, Baldur Norddahl said: > >> We should remember there are also multiple ways to print IPv4 addresses. >> You can zero extend the addresses and on some ancient systems you could >> also use the integer value. > > 19:17:38 0 [~] ping 2130706433 > PING 2130706433 (127.0.0.1) 56(84) bytes of data. > 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.126 ms > 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.075 ms > 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.063 ms > 64 bytes from 127.0.0.1: icmp_seq=4 ttl=64 time=0.082 ms > ^C > --- 2130706433 ping statistics --- > 4 packets transmitted, 4 received, 0% packet loss, time 84ms > rtt min/avg/max/mdev = 0.063/0.086/0.126/0.025 ms > > Works on Fedora Rawhide based on RedHat, Debian 10, and Android 9. > > That's a bit more than just 'some ancient systems' - depending whether > it works on other Android releases, and what IoT systems do, we may have > more systems today that support it than don't support it.
It also works on this 'ancient' macOS Monterey system. Last login: Sat Sep 25 20:50:00 on ttys000 xz4gb8 ~ % ping 2130706433 PING 2130706433 (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=64 time=0.047 ms 64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.111 ms 64 bytes from 127.0.0.1: icmp_seq=2 ttl=64 time=0.103 ms 64 bytes from 127.0.0.1: icmp_seq=3 ttl=64 time=0.109 ms ^C --- 2130706433 ping statistics --- 4 packets transmitted, 4 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.047/0.092/0.111/0.026 ms xz4gb8 ~ %
