NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBR50 + satellite randomly disconnecting specific devices from internet
I hope someone else has run into this weird problem and can offer some advice, so I appreciate anyone that can help! I'll be as detailed as I can to get started. We have an RBR50 + satellite set ...
So far, the reports seem to confirm that EITHER turning off DST *or* TM no longer triggers the problem, using the standard graphical interface.
There are other fixes that also work but require debug-level direct access, e.g., restarting dnsmasq (recovers). Note that setting clients to no longer relay DNS through dnsmasq has *not* been shown viable; it would allow clients to continue working using their current DHCP assignment but if dnsmasq crashes then new assignments and renewals would fail.
This appears related to the recent DNS/NTP issue. The router appears to lose the ability to relay DNS requests.
To confirm, try to set the DNS on your laptop or phone to something other than the router.
Here's a link to one of many other threads on this topic:
It would affect only devices that are currently relaying DNS through the router whose DNS is set to 192.168.1.1 (the router).
You can get around this by either restarting the dnsmasq process on the router (as posted to the thread link I gave previously) or setting your device to use some other DNS (e.g., Cloudflare 1.1.1.1).
l8nc wrote:It would affect only devices that are currently relaying DNS through the router whose DNS is set to 192.168.1.1 (the router).
You can get around this by either restarting the dnsmasq process on the router (as posted to the thread link I gave previously) or setting your device to use some other DNS (e.g., Cloudflare 1.1.1.1).
Not exactly...I use 192.168.1.1 to get to the router and my Orbi clock / DNS is fine, but of course I'm not running the latest wiz-bang firmware.
Ahh, so having my own DNS IP addresses entered into the router itself doesn't automatically set it to that via the router's DHCP like you'd expect?
Ok, I've read the other thread on possible fixes, so I'm going to start with the simplest - turning off the DST and see if that helps. If not then I'll have to switch to my cable modem for DHCP functions.
Though I really don't understand why it wouldn't also affect some devices that don't have a way to manually set the DHCP, like the Roku that's hardwired into it, or the WiFi cameras that don't have any manual setup options at all. Those devices are 100% relying on the Orbi for all DHCP/DNS configuration...
> Ahh, so having my own DNS IP addresses entered into the router itself doesn't automatically set it to that via the router's DHCP like you'd expect?
There are two outcomes you might expect:
- the router provides those DNS IP addresses in DHCP responses
- the router uses those DNS IP addresses for its requests, but still tells DHCP clients to use itself (192.168.1.1) as their DNS
NG routers support #2 but not #1 (yet - I hope this might eventually change).
I.e., you can override only the DNS the router sends its queries to, not the DNS the DHCP clients use.
