Wow!!! Orbi Firmware V2.0.0.72 Released

I crossed my fingers and I've upgraded to v2.0.0.72. Everything seems to be working just like before, which is fantastic! I have all manner of 23 devices connected within the house. 

Upgrade went well. My only problem is that I am unable to edit the VLAN ID tag. It defaults to name "internet" and Id of "10" but the ISP I use here in Australia (TPG on HFC cable) requires VLAN Id tag of 2. It doesnt allow me to edit the value, just stays stuck on the 10.

Has anybody else have same problem? Need to get this sorted out so can use the Orbi in Router mode and not in AP mode.

---

Mikey94025 wrote:

My upgrade to 2.0.0.72 did not lose my old settings.  My port forwarding, etc. all stayed put.

 

The new firmware lets you change the wireless power settings again, so you can set 2.4Ghz transmit power control to 100% / 75% / 50% / 25%.

---

i was coming from a modded downgrade to 1.11.0.20 so perhaps they saw it fit that mine needed a complete wipe. :D  

SO far so good!

Anyone testing out Live Parental Controls? I still get the "There was an error signing in, pleae make sure you're connected to the Internet and try again." that started showing up around 1.11.0.20

Are we allowed to finally use the Implicit Beamforming feature?

i have it enabled here and no issues , also have mu-mimo enabled

---

cyberprashant wrote:

---

Mikey94025 wrote:

My upgrade to 2.0.0.72 did not lose my old settings.  My port forwarding, etc. all stayed put.

 

---

i was coming from a modded downgrade to 1.11.0.20 so perhaps they saw it fit that mine needed a complete wipe. :D  

---

I was coming from 1.11.0.20 also...  Looks like some people may lose their settings but it's not clear which scenarios apply.

Is there a listing somewhere of everything that was updated/fixed?   Netgear doesn't seem to have that updated on the site.  

---

morrisseysb wrote:

Is there a listing somewhere of everything that was updated/fixed?   Netgear doesn't seem to have that updated on the site.  

---

This is from a Mod with links to individual files:

https://community.netgear.com/t5/Orbi/OrbiOS-2-0-availability/m-p/1368730#M13446

peteytesting thanks for the feedback. so we can assume that "Explicit" Beamforming is part of this Firmware and on by default correct? AND now we are OK to turn on "Implicit" Beamforming since bugs fixed so older devices/adapter cards can take advantage of this feature? 

Is there any actual documentation available on what "fast roaming" actually is?  (Realistically, if it was a Magical Unicorn, it wouldn't be a selectable option and would always be on, so I'd quite like to know what it actually does.)

Rodney

Version 2 is working great for me, more speed than version 1. Maxing out my 300 mb connection. I'm using AP mode. Turned off mesh mode since my orbi is in the middle of my two bridge AP's

---

rhester72 wrote:

Is there any actual documentation available on what "fast roaming" actually is?  (Realistically, if it was a Magical Unicorn, it wouldn't be a selectable option and would always be on, so I'd quite like to know what it actually does.)

 

Rodney

---

yes, would be nice to know when to enable this.  

Also is there any way to know if router is using daisy chain topology (I have 2 satellites in a triangle sort of shape) - not sure which is better to have - checked or unchecked.  I'm going to try unchecking it. 

---

cyberprashant wrote: 

Also is there any way to know if router is using daisy chain topology (I have 2 satellites in a triangle sort of shape) - not sure which is better to have - checked or unchecked.  I'm going to try unchecking it. 

---

I believe you should be able to tell from the attached devices list. Each device shows which Orbi it's connected to.

In the Attached Devices section, the last column Connected Orbi should show what the upstream Orbi is.  If it is connected to another Orbi Satellite, then it's Daisy Chain.  

After seeing this I put my Orbi back in place and upgraded.

I was pleased to see I didn't get an error (for satelites) on the "Firmware Update" page now.

I wasn't pleased to find my existing problem was not fixed (I essentially have one ongoing problem).

But then I haven't made any noise about it.

That problem is with an Intel NUC with an AC7260 wireless card.

The NUC is using Plex Media Player which means LibreELEC 8.0 underneath.

It may be the Intel Open Source driver but this has woked with a fairly large range of other routers so I think it should be fixed by Oualcomm and by extension Netgear. Given I had similar problems with the D7800 I believe this has been a problem for quite a while.

Because of the problem with the Intel wireless I put another router into media bridge mode and also had problems with stalls and disconnects. I used an RT-AC3200 with the previous firmware version and I have an EA8500 in place now and saw this same problem with both. I would have expected the Qualcomm based EA8500 to work fine with the Orbi Qualcomm wireless, that is odd!

But using a non-broadcom bridge isn't ok with the Orbi either, it sees only one device which changes IP address from time to time between the router and connected device making it really hard to get the assigned IP address of the player. Yes, there are workarounds assigning a fixed address to it but I shouldn't have to do that.

TBH I was thinking of just ripping it out again and I still might, but after seeing this thread I "might" perform a factory reset and re-configure before giving up "again".

---

st_shaw wrote:

---

cyberprashant wrote: 

Also is there any way to know if router is using daisy chain topology (I have 2 satellites in a triangle sort of shape) - not sure which is better to have - checked or unchecked.  I'm going to try unchecking it. 

---

I believe you should be able to tell from the attached devices list. Each device shows which Orbi it's connected to.

---

awesome! - they've really added a lot of useful info to the attached devices page.  I can see that even with daisy chain enabled I'm connected in star topology - that is each satellite appears to be connected ot the base.   And you're right can see which device connects to which satellite or router (including the satellites themselves). 

Roaming (AP or band) is a two way series of messages betwen AP (Orbi) and client (iphone, laptop, etc), and the Orbi's algorithm to ask a device to roam is based on reading various metrics (e.g. RSSI / SNR).  In an effort to give you a bit more control on how you want your Orbi to function, we've given you a lever to tune it.  This is really designed for the more advanced user.  

If you tune Fast Roaming to be "faster" then the Orbi will be more active in asking the client to roam to a different AP or band.  The beneift of this is that the client will more often be in a more optimum situation (higher signal strength / faster speed).  However, the downside is that sometimes this could result in a more disconnects or flip-flopping between two relatively equal situations.    

If you tune it to be "slower", then the Orbi won't be as active in asking clients to roam and leave things in a "good enough" state.  Clients will probably be in more stable situations, but potentially in the not as optimal connection, for example connected to the further AP.  

Play around with it and see what suits you best

Orbi Product Team

---

AmitR wrote:

... we've given you a lever to tune it. ...  If you tune Fast Roaming ...

Amit, can you please explain more about this "tunable lever" for Fast Roaming (FR)? 

I know where the Fast Roaming checkbox is in Advanced/Wireless, and I noticed a new additonal roaming-related checkbox on the Satellite Debug page, but I haven't seen anything that's "tunable"...  

When I hear that term, I think of a slider-bar or something like that, so I'm wondering if you can please provide more details about how we can tune FR to be "faster" or "slower".

I initially had the FR option checked, but then I kept dropping wifi calls as a walked around my house., so I know have it unchecked.  I haven't made any calls yet, but I'm hoping that will solve the wifi-calling drops for me.

Thank you, Amit - we appreciate your help here in the forums!!

Chris