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

Forum Discussion

elrao's avatar
elrao
Aspirant
Feb 01, 2022

Orbi RBR50 - Solid Magenta - Not connecting to Modem

Hi All

 

I have a Zyxel modem setup in VDSL bridge mode, with an RBR30 as my router.  I followed the instructions here: https://kitz.co.uk/routers/zyxel_VMG8324-B10A_bridge.htm to set this up and it has been working fine for a year or so.   Per the instructions, I ended up with:

 

Modem IP: 192.168.1.1

Router IP: 192.168.1.254

Router DHCP range: 192.168.1.2 to 192.168.1.254

 

Modem LAN 1 --> Router WAN (Modem LAN 1 is split from the other LAN ports)

Modem LAN 4 --> Router LAN

 

Today, my broadband connection dropped and the light on my router went solid magenta.  I logged in via the web interfacte (192.168.1.254) and could see the internet connection was down.  I logged into the modem and could see it was UP!  So the router thinks it is "down".   I checked using my vodafone modem/router and the line itself is fine, so the issue is with my hardware.

 

I then lost connection to my router, after a lot of faffing about, it turns out the IP address was changed from 192.168.1.254 to prevent a conflict.  I managed to get it back in, but it has conflicted out a number of times (not sure what it is conflicting with).  Checking the modem, the status light shows the VDSL is up and the UI shows a healthy sync rate.  However the router shows solid magenta, which I have seen people mention (but usually in AP mode).  

 

Have tried different cables to connect the router to the modem, rebooted etc. etc. 

 

For now, am running with the Vodafone router to get back online and have turned all my satellites off as am using the same network ID; but am missing the MESH connectivity I bought the Orbi for!

8 Replies

  • Check your ISP modem and ISP services up to the modem. 

    Power off both modem and RBR for 1 minute then back ON.

     

    Be sure to restart your network in this sequence:
    Turn off and unplug modem.
    Turn off router and computers.
    Plug in and turn on modem. Wait 2 minutes for it to connect.
    Turn on the router and wait 2 minutes for it to connect.
    Turn on computers and rest of network.

    • plemans's avatar
      plemans
      Guru

      It wouldn't have been the first time an ISP supplied device got an update or change and caused conflict. 

      If the passthrough/modem only mode isn't working properly. Log into the router and change it to AP (access point) mode. 

      The ISP router needs to be in router mode so make sure to put it in that mode prior to changing the orbi. 

      • elrao's avatar
        elrao
        Aspirant

        Hi

         

        plemans , FURRYe38  thanks for your comments.

         

        plemans The ISP supplied device was not connected when the error occured and so can't be the cause of the conflict.  I had only re-connected the ISP supplied device in order to check if the problem was with the ISP or with my hardware.  Not sure if the Zyxel would have done an OTA update.

         

        I haven't tried setting up the Zyxel as the router, with the Orbi in AP mode.  I assume that you can have the main ORBI (i.e. the router) in AP mode and have satellites with no issues?  I guess I assumed I needed to use the ORBI as the router to make use of the mesh network.

         

        FURRYe38 I have already done 95% of what you said.  Using the ISP modem/router to validate the line is OK.  I then disconnected it all and started again with my own Modem (the Zyxel) and powered this on (VDSL light goes orange to show connected), then powered on the Orbi (light goes Magenta after a few minutes). 

         

        The only thing I didn't do was turn off ALL devices connected to the network (there are about 50 if you include the WiFi ones); however I do have static IPs set for the majority of devices (none that would conflict with either the 192.168.1.1 assigned to the modem and 192.168.1.254 assigned to the ORBI).