NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RAX40 Firmware 1.0.3.80 Crash/Bug Log
Hello folks, can everyone please log all the issues they are experiencing with the RAX40 router on 1.0.3.80 firmware under this thread, I see there are several threads going on about the issue, figur...
I updated my router today and so far it seems fine. I did a factory reset, upgrade, another factory reset and then re-configured the thing to give it the best chance of working and not having issues due to an old config. The real test will be this weekend when various family comes over and there will be more devices.
I use mine in AP mode and not as my main router. This update introduces one issue in this particular configuration. The router admin page now forces one to access it using the www.routerlogin.net domain rather than allowing the IP address. Since the device is not my router and not handling my DNS it's unable to intercept those requests so you end up at their help page instead of the admin UI. I had to add a hosts file entry for the domain in order to regain access the admin page.
@ aoeex
I'm running firmware 94.
I am able to access the admin page using the IP address of the router and by www.routerlogin.net. I am not running in AP mode but not sure why that would make a difference.
Using the IP just results in the router issuing a redirect to the domain now. The domain only works if the RAX40 is providing the DNS services for your network as it will respond to a DNS request for routerlogin.net with it's local IP address. If the RAX isn't the device processing DNS requests then that domain instead resolves to it's public IP which takes you to netgear's help page.
Most people in most situations probably wouldn't have an issue as the RAX40 would be their main router and their DNS host so everything would work fine.
Since I have mine in AP mode, it's not handling my DNS queries (the main router does) so the routerlogin.net domain resolves to the public IP and shows the help page, not the admin UI. Due to that, and the fact that using the IP just results in a redirect to the domain, the admin UI is effectively inaccessible in such a configuration. A local override of that domain via the system's hosts file or a local DNS server is necessary for it to work.
It just seems to me that if you browse to http://[ip of rax40] that DNS would not be required and whatever you are using for your router would route (via internal switch) that request to the IP adress of the RAX40. I am assuming the RAX40 is using the same IP Subnet as your router. I could understand if www.routerlogin.net doesn't work because the RAX40 is not providing your DNS.
But the main thing is you are able to access the RAX40 admin screen using a hosts file. Sometimes it is just not worth the effort to figure out why something doesn't work when you can use an easy work-around to get what you need. So it sounds like you are golden.