I have both the WAX206 AP and the EAX20 mesh extender. I configured them using the iPhone app but want to change some settings only available from the web interface. Both devices you login with routerlogin.net but in my case it only "sees" WAX206.
When I had some Netgear devices, the login page would ask me to select which device I wanted to connect to. Now it doesn't.
When I used to have these types of problems, my workaround was turning off the devices other than the one to be configured. In this case, the extender needs the WAX206 to be up.
I have both the WAX206 AP and the EAX20 mesh extender. I configured them using the iPhone app but want to change some settings only available from the web interface. Both devices you login with routerlogin.net but in my case it only "sees" WAX206.
The DNS request from the client is intercepted at the first possible point. This is the first device where the DNS query does pass, typically the device where the wireless client is connected (associated) to.
When I had some Netgear devices, the login page would ask me to select which device I wanted to connect to. Now it doesn't.
Some older devices (extenders when I have it right) however had a feature allowing enumerating other connected devices, a feature no longer maintained when I have it right.
Put up DHCP (IP MAC address pair) reservations for your WAX206 and the EAX20 on the DHCP server - typically your router. Some router vendors (like AVM FritzBox for example) even have some DNS capabilities to resolve these reserved hostnames in DNS.
I tried the first option. Connected the EAX20 to the PC via ethernet but still the DNS would find the WAX206 first.
Won't try the second option yet. I am not an expert and don't want to mess the settings. Will have to live with how things are.
If Netgear expects us to use the app, then the app should be able to do wll what the web interface does. It also appears that Netgear expects you to only buy one of these devices (assume now the focus is on mesh systems).
I tried the first option. Connected the EAX20 to the PC via ethernet but still the DNS would find the WAX206 first.
Its not about the way the devices are connected. It's just about the logical path the logical connection is established. Like walking into an apartment, with different rooms.
Won't try the second option yet. I am not an expert and don't want to mess the settings. Will have to live with how things are.
Putting up DHCP MAC-IP reservations up does not mess up with your individual device config. It just ensures we can reach the device desired by calling the appropriate IP address. Remember how the telephony system works? Numbers! It's not a groundbreaking change of any hard work settings.
If Netgear expects us to use the app, then the app should be able to do wll what the web interface does. It also appears that Netgear expects you to only buy one of these devices (assume now the focus is on mesh systems).
A long time ago, Netgear had the Genie App (and Desktop program) where a simple network map presented all devices, and you were able to choose, or correct spoken to jump on the next device if the first one in the path wasn't the one desired for the administration.
Thanks for your help. I left it alone (the settings I wanted to change were not "must have". The extender worked well a few days but now it shows "no internet" when connected via ethernet (was working OK).
I have now disconnected the EAX20 (The WAX206 is working fine without any problem). Looks like the EAX20 was a wrong purchase.
No need to try to resolve this new issue. Thanks for your assistance.
