One thing I discovered after making my pico-w software to dynamically connect to the strongest A/P - which could either be a repeater, or the main router, is that the repeaters I have will 'pervert' the MAC address from the pico-w into something else. So, when looking at the main router to which the repeaters are connected, it shows an active lease for the pico-w reserved I/P addr. However this is not the current I/P the pico-w has been assigned; it's just a left-over stale lease. In this situation, the pico-w doesn't respond to anything sent to the reserved I/P addr - thereby making me think it is not working and resetting it over and over.What you want to do is create a DHCP reservation for the MAC address / IP address combination. Then the IP address is reserved to that MAC address and even if it is not using DHCP, at least you won't have an IP address conflict. Assuming the router supports reservations, of course.
If you have a clean sparse network with just a few wireless devices, you might notice the pico-w at its newly assigned address, but if your network is busy with other cloud devices, it might not be obvious which one is the pico-w. If I connect a browser to the repeater's HTTP interface, I can see the pico-w at its fake MAC and the I/P.
Phew, did I explain that clearly?
Anyway, rather than play 'where's the pico', assigning it a static I/P addr outside the DHCP range, it will always be at that address - even if it doesn't even show up in the router's table of connected devices. You can then modify your hosts file to give it a name.
Statistics: Posted by ronter — Tue Jan 16, 2024 10:27 pm
