Again, as far as the networking protocols, the router would not.I also set a hostname for the Pico, but the router doesn't appear to make use of this either
Just to review what you are after, what are you expecting to see, and where exactly? Why do you need the information from the router itself? Let's see if there is another solution.
Don't rely on the router to do extra things besides what I said above. TCP connection logs are a bonus feature and maybe your best bet for showing traffic.
All traffic is on the same subnet, correct?
Since I don't have a Pico W, nor a WiFi extender, I can't test anything for you, but have you, as an experiment set one of the RPi units static, attach it to your extender, then look at your router client list? I suspect it would also not be there unless the router does ping scans or arping scabs actively. If you ran arping from your Pi while connected to your router AP, and the Pico connected to the extender, do you get anything back? I'm not sure if you would due to the MAC translation. Ping, however, should work. arp-scan or nmap can do arp scans and IP scans, if needed.
This all begs the questions that I now have about the Pico W.
Since all hosts, not only routers need a routing table, and all IPv4 hosts need an arp table, how does one,
A) display the routing table of the Pico W
B) display the routing cache
B) display the arp table /cache of the Pico W
C) view the active socket table on a Pico W
Statistics: Posted by breaker — Thu Jan 18, 2024 10:07 pm
