05-14-2012 06:14 PM - edited 03-17-2019 11:10 PM
Hi All,
Through some issue troubleshooting I've stumbled across what seems to be odd behaviour with the Codian 4510. In two seperate environments I've found that pinging the device with a packet size of greater than 76 bytes of data results in timeouts as per below. Does anyone know why this occurs?
localhost:~ jason$ ping -s 76 10.2.0.208
PING 10.2.0.208 (10.2.0.208): 76 data bytes
84 bytes from 10.2.0.208: icmp_seq=0 ttl=254 time=3.642 ms
84 bytes from 10.2.0.208: icmp_seq=1 ttl=254 time=3.579 ms
^C
--- 10.2.0.208 ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 3.579/3.611/3.642/0.031 ms
localhost:~ jason$ ping -s 77 10.2.0.208
PING 10.2.0.208 (10.2.0.208): 77 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
--- 10.2.0.208 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
Solved! Go to Solution.
05-15-2012 02:14 AM
This is by design, in order to prevent problems due to excessively large ICMP packets.
05-15-2012 02:14 AM
This is by design, in order to prevent problems due to excessively large ICMP packets.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide