I have one PC running Thonny, with the server Pico connected to it. Print statements in the basic server code I uploaded show it connected to the router as 192.168.1.153. It creates the listening socket and starts waiting for a client.
I have another PC running Thonny, with the client Pico connectd to it. I then start the client software. It also connects to the router as 192.168.1.174 Both are port 80.
The problem is that the server will not "accept" the client. In terms of pinging, I can use a Windows cmd window (xterm) and ping 192.168.1.153 from the client's PC and it shows "destination not available". Same goes from issuing ping 192.168.1.174 from the PC running the server.
If I restart the Pico server -- and don't bother to start the client -- and then ping 192.168.1.153, I get a successful ping using the server PC.
If I just start the client (no server), I get a successful ping using the client PC.
Interestingly, if I terminate the client, (keyboard interrupt, and Thonny REPL shows >>>), I can STILL successfully ping 192.1678.1.174. So even though the client app has terminated, 174 is still alive on the router. Looks like I need to modify the code for a WLAN.disconnect().
I have another PC running Thonny, with the client Pico connectd to it. I then start the client software. It also connects to the router as 192.168.1.174 Both are port 80.
The problem is that the server will not "accept" the client. In terms of pinging, I can use a Windows cmd window (xterm) and ping 192.168.1.153 from the client's PC and it shows "destination not available". Same goes from issuing ping 192.168.1.174 from the PC running the server.
If I restart the Pico server -- and don't bother to start the client -- and then ping 192.168.1.153, I get a successful ping using the server PC.
If I just start the client (no server), I get a successful ping using the client PC.
Interestingly, if I terminate the client, (keyboard interrupt, and Thonny REPL shows >>>), I can STILL successfully ping 192.1678.1.174. So even though the client app has terminated, 174 is still alive on the router. Looks like I need to modify the code for a WLAN.disconnect().
Statistics: Posted by dondondon — Thu Mar 07, 2024 2:19 am