NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FYI: Firmware update 2.5.1.8 causes DNS timeouts only fixed by reboot on my RBR50 and RBS50's
Hi All,
Mostly an FYI as I've downgraded back to 2.3.5.30 and all is well again.
I have one RBR50 and three RBS50's that have been working flawlessly for pretty much as long as I can remember behind an Xfinity Xfi modem that is bridged. I saw the firmware update 3 days ago and upgraded all devices to 2.5.1.8. Ever since, the RBR50 has gone unresponsive for DNS queries multiple times per day. Existing connections were fine (i.e. it passed traffic back and forth just fine) but as soon as name resolution came in (i.e. going to a new website) the connection would fail with a DNS timeout. The only way to fix it was to reboot the RBR50.
To troubleshoot, I noted the DNS server it is setup to use (comcast 75.75.75.75 and .76) and at a time when name resolution wasn't working, I manually configured my desktop to use those DNS servers while leaving IP at DHCP. Voila, everything worked fine. So, for whatever reason, while the RBR technically had access to the DNS server (since I could connect to it from my desktop) it was timing out queries.
I downgraded all devices back to 2.3.5.30 and everything has been working again for the last 24 hours. Note also that for as long as I've had these devices (2+ years) the network map shows all satellites connected directly to the router. After the 2.5.1.8 update, it showed that 2 of the satellites were connecting to one of the other satellites, and that one was the only one connecting to the router. I know it's a mesh, but a bit odd that after all this time the topology suddenly changed.
Anyway - as noted, mostly an FYI. Curious how these issues get back to the dev team when the free 90 day support has long expired?
Thanks,
Per
21 Replies
I went into the Orbi app and it showed an update was available, prompting me to update.
And now that I'm downgraded, it again shows me that; same if I go to routerlogin.net (see attached)
perfarny wrote:I went into the Orbi app and it showed an update was available, prompting me to update.
And now that I'm downgraded, it again shows me that; same if I go to routerlogin.net (see attached)
so what's the problem? You don't have to update. Is your system working now?
This explains the other comment I replied to. I did not manually upgrade, that I am aware of, and I am on 2.1.5.8
Retired_Member wrote:The part I missed is how you came upon 2.5.1.8.?
The recommendation is to stay away from manual updates.
OrbiPhilip wrote:This explains the other comment I replied to. I did not manually upgrade, that I am aware of, and I am on 2.1.5.8
Retired_Member wrote:The part I missed is how you came upon 2.5.1.8.?
The recommendation is to stay away from manual updates.
could be...I believe i saw the same thing with....FM ....2.3.5.30
when it was first available it was bad....then after a few months, NG started pushing it out auto. I've been on it since Oct19.
FYI...to me manual means you clicked something to start the download. auto means you wake up and there it is.
What happens if you don't use any custome DNS on the RBR?
Try using 1.1.1.1 and 9.9.9.9 for DNS.
Has a factory reset and setup from scratch been performed since last FW update?
I and others don't see this issue. Doesn't mean that this version is buggy either. Try a reset next time you update FW to be sure.
If it was FW, more users would be posting about it.
perfarny wrote:Hi All,
Mostly an FYI as I've downgraded back to 2.3.5.30 and all is well again.
I have one RBR50 and three RBS50's that have been working flawlessly for pretty much as long as I can remember behind an Xfinity Xfi modem that is bridged. I saw the firmware update 3 days ago and upgraded all devices to 2.5.1.8. Ever since, the RBR50 has gone unresponsive for DNS queries multiple times per day. Existing connections were fine (i.e. it passed traffic back and forth just fine) but as soon as name resolution came in (i.e. going to a new website) the connection would fail with a DNS timeout. The only way to fix it was to reboot the RBR50.
To troubleshoot, I noted the DNS server it is setup to use (comcast 75.75.75.75 and .76) and at a time when name resolution wasn't working, I manually configured my desktop to use those DNS servers while leaving IP at DHCP. Voila, everything worked fine. So, for whatever reason, while the RBR technically had access to the DNS server (since I could connect to it from my desktop) it was timing out queries.
I downgraded all devices back to 2.3.5.30 and everything has been working again for the last 24 hours. Note also that for as long as I've had these devices (2+ years) the network map shows all satellites connected directly to the router. After the 2.5.1.8 update, it showed that 2 of the satellites were connecting to one of the other satellites, and that one was the only one connecting to the router. I know it's a mesh, but a bit odd that after all this time the topology suddenly changed.
Anyway - as noted, mostly an FYI. Curious how these issues get back to the dev team when the free 90 day support has long expired?
Thanks,
Per
FURRYe38 wrote:What happens if you don't use any custome DNS on the RBR?
Try using 1.1.1.1 and 9.9.9.9 for DNS.
I never used a custom DNS on the RBR, I simply let it get its info via DHCP. Only in troubleshooting did I statically configure a DNS serveron my desktop (which happened to be the same one that the RBR was given to use...and it worked when my desktop was configured to use it directly vs asking the RBR to do name resolution on its behalf).
I'm not going to update again to the new firmware as I'm stable (again) now.
FURRYe38 wrote:Has a factory reset and setup from scratch been performed since last FW update?
I and others don't see this issue. Doesn't mean that this version is buggy either. Try a reset next time you update FW to be sure.
If it was FW, more users would be posting about it.
I did not do that. Sounds like there's history in that working for other issues in the past? Will try that if/when I do future updates. Thanks!
Same issues for me after I upgraded firmware. I just rolled back to 2.3.5.30 so hopefully that fixes it. I've had these for 6 months and they've been nothing but trouble. I now unplug them and plug my laptop directly into my cable modem when working from home as they are too unreliable for work.
As for the factory reset after a firmware upgrade... That is just ridiculous that it should be a requirement for the Orbi to work without issues. Can you imagine if you had to do a factory reset after every firmware upgrade on your smart phone? People would lose their minds.
