Cannot get in to router settings

> [...] Whenever I check for updates (weekly), it always says this is
> the latest version. [...]

   Not as reliable, in general, as checking the available downloads, but
true in this case.  In general:

   Visit http://netgear.com/support , put in your model number, and look
for Downloads.  (For older versions, under Firmware and Software
Downloads, look for "View Previous Versions".)  Find the kit(s).
Download the kit(s) you want.  Read the "Release Notes" file for
instructions.  (In the User Manual, look for "firmware", and,
especially, for a topic like "Manually Upload Firmware to the Router".)
When that fails because of a deficient User Manual, try:

      https://kb.netgear.com/23960

> [...] the Netgear manual instructions say to connect the modem's LAN
> jack to the Netgear Router's LAN jack via the ethernet cable. [...]

   Huh?  _Which_ "the Netgear manual" says _what_, exactly?  "the
Netgear Router's _LAN_ jack"?

   If you're having trouble getting into "http://routerlogin.net" on the
R8000P when it's configured as a router, then you might try not
connecting any modem to the R8000P.  That should avoid many types of
DNS and other problems.  (See, for example:
https://community.netgear.com/t5/x/x/m-p/2021905 )

   When you connect your Mac to the R8000P (LAN Ethernet port or
wireless), does that interface get a proper IP configuration?

   If you've progressed to configuring the R8000P as a wireless access
point, then...

   When you configure the R8000P as a wireless access point, it should,
by default, get a new/different LAN IP address from your main router,
using DHCP.  When that happens, you'll need to ask your main router
about the devices which are connected to it to learn the new/different
LAN IP address of the R8000P-as-WAP.  Most likely, you'll want to
reserve a particular (memorable) address for the R8000P-as-WAP (on the
main router), so that it will always get the same address, and you won't
need to hunt for it every time you want to talk to the thing.

   There's some chance that the usual "routerlogin" names will still
work, if your client device is connected directly to the R8000P-as-WAP,
but its new/different LAN IP address should work from anyplace on your
LAN.

---

VJOGuy wrote:

So the Netgear manual instructions say to connect the modem's LAN jack to the Netgear Router's LAN jack via the ethernet cable.  (turns out, it was already configured that way).  Since my iMac browsers won't let me in to the router settings, I tried it on my iPad.  First I ensured that the WiFI was the one from the Netgear router.  Then, I used routerlogin.net.  In Safari, I get a "Safari cannot open the page because it could not connect to the server" message.  When I use Safari and 192.168.1.1 to try to log in, the search never completes....it just times out.

 

I tried it with Brave (browser) on my iPad, and I was able to log in to the settings (makes no sense to me why so many other browsers don't allow me to log in, but this one does?).  

 

The last step was to log out of the settings, and then back in.  And don't you know it?  I can't log back in now!  Same thing as before...inputting 192.168.1.1 has the browser searching and not going anywhere.  And routerlogin.net or .com keeps taking me back to the Netgear.com website, instead of the router settings!  

---

ALmost everything more than strange. And honestly, not much Netgear router things going on here. Three things come into my mind:

1. ref. the routerlogin.com/.net ... of your MacOS system or any other system is configured to use secured DNS (encrypted DNS) the Netgear router will never "see" the DNS query and you will end on the Netgear landing page instead.

2. 192.168.1.1 isn't a search ... if the browser does start a search instead of heading to the IP, do't jnow what to say - it should be taken as an URL by the browser. try http://192.168.1.1/ instead  

3. Is it possible your iMac and your mobile devices are connected, or can connect to the other router?