NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi Mesh system (1+2) from Costco with latest firmware 2.3.5.30
Just bought my first Wifi Mesh system which is Orbi Mesh system (1+2). A great deal from Costco, but as soon as I upgraded to latest firmware 2.3.5.30, it became garbage. It disconnects often an...
Yes, did reset twice and reloaded the firmware. It was of no help. Same choppiness.
I downgraded to last fw version 2.3.1.60 and evaluating the performance this week.
Let us know how it turns out.
What is the distance between the router and satellite(s)? 30 feet is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected.
What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
singhravik wrote:Yes, did reset twice and reloaded the firmware. It was of no help. Same choppiness.
I downgraded to last fw version 2.3.1.60 and evaluating the performance this week.
FURRYe38 wrote:Let us know how it turns out.
What is the distance between the router and satellite(s)? 30 feet is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected.
What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
singhravik wrote:Yes, did reset twice and reloaded the firmware. It was of no help. Same choppiness.
I downgraded to last fw version 2.3.1.60 and evaluating the performance this week.
Good trouble shooting practice allows to make one change (FW revision) and determine the results. Then IF necessary look else where.
Isn't this FREE QA (quality testing) by consumers post release! too bad !
I'll avoid Netgear next time.
I hated the NightHawk for same reason.. poor quality and too much on consumers to try out.
singhravik wrote:Isn't this FREE QA (quality testing) by consumers post release! too bad !
I'll avoid Netgear next time.
I hated the NightHawk for same reason.. poor quality and too much on consumers to try out.
I believe what you'll find is that NO FW is perfect and ALL manufacturers such as NG are faced with the same problem. You're best bet is if you can find a FW that works for you and keeps your system stable, stay there, don't upgrade. When a new FW does becomes available, read the release notes first to understand what changes are offered. Good luck
Both the satellites are under 30ft of distance from router. Teh building material is dry-wall over wood frame (no concrete or metal).
Channels are all Auto. Should they adjust the channel per lowest noise. This was advertised as such.
Getting a poll on succes of 2.3.5.30 would be good idea. Can we do that?
IF the RBS is under 30 feet then is probably too close. 30 feet is recommended in between RBR and RBS to begin with depending upon building materials when wirelessly connected.
Wifi signal over lap is important. On any FW version.
I have my one out at 40 feet.
Any Wifi Neighbors near by? If so, how many? If you have some near by, I would manually adjust channels far appart from wifi neighbors as best as you can. I have a next door nieghbor, I mean right next door and there Orbi works on 6 and 48. I have to set channel 1 and 36 on my system.
You might try setting the power level on the RBR from 100% to 75 or 50% if you do have lots of neighbors near by. This helps reduce the interference from neighbors with your signal and adjusts the foot print of the wifi coverage. How much out side single do you really need out side the home?
Some of these issues can cause false positives on any FW. Placement and configuration of the system is key, regardless of FW version.
singhravik wrote:Both the satellites are under 30ft of distance from router. Teh building material is dry-wall over wood frame (no concrete or metal).
Channels are all Auto. Should they adjust the channel per lowest noise. This was advertised as such.
Getting a poll on succes of 2.3.5.30 would be good idea. Can we do that?
v2.3.1.60 as well as 2.3.5.30 had the same issue with Satellite connectivity. I used to do the following to get around this issue:
- Switch off the Satellite
- Go to Attached Devices in the web GUI and click on the "Disconnect" button beside the Satellite in questions
- Turn on the Satellite and use a paper clip to factory reset the Satellite
- When the Satellite is up after factory reset, press the Sync button on the Satellite (if you have wired backhaul then keep the Ethernet cable to the Router connected while doing the sync) and then press the Sync button on the Router
- When the Satellite is added after this procedure it should behave correctly.
Good luck!
