v01d opened a new issue #3128: URL: https://github.com/apache/incubator-nuttx/issues/3128
I found that if I do ping to an unreachable address, such as 192.186.0.1 when no interface is set to that net, ping ends after 10 pings once, but a second call blocks at ping number 5: ``` NuttShell (NSH) NuttX-10.0.1 nsh> ping 1.1.1.1 PING 1.1.1.1 56 bytes of data No response from 1.1.1.1: icmp_seq=0 time=1000 ms No response from 1.1.1.1: icmp_seq=1 time=1000 ms No response from 1.1.1.1: icmp_seq=2 time=1000 ms No response from 1.1.1.1: icmp_seq=3 time=1000 ms No response from 1.1.1.1: icmp_seq=4 time=1000 ms No response from 1.1.1.1: icmp_seq=5 time=1000 ms No response from 1.1.1.1: icmp_seq=6 time=1000 ms No response from 1.1.1.1: icmp_seq=7 time=1000 ms No response from 1.1.1.1: icmp_seq=8 time=1000 ms No response from 1.1.1.1: icmp_seq=9 time=1000 ms 10 packets transmitted, 0 received, 100% packet loss, time 10100 ms nsh> ping 1.1.1.1 PING 1.1.1.1 56 bytes of data No response from 1.1.1.1: icmp_seq=0 time=1000 ms No response from 1.1.1.1: icmp_seq=1 time=1000 ms No response from 1.1.1.1: icmp_seq=2 time=1000 ms No response from 1.1.1.1: icmp_seq=3 time=1000 ms No response from 1.1.1.1: icmp_seq=4 time=1000 ms No response from 1.1.1.1: icmp_seq=5 time=1000 ms ``` This hangs here but after maybe about a minute continues sending pings about 1 per second and then finishes: ``` No response from 1.1.1.1: icmp_seq=6 time=1000 ms No response from 1.1.1.1: icmp_seq=7 time=1000 ms No response from 1.1.1.1: icmp_seq=8 time=1000 ms No response from 1.1.1.1: icmp_seq=9 time=1000 ms 10 packets transmitted, 0 received, 100% packet loss, time 70120 ms nsh> nsh> ``` I tested this on ESP32 with WAPI config, but I'm not sure that is relevant. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
