Interesting data point just occured now... I have my config setup as mentioned before: Wireless laptop/pico-w-server, and wireless laptop2/pico-w-client. The only change I made to the code was to change the "conversation": Instead of the client getting an input and the server then just echoing it back, I have the client just asking for an input (simple string) and the server responding back with an elapsed time since the server first started listening for the client. As usual, it did not work. I have a 3rd wireless PC in another room and I was pinging the server and seeing destination unreachable. Meanwhile I was re-reading your last reply and trying to make sure I am absorbing all of it. Turns out that about 10-15 minutes into reading and re-reading your reply, the pinging all of a sudden started working. I went back to the other room to watch what the picos were doing and they were communicating back and forth! The first elapsed time was something like 780 seconds., around 13 minutes. As I write this, the comm is communicating well for at least another 10 minutes. So the basic question is why did it take so long before I could successfully ping the server?
I am starting to try to get a bit educated about ARP (https://www.networkacademy.io/ccna/ethernet/what-is-arp) and see if tells me something about how my system does the pinging. I will upload a table tomorrow to show you the results of my pinging test.
I am starting to try to get a bit educated about ARP (https://www.networkacademy.io/ccna/ethernet/what-is-arp) and see if tells me something about how my system does the pinging. I will upload a table tomorrow to show you the results of my pinging test.
Statistics: Posted by dondondon — Sat Mar 16, 2024 6:10 am