NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New - RBR750 / RBS750 Firmware Version 4.6.5.14 Released
Enhancements:
Adds support for the RBS350
Security Fixes:
Fixes security vulnerabilities.
For more information about security vulnerabilities, visit https://www.netgear.com/about/secu...
WOW, this morning about 2am i decided to update my two ORBI RBS satillites first. and that went ok, till a fantom ORBI showed up in my Orbi App. i then proceeded to update the RBR750, that went well till it said it was online but it wasnt. i followed the directions according to Furrye38, (ty) and i unplugged the sats and then the router, waited 2-3 minutes then i plugged in the router and then the sats and waited........it took a few minutes and the router came online then the sats followed. it still took some time for all my devices to get back on line (about 60), which is normal thing that has been happening. then today was the test. we had some heavy thunderstorms roll in, these south florida storms alway knock out some power or damages some weak transformers to were the power goes on and off real quick. it happened 3 times in a half hour i also have the comcast modem and the RBR750 plugged into a surge and battery back up. the weakest like here is the sats, no battery-back up for them and they used to take forever to re-sync but after the upgraded firmware last night, WOW, the ORBI's came right back online which shocked me, i thought i would need to reboot the sats. but no input from me and the whole system came back online quick. i am no IT guy here but this is a major inprovement from the previous firmware that almost killed the ORBI system. thanks to all here on this forum, i have learned alot from here.
converge2 wrote:Like many others here I started to get issues with dropouts with recent 4.* firmware updates.
Been super stable for at few days so I thought I write down what I did.
Dropouts were basically reconnects from satellite to main Orbi. I'm in AP mode behind a pfsense box (Netgate 3100).
Tried giving everything that's running 24/7 a static IP and permanent ARP table entry. Thought it fixed it, but drops came back.
Ethernet connecting as much as possible. Still drops (WiFi devices only, Ethernet rock stable).
Factory reset + manual reconfigure. Again, good for a day, but then came back.
Satellite is only about 25-30ft from base, so I thought devices might get confused (although they never have been in the past). Set the transmission power to 25% for 2.4 and 50% for 5Ghz. Coverage still good (should have been a nicer neighbor and done earlier) but still drops.
Removed AX for 2.4. Still dropping.
Removed multi media setting for 2.4 and set the channel from auto to 1 (1 is what my Mac WiFi diagnostics recommended). Rebooting everything in the network. Stable!
Jinxing it by posting here. TBD.
Updating to say that while it seems slightly more stable, I'm not convinced that the settings changes make a huge difference in my case. So don't want to send anyone down rabbit holes. I got an Ethernet cable fix for the most annoying drop case, the others I can live with for now and hope future updates make the Wifi more stable.
converge2: firmware issues with 4.* are widely documented here. If you want stability downgrade to 3.* This is the only thing that worked for me, after wasting days to try to make 4.* fw work.
If you can reutur the system, I suggest you do so and buy a different brand. Otherwise, I recommend trying to go back to 3.*
If you can reutur the system, I suggest you do so and buy a different brand. Otherwise, I recommend trying to go back to 3.*
FW issues widely documented by those who speak the loudest. I have had ZERO issues with firmware 4.X. I just checked and I have been up 36 straight days, without one outage, drop or anything. So for many of the silent majority, the firmware has not been an issue.
I fired up my system on Sept 11. After a solid week of no issues, my wifi did drop out, two days in a row, every 24 hours. To me it lined up with DHCP renewal. So the one and only change I did was to establish a static ip for the router hanging of my Fios router and then told the orbi to use said static ip. Came back up, hasn't been down since (did have a power outage 36 days ago). I even was bold enough to upgrade the firmware of the satellite while I was 90 miles to the east at the beach. No issues. Not saying what I did was the magic bullet, but it has worked for me. In this configuraion I have experenced two FW upgrades, again resulting in no downtime or adverse performance. No idea why some expereince so many issues, but for me, Orbi has performed as advertised.
- Counterpoint: i run a "samKnows" Comcast service monitor, which tracks public network speed and disconnections. The only device between the SamKnows box and the cable modem is the Orbi RBR750 - and last week, I had 122 service disconnections. I have had Comcast monitoring my cable modem for the past month, and there has only been 1 observed disconnect between them and my cable modem... so the Orbi is the culprit. Wish it weren't so, but it is.
Could you explain a bit more about how you use SamKnows? (Is there a device? A cost?)
I have experimented a bit with PingInfoView, a program that sends ICMP packets to a user created list of IP's every 30 seconds and records whether responses are received or not. I ping all of the major DNS servers (Google, CloudFlare, OpenDNS, Quad Nine, CleanOpenBrowsing). Since ICMP is based on UDP packets which do not guarantee delivery, the premise is that missing a response here or there is not unusual, but if all of the DNS servers fail to respond (especially several times in a row) then there must have been a service interruption. This obviously might not detect a service interruption of less than 30 seconds. I have run a test for up to a week and found nothing that indicated a break in service through my old RBR50 router and Spectrum internet.
My interest is academic (SamKnows), and not related to the central topic (RBR750 firmware release). On that issue, I remain flummoxed by the situation that some Orbi customers are nearly "dead in the water" and desperate while other customers with apparently the same equipment experience no problems at all. This seems to be the case with almost every Orbi model. Maybe SamKnows uses a technology that provides different measurements and I might want to compare it against my current practice.
Thanks
Mr410 wrote:FW issues widely documented by those who speak the loudest. I have had ZERO issues with firmware 4.X. I just checked and I have been up 36 straight days, without one outage, drop or anything. So for many of the silent majority, the firmware has not been an issue.
Although I do not have the issues cited in this thread, since I operate my Orbi as AP and have updates blocked (currently static at v3), I fail to see any statistic that the MAJORITY of users do not have the claimed or similar issues. One could easily say that the majority do have issues, but are not posting in this forum, or just lurk to find answers.
I lurk in various forums quite a bit for answers to issues I may be having with electronics, automotive, appliances, etc., etc., etc. I rarely post myself if I am able to find answers by lurking/searching on the internet - even if the (current) answer is that there is no fix at this time.
I think this thread already shows that, for those that HAVE posted here in the forums, for most of THESE users, there is a Orbi FW issue. However that doesn't mean that some users who have not posted, this doesn't mean others may or may NOT have issues. I've seen something as little as a factory reste and setup from scratch help some. We also can NOT discount the ones that have posted and say they have not had problems, unlike the majority. I'm also in the minority as well. My 7 series has worked well for many weeks with out seeing problems that don't reflect what the majority is seeing. However this is NOT about the majority or minority. NG ALREADY KNOWS ABOUT THE PROBLEMS in FW. This subject and discussing is a dead horse. All we can do is to help those that are having problems here in the forums with suggestions and alternatives, UNTIL NG gets this fixed. Fixes DO NOT happen over night. And just because this seems to be on long ongoing problem, doen't mean they don't care. Other mititgating factors like COVID and work place changes over the past two years maybe playing a part in this as well. Do ASSUME anything. So were here to help as best as we can until the fix comes out. For those users who don't want to wait or can't, please return your system and go find something that does work. For those who can't return your unit, try the suggstions here in the forums and also contact NG support and let them know about what your experiencing. Otherwise, everyone will have to be patient while we ALL wait for NG to get things fixed.
Have a nice day.
