NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New - RBK752/753 Firmware Version 4.6.3.7 Released
Security Fixes: Fixes security vulnerabilities. For more information about security vulnerabilities, visit https://www.netgear.com/about/security. New Features and Enhancements: Supports Smart...
***Updated: 9/13/2021 11:50 AM PT
Hello Orbi Community,
Please accept my apologies for any delay in getting this message to you. I have been advised that an official firmware release is in the final stages of internal testing and in the process of being posted to our support site. Likely, within the next 24 hours.
To get this firmware release now please click the link below:
For instructions on how to manually download this firmware please visit:
How do I manually upgrade firmware on my Orbi router using orbilogin.com?
Thank you for your patience,
ChristineT
My Samsung TV will not connect to the internet now after the firmware just updated tonight. I checked and my TV will easily connect to my iPhone hotspot. Any ideas how to fix this issue? The DNS was set to 8.8.4.4 prior to the firmware update.
I just got off the phone with NETGEAR support and the problems appears to be with the firmware on the Satellite. When we disconnected the satellite from power and TV attached directly to the router the tv immediately connected to the internet. They said it would be a problem until a firmware update is release.
Thanks for letting us know.
cpmassen wrote:
I just got off the phone with NETGEAR support and the problems appears to be with the firmware on the Satellite. When we disconnected the satellite from power and TV attached directly to the router the tv immediately connected to the internet. They said it would be a problem until a firmware update is release.Follow-up on loss of wireless connectivity in this buggy firmware release...
I can confirm that disabling AX seems to help the issue I was having with the current firmware where I would lose connectivity when the endpoint transitioned between the router and the satellite. Of course, one of the reasons I bought this router in the first place was specifically for AX support, so this is a huge disappointment. This firmware release is simply an all-around disaster. If you have an earlier firmware version, do NOT update.
Thanks for confirming this. NG is aware of the problems and also recommended disabling AX mode as well. Lets all hope the next FW update fixes this. Please be patient.
- With all due respect and I mean this because you have been helpful to so many on this board, I am not sure anyone has patience for a fix from Netgear. It took them one update to screw up a network I had spent hours tweaking and adding devices to. It was perfectly fine, they knew the problems well in advance from the comments and feedback before the automatic update, but they did it anyway. I feel like I spent hours building the perfect sandcastle only to have oaf walk through it carrying his cooler and beach chairs, then looking back and saying, “my bad, I will come back and help you fix it - just give me a minute”.
For me, that is unforgivable and I am starting over with a Unifi system and taking this back to Costco.
I will say that for those of you that are trying to fix it, the folks on the chat app seem much more competent than the ones on the phone. However, after an hour of getting kicked off chat (because it now kicks me off my network every few minutes) and then talking to incompetents on the phone, I threw in the towel. Easier to set up something entirely new than to deal with this. After 20 years of owning various Netgear products because in my mind they were a good brand, I won’t be back. So I thought I would chime in here after spending what has now amounted to days worth of time trying to sort out some stability. I have actually discovered some interesting quirks, which might be helpful to other, or helpful to netgear in a fixed firmware.
1. I ended up turning off the AX channels, although I don't really think this led to an increase in stability.
2. I am running the 2437 CTX/RTX, but again I also don't think this had anything to do with it.
I think there is a serious problem with the DHCP which is causing the issues.
Now for the kicker. I am a Verizon FIOS customer and my Orbi sits after the FIOS Gateway. By default the FIOS gateway takes IP range 192.168.1.XXX, and it needs to be there to receive from the modem and pass on. As with all firmwares, I typically used 192.168.85.XXX as my gateways on my Orbi, but after changing to this every time my stability went horrid. So I started letting netgear keeps its 10.0.0.XXX gateway it defaults to when it sees something else has the 192.X gateways. Again, my stability was trash. So I started looking at logs and digging in to issues. The #1 problem I saw was that somehow my satellites were giving out IPs in the 192.168.1.XXX family, and were also setting themselves to this, despite the fact this is NOT listed as an acceptable DHCP range on the Orbi at all. So.....
I went into the Verizon router and set it to 192.168.0.XXX, and I set a static IP for my Orbi, and gave it the 192.168.1.XXX DHCP range that would be the default if the Verizon router had not been there. I set up 1 satellite, and put everything on the 4.x firmware. It has been running with 100% stability for around 3-4 days now with zero out of sync errors or drop outs in service.
I can't say with total certainty that this is what is causing all the issues, but after going back and forth and testing against this ~4 times to see stability I think something is messed up in the firmware where if your DHCP range is anything but the default range there are some serious issues with the satellites maintaining the DHCP ranges of the router. It seems like if the satellite gets out of sync it reverts to the 192.168.1.XXX range, while the router maintains the original range, and then all the devices get confused and end up connected with invalid IPs and yea.... everything goes downhill very quickly :smileysad:
- Can confirm this as well. Post update, all of my devices were assigned 10.0.0.1 IP addresses. I just completed a factory reset and now back to 192 ip range and everything is working including my air print issue. Net gear pushed this update to sell a new product shame on them for not thoroughly testing this. They have a beta program or should.
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?
intergeek14 wrote:
Can confirm this as well. Post update, all of my devices were assigned 10.0.0.1 IP addresses. I just completed a factory reset and now back to 192 ip range and everything is working including my air print issue. Net gear pushed this update to sell a new product shame on them for not thoroughly testing this. They have a beta program or should.- How did you log into your ONT?
Mine is Calix 711GE ONT
My connection is 900/900 symmetrical Sorry , I'm confused, can you walk me through what you did here? My connection to my sattalites have been HORRIBLE and constantly dropping.
I have Verizon FIOS and an ONT. My Orbi has always been 192.168.1.1 and all the devices 192.168.1.X .
Specifically, my use router as DHCP server is checked and the range is 192.168.1.2 to 192.168.1.254
It seems like you changed your settings to what I already have and mine does not work. Maybe I'm misunderstanding what you changed ?
Thank you!
The user only changed the IP address of the RBR from 192.168.1.1 to 192.168.1.100. I don't believe this will be impacting whats happening. However you might change the following as listed as well here:
"4. Advanced - Wireless Settings - unchecked “20/40 mhz coexistence”
- Enable WMM for 2.4 and 5ghz both checked
- CTS/RTS threshold to 2347 for both 2.4 and 5g
- Transmit power for 2.4g to 25% and 5g to 100%"
ahswp wrote:
Sorry , I'm confused, can you walk me through what you did here? My connection to my sattalites have been HORRIBLE and constantly dropping.
I have Verizon FIOS and an ONT. My Orbi has always been 192.168.1.1 and all the devices 192.168.1.X .
Specifically, my use router as DHCP server is checked and the range is 192.168.1.2 to 192.168.1.254
It seems like you changed your settings to what I already have and mine does not work. Maybe I'm misunderstanding what you changed ?
Thank you!
Thank you I will try this.
I'm beyond unhappy with Netgear. Shouldn't take a month of people complaining to fix this. They should offer a way to downgrade in the meantime.
I'm on the verge of returning these to Costco and going with another solution.
