acassis commented on issue #7802: URL: https://github.com/apache/nuttx/issues/7802#issuecomment-1339532595
Some important information: If the WiFi/SSID is defined in the menuconfig the issue doesn't happen. The initial PR https://github.com/apache/nuttx/pull/7616 was the initial guilt, but later PR increased the issue. With only the original PR if we try to ping from computer to the esp32 board the ping will not work, but I noticed that when we run at same time ping from board "nsh>" to some external IP, magically the ping from PC works monumentally and then start to DUP until read ~1010ms and succeed a single ping and start increasing the DUP timeout until reach 1010ms and a successful ping happen and the cycle restarts: ``` nsh> ping 8.8.8.8 PING 8.8.8.8 56 bytes of data 56 bytes from 8.8.8.8: icmp_seq=0 time=60.0 ms 56 bytes from 8.8.8.8: icmp_seq=1 time=40.0 ms 56 bytes from 8.8.8.8: icmp_seq=2 time=40.0 ms 56 bytes from 8.8.8.8: icmp_seq=3 time=40.0 ms 56 bytes from 8.8.8.8: icmp_seq=4 time=50.0 ms 56 bytes from 8.8.8.8: icmp_seq=5 time=40.0 ms 56 bytes from 8.8.8.8: icmp_seq=6 time=40.0 ms 56 bytes from 8.8.8.8: icmp_seq=7 time=40.0 ms 56 bytes from 8.8.8.8: icmp_seq=8 time=40.0 ms 56 bytes from 8.8.8.8: icmp_seq=9 time=40.0 ms 10 packets transmitted, 10 received, 0% packet loss, time 10100 ms rtt min/avg/max/mdev = 40.000/43.000/60.000/6.403 ms ``` From PC to computer: ``` 64 bytes from 192.168.0.7: icmp_seq=170 ttl=64 time=1000 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=170 ttl=64 time=1000 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=170 ttl=64 time=1003 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=170 ttl=64 time=1003 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=171 ttl=64 time=4.33 ms ... 64 bytes from 192.168.0.7: icmp_seq=171 ttl=64 time=135 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=171 ttl=64 time=135 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=171 ttl=64 time=136 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=172 ttl=64 time=8.97 ms ... 64 bytes from 192.168.0.7: icmp_seq=172 ttl=64 time=1004 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=172 ttl=64 time=1004 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=172 ttl=64 time=1010 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=172 ttl=64 time=1011 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=173 ttl=64 time=12.3 ms ... bytes from 192.168.0.7: icmp_seq=174 ttl=64 time=1007 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=174 ttl=64 time=1012 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=174 ttl=64 time=1012 ms (DUP!) 64 bytes from 192.168.0.7: icmp_seq=175 ttl=64 time=13.0 ms ``` After applying remaining PRs (master HEAD) the ping only works momentarily during the "nsh>" ping and after it finishes the PC ping always returns DUP timeout. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
