On Sun, 19 Dec 2021, J Doe wrote:
8.8.8.8 truncates ICMP's responses, this is well known. Different platforms will react differently to it.
lukas@dev:~$ ping 8.8.8.8 -c1 -s1000 PING 8.8.8.8 (8.8.8.8) 1000(1028) bytes of data. 76 bytes from 8.8.8.8: icmp_seq=1 ttl=116 (truncated)
--- 8.8.8.8 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 5.657/5.657/5.657/0.000 ms lukas@dev:~$ ping 1.1.1.1 -c1 -s1000 PING 1.1.1.1 (1.1.1.1) 1000(1028) bytes of data. 1008 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=15.8 ms
--- 1.1.1.1 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 15.893/15.893/15.893/0.000 ms lukas@dev:~$
Hi,
Out of curiosity - does anyone know why Google is truncating ICMP responses ?
My guess would be to reduce "garbage traffic bandwidth". They're running an open resolver...not a lighthouse. ---------------------------------------------------------------------- Jon Lewis, MCP :) | I route StackPath, Sr. Neteng | therefore you are _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________