I bought a second wifi ap to test my embedded code. It is a recent NETGEAR access point.
After awhile I noticed that my picow got "lost" on my network. From this I mean mdns could not locate the picow and I could not ping it by its ip address, which the website prints out every 10 seconds. I could not tell where this was happening, but I was changing my webapp code, so I assumed my code was wrong. So I used git to get the suspected problem code (2 servers I was no longer using dns and dhcp). Nope, even going to this older software it is still losing the connection.
Interestingly the picow could still access the network ntp server, which it does every 2 hours to update its clock. So the picow could get out, but the local stuff on my network could not get to the picow! Also interesting, if I leave a ping running on a console in my linux development box, I do not lose connectivity via LAN to the picow.
As a test I switched back to my original wifi AP (an old linksys ap/router). Now my picow remains on the network for both mdns and ping to the picow ip address. Before this ran for days, so far with the change in router it has run for several hours.
This swap of AP in use I did a couple times. So it would appear the NETGEAR AP has some flaw, or recent wifi standards have changed.
Both APs are connected to a switch that is connected by about 100 ft of Ethernet cable to another switch which is connected to my ISPs wifi router. So I think a fairly normal setup for a mainly ethernet LAN.
Any ideas? I thought the newer AP would be better, but it seems defective.
After awhile I noticed that my picow got "lost" on my network. From this I mean mdns could not locate the picow and I could not ping it by its ip address, which the website prints out every 10 seconds. I could not tell where this was happening, but I was changing my webapp code, so I assumed my code was wrong. So I used git to get the suspected problem code (2 servers I was no longer using dns and dhcp). Nope, even going to this older software it is still losing the connection.
Interestingly the picow could still access the network ntp server, which it does every 2 hours to update its clock. So the picow could get out, but the local stuff on my network could not get to the picow! Also interesting, if I leave a ping running on a console in my linux development box, I do not lose connectivity via LAN to the picow.
As a test I switched back to my original wifi AP (an old linksys ap/router). Now my picow remains on the network for both mdns and ping to the picow ip address. Before this ran for days, so far with the change in router it has run for several hours.
This swap of AP in use I did a couple times. So it would appear the NETGEAR AP has some flaw, or recent wifi standards have changed.
Both APs are connected to a switch that is connected by about 100 ft of Ethernet cable to another switch which is connected to my ISPs wifi router. So I think a fairly normal setup for a mainly ethernet LAN.
Any ideas? I thought the newer AP would be better, but it seems defective.
Statistics: Posted by nospamcalfee — Tue Jun 24, 2025 10:11 pm — Replies 2 — Views 58