NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Orbi MR 2.1 Update 3/23/18
Our teams are still working through the issues, but I wanted to provide a quick update on OrbiOS 2.1. We usually wait to release our software until it's available across all Orbi product lines, but ...
DarrenM where is the link for the RBW30 beta? I can only see 2.0.1.2 (plus older).
andygodber wrote:DarrenM where is the link for the RBW30 beta? I can only see 2.0.1.2 (plus older).
http://files.netgear-support.com/go/?a=d&i=x990UeDEdo also on the first page of this thread
BETA: A beta version of a program is an unfinished version released to either the public a select few or whoever signs up to beta test it for bugs or glitches.
Try and be patient ... it sucks but they are working on it.
Im using a newer beta for about 12 hours now ....
steve8411 wrote:Try and be patient ... it sucks but they are working on it.
Im using a newer beta for about 12 hours now ....
I've been on 2.0.14 (roll back) for nearly 2 months. Averaging disconnects once a week
- Still crappy here, drops / loss of internet connection
Do you factory reset the router after upgrading the FW and set up from scratch? This needs to be done for this version of FW.
Let us know what your seeing if you have problems with this version of FW.
steve8411 wrote:Try and be patient ... it sucks but they are working on it.
Im using a newer beta for about 12 hours now ....
How is your router, channels and satellite configured?
Distances between router and satellite?
I'm on v2.1.3 here and not seeing any disconnects.
Disconnects as is from the router, satellite, satellite disconnecting from router? Router disaconnectin from internet? client disconnecting from router or satellite?
Specifics would be helpful...
Retired_Member wrote:
steve8411 wrote:Try and be patient ... it sucks but they are working on it.
Im using a newer beta for about 12 hours now ....
I've been on 2.0.14 (roll back) for nearly 2 months. Averaging disconnects once a week
FURRYe38 wrote:How is your router, channels and satellite configured?
Distances between router and satellite?
I'm on v2.1.3 here and not seeing any disconnects.
Disconnects as is from the router, satellite, satellite disconnecting from router? Router disaconnectin from internet? client disconnecting from router or satellite?
Specifics would be helpful...
Retired_Member wrote:
steve8411 wrote:Try and be patient ... it sucks but they are working on it.
Im using a newer beta for about 12 hours now ....
I've been on 2.0.14 (roll back) for nearly 2 months. Averaging disconnects once a week
Disconnects as in the Router goes pink, while the Sats, there is no change other than the entire network is down. I'm not ready to jump back into the tweaker mode. I never touched it out of the box but set it up (Nov 17). No AP mode, modem, router, and devices. It all worked fine the first 2-3 months. So whatever is causing the disconnects I don't feel it's anything I did on my and I'm not going to start chasing rabbits.
My issues were mostly with Apple devices ... Wifi would be connected but device would not be able to access internet prompting a restart of wifi or device.
So working with support and providing logs they've furnised a new revised beta -not available- to test....
I have 30+ devices accross many platforms on my home network ...
The pink has to do with your ISP services between the router and modem. One thing I haven't seen with mine. You can't just wait around for FW to fix this. This may not be something FW can fix. Troubleshooting starts always with the ISP services and flows down. It's not always the routers fault.
I recommend that you have your ISP check the cabling going to the ISP modem, check signal levels going to the ISP modem. For DSL or Fiber service lines, ensure that the ISP is using good working phone or cable lines to the DSL modem and that the phone lines are filtered correctly. For cable Internet, RG-6 coaxial cable is needed, not RG-59. Check for t.v. line splitters and remove them as they can introduce noise on the line and lower the signal going to the ISP modem. I recommend having the ISP service physically check the lines going from the out side to the ISP modem. Connecting to the ISP modem could result in a false positive as the signal to the modem could be just enough to that point then adding on a router, could see problems. The router operation is dependent upon getting good data flow from the ISP modem and the modem is dependent upon getting good signal from the ISP Service.
Seems that your issues is particular to your configuration set up. However since you have resolved to not do anything. I guess this is all up to you. "Can lead a horse..."
Hope this helps other users who will take action if needed.Good Luck.
Retired_Member wrote:
FURRYe38 wrote:How is your router, channels and satellite configured?
Distances between router and satellite?
I'm on v2.1.3 here and not seeing any disconnects.
Disconnects as is from the router, satellite, satellite disconnecting from router? Router disaconnectin from internet? client disconnecting from router or satellite?
Specifics would be helpful...
Retired_Member wrote:
steve8411 wrote:Try and be patient ... it sucks but they are working on it.
Im using a newer beta for about 12 hours now ....
I've been on 2.0.14 (roll back) for nearly 2 months. Averaging disconnects once a week
Disconnects as in the Router goes pink, while the Sats, there is no change other than the entire network is down. I'm not ready to jump back into the tweaker mode. I never touched it out of the box but set it up (Nov 17). No AP mode, modem, router, and devices. It all worked fine the first 2-3 months. So whatever is causing the disconnects I don't feel it's anything I did on my and I'm not going to start chasing rabbits.
steve8411 wrote:My issues were mostly with Apple devices ... Wifi would be connected but device would not be able to access internet prompting a restart of wifi or device.
So working with support and providing logs they've furnised a new revised beta -not available- to test....
I have 30+ devices accross many platforms on my home network ...
...and see...not to pick on you...but this might be a case where NG continues to operate under the fix/break mode. They fix some users while all of a sudden break others. I know there are a gazillon ways to run a home network and I consider mine fairly simple (no AP, No switches, etc.) and yet it can fall victim.
all I can say..."I'm glad I bought it from Costco"
Good Luck.
May very well be why they asked me to participate ....
I have Windows, Parrot, Roku's, Apple, Android, Raspberry Pi and a host of other devices running on my network ...
How is your system configured?
What channels are you using?
Did you upgrade FW and is Beamforming, Mimo, Daisy Chain, Fast Roaming and IPv6 enabled or disable?
Whats the distance between the router and satellite?
Is 20/40Mhz Coexistence enabled?
steve8411 wrote:May very well be why they asked me to participate ....
I have Windows, Parrot, Roku's, Apple, Android, Raspberry Pi and a host of other devices running on my network ...
When doing a FW upgrade, do you lose all the labeling of devices, setup parameters? It was a ton of work just setting this thing up. It is by no means a PnP product, and I'm technically inclined...
Dear fellows in misery,
All the follwing applies only WHEN IN AP MODE!
Some relief comes from wired ethernet backhaul. I guess it is because of saved 5G bandwidth. Who knows.
However, problem was to run an extra cat 6 cable through the flat - next to the already existing LAN wired infrastructure.
Why is this an issue?
Well because the Netgear documentation - same crappy&confusing as the firmware - advises to use the yellow WAN port. Wrong.
As for ethernet wired backhaul in AP mode, use 1st LAN port - right next to the yellow one.
(no idea if this has influence but Daisychain Off, Beamforming On, MU-MIMO On, Fast Roaming On and :smileyfrustrated:Yes Yes Yes I did paper-clip factory reset the cheesy orbi router + satellite after firmware migration to 2.1.3.4)
=> this doesn't hinder Orbi junk from internet drops or lost connections but it reduces them
Cheers, Volker
PS
There is an entire thread for this:
https://community.netgear.com/t5/Orbi/Ethernet-Backhaul-Best-Practices/m-p/1486919#M21278
PPS
I also liked this reddit blog entry to find out the satellite backhaul type via telnet:
https://www.reddit.com/r/orbi/comments/7jfdhk/ethernet_backhaul_howto/
If you upgraded to v2.1.3.4, yes all settings will be erased. This is for only this version. These are beta and there are differences in FW from last version to beta. We see that other users reported continued problems after the update however didn't reset the router and set up from scratch. After doing a reset and set up again, the problems not longer appeard. Im told that going forward, NG is aware of this and next future updates users should not have to reset and set up from scratch after doing a FW update.
mmiguy wrote:When doing a FW upgrade, do you lose all the labeling of devices, setup parameters? It was a ton of work just setting this thing up. It is by no means a PnP product, and I'm technically inclined...
So did chaning from WAN to LAN port resolve your problems?
Planetom wrote:Dear fellows in misery,
All the follwing applies only WHEN IN AP MODE!
Some relief comes from wired ethernet backhaul. I guess it is because of saved 5G bandwidth. Who knows.
However, problem was to run an extra cat 6 cable through the flat - next to the already existing LAN wired infrastructure.
Why is this an issue?
Well because the Netgear documentation - same crappy&confusing as the firmware - advises to use the yellow WAN port. Wrong.
As for ethernet wired backhaul in AP mode, use 1st LAN port - right next to the yellow one.
(no idea if this has influence but Daisychain Off, Beamforming On, MU-MIMO On, Fast Roaming On and :smileyfrustrated:Yes Yes Yes I did paper-clip factory reset the cheesy orbi router + satellite after firmware migration to 2.1.3.4)
=> this doesn't hinder Orbi junk from internet drops or lost connections but it reduces them
Cheers, Volker
PS
There is an entire thread for this:
https://community.netgear.com/t5/Orbi/Ethernet-Backhaul-Best-Practices/m-p/1486919#M21278
PPS
I also liked this reddit blog entry to find out the satellite backhaul type via telnet:
https://www.reddit.com/r/orbi/comments/7jfdhk/ethernet_backhaul_howto/
This is very bad and missleading information based on a led color on a device that sounds like its crashing/malfunctioning. With all the issues netgear has it would be a waste of money to have someone come out to look. Just RMA the device or return it or RMA until netgear refunds you
FURRYe38 wrote:The pink has to do with your ISP services between the router and modem. One thing I haven't seen with mine. You can't just wait around for FW to fix this. This may not be something FW can fix. Troubleshooting starts always with the ISP services and flows down. It's not always the routers fault.
I recommend that you have your ISP check the cabling going to the ISP modem, check signal levels going to the ISP modem. For DSL or Fiber service lines, ensure that the ISP is using good working phone or cable lines to the DSL modem and that the phone lines are filtered correctly. For cable Internet, RG-6 coaxial cable is needed, not RG-59. Check for t.v. line splitters and remove them as they can introduce noise on the line and lower the signal going to the ISP modem. I recommend having the ISP service physically check the lines going from the out side to the ISP modem. Connecting to the ISP modem could result in a false positive as the signal to the modem could be just enough to that point then adding on a router, could see problems. The router operation is dependent upon getting good data flow from the ISP modem and the modem is dependent upon getting good signal from the ISP Service.
Seems that your issues is particular to your configuration set up. However since you have resolved to not do anything. I guess this is all up to you. "Can lead a horse..."
Hope this helps other users who will take action if needed.Good Luck.
Retired_Member wrote:
FURRYe38 wrote:How is your router, channels and satellite configured?
Distances between router and satellite?
I'm on v2.1.3 here and not seeing any disconnects.
Disconnects as is from the router, satellite, satellite disconnecting from router? Router disaconnectin from internet? client disconnecting from router or satellite?
Specifics would be helpful...
Retired_Member wrote:
steve8411 wrote:Try and be patient ... it sucks but they are working on it.
Im using a newer beta for about 12 hours now ....
I've been on 2.0.14 (roll back) for nearly 2 months. Averaging disconnects once a week
Disconnects as in the Router goes pink, while the Sats, there is no change other than the entire network is down. I'm not ready to jump back into the tweaker mode. I never touched it out of the box but set it up (Nov 17). No AP mode, modem, router, and devices. It all worked fine the first 2-3 months. So whatever is causing the disconnects I don't feel it's anything I did on my and I'm not going to start chasing rabbits.
FURRYe38 wrote:So did chaning from WAN to LAN port resolve your problems?
Planetom wrote:Dear fellows in misery,
All the follwing applies only WHEN IN AP MODE!
Some relief comes from wired ethernet backhaul. I guess it is because of saved 5G bandwidth. Who knows.
However, problem was to run an extra cat 6 cable through the flat - next to the already existing LAN wired infrastructure.
Why is this an issue?
Well because the Netgear documentation - same crappy&confusing as the firmware - advises to use the yellow WAN port. Wrong.
As for ethernet wired backhaul in AP mode, use 1st LAN port - right next to the yellow one.
(no idea if this has influence but Daisychain Off, Beamforming On, MU-MIMO On, Fast Roaming On and :smileyfrustrated:Yes Yes Yes I did paper-clip factory reset the cheesy orbi router + satellite after firmware migration to 2.1.3.4)
=> this doesn't hinder Orbi junk from internet drops or lost connections but it reduces them
Cheers, Volker
PS
There is an entire thread for this:
https://community.netgear.com/t5/Orbi/Ethernet-Backhaul-Best-Practices/m-p/1486919#M21278
PPS
I also liked this reddit blog entry to find out the satellite backhaul type via telnet:
https://www.reddit.com/r/orbi/comments/7jfdhk/ethernet_backhaul_howto/
It eased the pain didn't solve
Just another quick update from me, been traveling alot for work and my wife has had zero issues while I was away. SO I am now at almost 28 days with zero issues and here is a screen shot of the .debug.htm.
Hi,
Does this 2.1 beta support the 'daisy chain' ?
I have the router at topmost position in my house and I need to reach my underground garage with 2 RBS50 between at each level of the house.
(of course a RBS50 in the garage cannot reach directmy the RBR50 router and I need it to go through RBS50->RBS50->RBS50->RBR50)
Is it stable and working good ?
Regards,Kristo.
For the 50 series, yes.
Please do a factory reset after loading FW and set up from scratch if you update. It's needed on this version:
https://community.netgear.com/t5/Orbi/Orbi-MR-2-1-Update-3-23-18/m-p/1548414/highlight/true#M27868
https://community.netgear.com/t5/Orbi/speed-slows-down-Orbi/m-p/1551822/highlight/true#M28289
Kristofior wrote:Hi,
Does this 2.1 beta support the 'daisy chain' ?
I have the router at topmost position in my house and I need to reach my underground garage with 2 RBS50 between at each level of the house.
(of course a RBS50 in the garage cannot reach directmy the RBR50 router and I need it to go through RBS50->RBS50->RBS50->RBR50)
Is it stable and working good ?
Regards,Kristo.
