NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

2pfspiff's avatar
Oct 23, 2018
Solved

R8000 can not log into X6 GUI when in AP mode.

Good day.  I have an X6 R8000 nighthawk that is in AP mode and I am not able to access the GUI through Routerlogin.net/.com and 192.168.1.1.  I am using a Xfinity 1 gig Arris TG3482G modem/router run...
  • antinode's avatar
    Oct 23, 2018

    > [...] I have an X6 R8000 nighthawk that is in AP mode and I am not
    > able to access the GUI through Routerlogin.net/.com and 192.168.1.1.
    > [...]

       Those "routerlogin" names work only when the Netgear router is used
    as your DNS server, which won't be true for a wireless access point.
    And, the LAN IP address of a WAP is practically never what it would be
    if it were configured as a full-function router ("192.168.1.1").

       To reach the management web site of the R8000-as-WAP, you need to
    know its LAN IP address, and that depends on exactly how you configured
    the R8000-as-WAP.  If you had chosen "Enable fixed IP settings on this
    device (not recommended)", then you would have specified that address
    yourself, and you'd already know it.  More likely, you chose "Get
    dynamically from existing router", and so the R8000-as-WAP got its
    address from (the DHCP server on) the main router.  

       With any luck, that main router will provide some kind of "Attached
    Devices" or "DHCP Clients" report where you'll be able to find the
    R8000-as-WAP, and which which will reveal the new LAN IP address of the
    R8000-as-WAP.  If you point your web browser at _that_ address, then you
    may be able to reach the management web site of the R8000-as-WAP.

       If you want to find the R8000-as-WAP later with less effort, then you
    should be able to reserve an address for it in the DHCP server
    configuration of the main router.  (Pick something memorable.)

    > [...] I tried to put the Arris into Bridge mode, but it did not
    > function properly. [...]

       Not much meat on that bone.  That was the other option for getting to
    a configuration with only one NAT router.