NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Not able to login (locally) to R9000 X10
I cannot login to the Genie interface of my R9000. I get the login prompt (username:admin, password) after which the browser (tried firefox, chrome, IE) all show "transferring data from 192.168.1.1"...
It was Bitdefender's Privacy setting. I had to add the IP address to the whitelist in Bitdefender.
alokeprasad wrote:
It was Bitdefender's Privacy setting. I had to add the IP address to the whitelist in Bitdefender.
...for http only. The R9000 does support https, and comes with a valid certificate for routerlogin.net et all:
Does using routerlogin.net (instead of 192.168.1.1) require a fuctional internet access?
How is the name "routerlogin.net" resolved?
Curious.
Aloke
> Does using routerlogin.net (instead of 192.168.1.1) require a fuctional
> internet access?No.
> How is the name "routerlogin.net" resolved?
The router intercepts it, and returns its own LAN IP address.
If your client device is configured to use some real-world DNS server
instead of a Netgear router, then you might find yourself talking to a
Netgear web server with a misleading/useless error page for your
enjoyment.https://community.netgear.com/t5/x/x/m-p/1365830
Interestingly, a typical Netgear router will intercept a request for
one of those "routerlogin" names, even when it's configured as a
wireless access point, and you might expect it not to deal with DNS.
antinode wrote:
If your client device is configured to use some real-world DNS server
instead of a Netgear router, then you might find yourself talking to a
Netgear web server with a misleading/useless error page for your
enjoyment.In Win10's network IPv4 settings, I have the Gateway set to the R9000 (192.168.1.1) and DNS to Cloudflare and Google (1.1.1.1 and 8.8.8.8).
Thats what ipconfig shows as well. In the router's Advanced Internet setup. I have these DNS entered as well.
Routerlogin.net is still getting resolved correctly to 192.168.1.1 (I am seeing the router's setup screens) in Win10.
How come?
> [...] DNS to Cloudflare and Google (1.1.1.1 and 8.8.8.8). [...]
> [...] Routerlogin.net is still getting resolved correctly to
> 192.168.1.1 [...]The R9000 could be intercepting even more DNS stuff than I'd expect,
or your Windows system or web browser could be using a cached value.What does "nslookup routerlogin.net" say?
