NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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 i...
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).
If the orbi is in access point mode, the mesh/roaming/satellites will all still function properly.
Its not typical to have the modem and the router in the same subnet (192.168.1.***) if they're in a proper passthrough/modem only/dmz mode. Thats why you can get conflicts.
You might have just been lucky or not had enough devices to cause conflicts.
so I'd try leaving the ISP gateway in router mode (disabe its wifi) and put the orbi in access point mode.
The range on the router is 192.168.1.2 to 192.168.1.254. The modem is 192.168.1.1, so should be no IP conflict as the router would never try to assign 192.168.1.1 to any other device. Worked like this for 2 years!
Then the other day, just stopped working. Nothing was changed by me, the internet just dropped out from the network even though the modem showed as connected.
Any conflict would appear to be on the 192.168.1.254 address, as the router (which has this address) is being assigned another address to remove the conflict (but it is not conflicting with the modem, as that is still accessible with 192.168.1.1).
So it worked for 2 years.
yay for you. but it still wasn't setup properly and is still a double nat.
And worse, its a double nat with both routers in the same subnet.
Its lucky it worked at all.
If you want to leave it as is, go ahead. But it isn't working.
So maybe a change to set it up properly is needed.
Why is it double NAT when the modem has all that functionality disabled? It is in bridge mode, which, by definition means that NAT is disabled on it!
The Zyxel (modem) is setup so that "LAN1" is connected to the WAN port on the ORBI. "LAN 4" is then connected to the LAN side of the ORBI. On the Zyxel, LAN1 is then segregated from the rest of the ports, so the modem basically has a LAN side (LAN 2 - 4) and a WAN side (LAN 1).
The reason for having the modem (LAN side) on the same subnet is to allow me to access it via the network to check on line stats etc.
This is a tried and tested setup, used by many others with no issues, not just me. Yay.