NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR50 crashes during configuration
Hello, since I've updated to 2.5.1.8, the system has become a real pain in the ass when configuring dhcp and I have no clue how to fix it. I need to reserve the addresses of about 50 IoT devices ...
Hi, i spent several hours re-installing and configuring the devices. Fact is, I can't restart the system since it tends to forget the configured addresses. The workaround is to use backups every time and since the router is hooked to my UPS, chances are that it's not gonna restart due to power loss. Fingers crossed and in the meantime I've looked at other solutions...
To finish this story: today, my router had a fatal accident with a 10 pound hammer, crashed it completely to pieces. It was quite satisfying... The remains will be delivered to the local dump.
The reason for this is that this little **bleep** chose to give my surveillance cam a new network address the other day (yes, not the one that's still reserved in the DHCP-Server) - what's more, it chose one that collides with my internal dns server address - which is connected via cable -, causing just a very little bit of a bloody mess in my network. I've checked it twice: the cam gets a new address every time(!!) it reconnects. Seems like *this* Orbi didn't even know the term "lease time". In combination with the colliding addresses, this is just a no-go. I'm done with it and switching to a more reliable system. Lucky enough, the test systems are already sitting on my table.
Just a last word about the double NAT and my network setup: the internal net behind the Orbi-DHCP caused the problems. It's never shown any problem with the internet connection or the devices in my DMZ zones. I really tried to fix these problems via updates, reserving addresses etc but if the systems doesn't even remember that the same MAC has been given an address just 10 seconds before (and leases a new one every time), it's junk. Even more, if it ignores fixed addresses.
Cheers,
Uwe
The RBR is connected to a AVM Fritz!Box 7490 DSL Modem.
Did a downgrade to 2.3.5.30 yesterday - feels like it's slightly more stable now but still crashes when I try to add devices via the advanced configuration listing. Am doing it manually now - with about 50 devices configured, I'd rather not do a full reconfiguration in the next few days. If it comes to a full lockdown here in Germany, maybe there'll be enough spare time that needs to be filled... :-(
Cheers and stay at home if you can
Uwe
Your ISP modem has a built in router and wifi:
This would be a double NAT condition which isn't recommended. https://kb.netgear.com/30186/What-is-Double-NAT
https://kb.netgear.com/30187/How-to-fix-issues-with-Double-NAT
Couple of options,
1. Configure the modem for transparent bridge or modem only mode. Then use the Orbi router in router mode. You'll need to contact the ISP for help and information in regards to the modem being bridged correctly.
2. If you can't bridge the modem, disable ALL wifi radios on the modem, configure the modems DMZ/ExposedHost or IP Pass-Through for the IP address the Orbi router gets from the modem. Then you can use the Orbi router in Router mode.
3. Or disable all wifi radios on the modem and connect the Orbi router to the modem, configure AP mode on the Orbi router. https://kb.netgear.com/31218/How-do-I-configure-my-Orbi-router-to-act-as-an-access-point and https://www.youtube.com/watch?v=H7LOcJ8GdDo&app=desktop
I would try a factory reset of the RBR and RBS after re-applying v2.5.1.8 FW version after you correctly configure the ISP modem or system using one of the options suggested above.
Hi, i spent several hours re-installing and configuring the devices. Fact is, I can't restart the system since it tends to forget the configured addresses. The workaround is to use backups every time and since the router is hooked to my UPS, chances are that it's not gonna restart due to power loss. Fingers crossed and in the meantime I've looked at other solutions...
To finish this story: today, my router had a fatal accident with a 10 pound hammer, crashed it completely to pieces. It was quite satisfying... The remains will be delivered to the local dump.
The reason for this is that this little **bleep** chose to give my surveillance cam a new network address the other day (yes, not the one that's still reserved in the DHCP-Server) - what's more, it chose one that collides with my internal dns server address - which is connected via cable -, causing just a very little bit of a bloody mess in my network. I've checked it twice: the cam gets a new address every time(!!) it reconnects. Seems like *this* Orbi didn't even know the term "lease time". In combination with the colliding addresses, this is just a no-go. I'm done with it and switching to a more reliable system. Lucky enough, the test systems are already sitting on my table.
Just a last word about the double NAT and my network setup: the internal net behind the Orbi-DHCP caused the problems. It's never shown any problem with the internet connection or the devices in my DMZ zones. I really tried to fix these problems via updates, reserving addresses etc but if the systems doesn't even remember that the same MAC has been given an address just 10 seconds before (and leases a new one every time), it's junk. Even more, if it ignores fixed addresses.
Cheers,
Uwe
Sounds like a user configuration issue. Haven't seen this issue at all.
One can set up cameras or any devices for static IP addresses outside of a default IP address pool to help avoid networking configuration issues. I have 3 cameras setup with my Orbi system. Zero issues. Using static IP addresses outside of the DHCP IP addresss pool.
I would review more networking configuration information on howe networking and devices can be connected.
Good Luck.