Orbi MR 2.1 Update 3/23/18

Are you using the iPad Pro 9.7? That is the only device I'm having issues with disconnecting, so I'm not sure if it's the iPad going bad, or the Orbi.

I'm running 2.1.2.18 on my RBR50 + RBS50 (2) and 2.1.2.20 on my RBS50Y.

In a few days, I'm getting my internet speed upgraded from 50Mbps to 1Gbps. I'd like to start using wired backhaul to take advantage of the increased speed from my ISP. What firmware version should I look to upgrade to?

Thanks. Wonder if the iPad Pro 9.7 has something in its Wi-Fi chip that the Orbi doesn't like? It's kinda driving me crazy at this point. Usually a reboot of the iPad fixes it.

Try disabling the following and see:

Beamforming, MIMO, Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Save settings and reboot the router.

Try upgrading to a Beta version of FW and see if this does anything different?

---

turns2stone wrote:

Are you using the iPad Pro 9.7? That is the only device I'm having issues with disconnecting, so I'm not sure if it's the iPad going bad, or the Orbi.

 

I'm running 2.1.2.18 on my RBR50 + RBS50 (2) and 2.1.2.20 on my RBS50Y.

 

In a few days, I'm getting my internet speed upgraded from 50Mbps to 1Gbps. I'd like to start using wired backhaul to take advantage of the increased speed from my ISP. What firmware version should I look to upgrade to?

---

Hi all,

I've put my Orbis back in service and I've installed the latest 2.1 firmware, it's been running for a maybe a week now.

Last night the Orbi router stopped responding while watching a movie.

But this time I saw it was rebooting, I think this is also what has happened at least once before and matches with what others in this thread have seen.

This is almost certainly a kernel crash.

My question is, do any of the logs that support request contain kernel back traces if there are any?

It's next to impossible to resolve problems like this without such a trace and even very hard with one.

Ian

Thanks, I will give that a try.

So I got Ethernet backhaul working. Question: Should all wireless devices now show their connected to the Orbi Router? When I was using Wireless backhaul, each device near the satellite would show they were connected to it. Now 100% off my wireless devices show connected to the Router.

---

Bullyterrier wrote:
In case anyone from Netgear is here I have this iPad internet blocked after sleep issue open as case 29999148 and am happy to gather debug info if required. The support rep asked where I obtained the beta so I replied today re this thread. The rest of the response was not helpful in progressing the issue.

---

So yor not using an RBR50 or RBS50?

The firmware for those is available on the Netgrear support site.

wireless devices when connected should show connected to the satellite when there connected there. If there connected to the router, they will show at the router.

---

turns2stone wrote:

Thanks, I will give that a try.

 

So I got Ethernet backhaul working. Question: Should all wireless devices now show their connected to the Orbi Router? When I was using Wireless backhaul, each device near the satellite would show they were connected to it. Now 100% off my wireless devices show connected to the Router.

---

Did you factory reset the router and Satellite(s) after you upgraded to v2.1.3.4? This needs to be performed for this version of FW.

---

raven_au wrote:

Hi all,

 

I've put my Orbis back in service and I've installed the latest 2.1 firmware, it's been running for a maybe a week now.

 

Last night the Orbi router stopped responding while watching a movie.

 

But this time I saw it was rebooting, I think this is also what has happened at least once before and matches with what others in this thread have seen.

 

This is almost certainly a kernel crash.

 

My question is, do any of the logs that support request contain kernel back traces if there are any?

 

It's next to impossible to resolve problems like this without such a trace and even very hard with one.

 

Ian

---

OK that's what I thought.

Turns out, wired backhaul is just too unstable for me. The entire network crashes! I'm running 2.1.3.4 on RBR50 and RBS50 (x2) and 2.1.2.20 on the RBS50Y.

Did I need to do a full factory reset? That seems like a major pain. 

Is there a FW update for the RBS50Y? Might be a problem here.

There any networks switches between the satellites and router?

Please factory reset the router and RSB50 units then set up from scratch.

My wired back haul is working fine. You have to give it time to reconfigure for the new connection?

Are you connecting all satellites at the same time for wired or doing one at a time and giving it 5 minutes to reconfigure?

Others are reporting success after a factory reset and set up from scratch:

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

---

turns2stone wrote:

OK that's what I thought.

 

Turns out, wired backhaul is just too unstable for me. The entire network crashes! I'm running 2.1.3.4 on RBR50 and RBS50 (x2) and 2.1.2.20 on the RBS50Y.

 

Did I need to do a full factory reset? That seems like a major pain. 

---

Yeah, this is a mess.

I factory-reset EVERYthing. Brought the router back up, it found the outdoor satellite no problem. Everytime I try to sync a wired satellite, the entire network crashes as its being setup. It’s almost like the router figures out its wired backhaul and just pukes.

When setting up wired back haul, are you first setting up the satellite via wireless and is it working at this stage? It should be. Then connect the LAN cable between the router and satellite and give 5 minutes before you check the network? It needs a good 5 minutes. Yes the network may seem to stop working, however give it time. After 5 minutes it should be stable and working. Do one Satellite at a time. 

Possible that there is something wrong with the satellite in this configuration. Something to contact NG support about if you can't get it working on LAN back haul. Others including me have wired back haul working...

---

turns2stone wrote:

Yeah, this is a mess.

 

I factory-reset EVERYthing. Brought the router back up, it found the outdoor satellite no problem. Everytime I try to sync a wired satellite, the entire network crashes as its being setup. It’s almost like the router figures out its wired backhaul and just pukes.

---

---

FURRYe38 wrote:

Did you factory reset the router and Satellite(s) after you upgraded to v2.1.3.4? This needs to be performed for this version of FW.

---

 

---

Yes, all Orbis were factory default reset and configured from scratch, it happened less than 24 hours afterwared.

There's more, the device I was using might have been connected via an RBS40 satelite with 2.1.3.6 to my RBR50, unfortunately I hadn't checked.

Are you able to answer the question I asked?

---

raven_au wrote:

---

FURRYe38 wrote:

Did you factory reset the router and Satellite(s) after you upgraded to v2.1.3.4? This needs to be performed for this version of FW.

---

 

---

Yes, all Orbis were factory default reset and configured from scratch, it happened less than 24 hours afterwared.

 

There's more, the device I was using might have been connected via an RBS40 satelite with 2.1.3.6 to my RBR50, unfortunately I hadn't checked.

 

Are you able to answer the question I asked?

---

Also, I've enabled Circle.

Can you disable Circle and see if the problem still happens while watching a movie? 

How are you watching movies? What kind of device? Mfr and model#? Thisdevice wired or wireless when watching movies? 

As far as logging, not sure about the logs. You might enable them and send them to your email address and check them out. 

---

raven_au wrote:

---

raven_au wrote:

---

FURRYe38 wrote:

Did you factory reset the router and Satellite(s) after you upgraded to v2.1.3.4? This needs to be performed for this version of FW.

---

 

---

Yes, all Orbis were factory default reset and configured from scratch, it happened less than 24 hours afterwared.

 

There's more, the device I was using might have been connected via an RBS40 satelite with 2.1.3.6 to my RBR50, unfortunately I hadn't checked.

 

Are you able to answer the question I asked?

---

Also, I've enabled Circle.

---

---

@@FURRYe38 wrote:

Can you disable Circle and see if the problem still happens while watching a movie? 

How are you watching movies? What kind of device? Mfr and model#? Thisdevice wired or wireless when watching movies? 

---

The device was an Apple TV 4K and in this case it was the Apple Movies app.

I have had the impression in the past that certain devices wireless can cause problems, such as NUC D54250WYK, and connecting that via ethernet cable resolved my problem at the time. I've done the same thing for this particular Apple TV 4K, I've left my other one as wireless to see what will happen but I'll have to wait until it gets more use.

I find now that others in my household have had what appears to be a disconnection problem over the last several days, I've asked them to check if the router is rebooting when it happens and let me know. AFAICT this was while using an Apple TV (previous version to the 4K). I hadn't had problems with Apple devices previously so this is curious. The Apple devices have all updated to 11.3 now, I believe, certainly the Apple TV are all on this version of tvOS.

I'll check disabling Circle if the problem continues and it sounds like I'll need to work out if the kernel back trace gets captured in the log myself. Often they happen to quickly to be captured in the logs and one needs to connect a serial cable to the router to get the backtrace.

I've got several usb serial devices but I don't want to pull my Orbi appart, assuming there is a serial interface on the board. Perhaps there is some other way to get serial access to the Orbi, anyone?

Thanks. I got one satellite connected via Ethernet using this method. But can't get a second. It just shows connected via 2.4Ghz and shows Backhaul status as "Poor", even though Ethernet is connected.

A couple of things that helped me (not sure if they are all needed)

Factory reset
set up wireless connection to satellites first then move to wired location
Network connection to router should be to one of the lan ports
Turn off diasy chain
Turn off IGMP snooping on your managed switch

I'm running stable w/ correct reporting of "good" "wired" connection in the GUI

---

FURRYe38 wrote:

When setting up wired back haul, are you first setting up the satellite via wireless and is it working at this stage? It should be. Then connect the LAN cable between the router and satellite and give 5 minutes before you check the network? It needs a good 5 minutes. Yes the network may seem to stop working, however give it time. After 5 minutes it should be stable and working. Do one Satellite at a time. 

 

Possible that there is something wrong with the satellite in this configuration. Something to contact NG support about if you can't get it working on LAN back haul. Others including me have wired back haul working...

---

turns2stone wrote:

Yeah, this is a mess.

 

I factory-reset EVERYthing. Brought the router back up, it found the outdoor satellite no problem. Everytime I try to sync a wired satellite, the entire network crashes as its being setup. It’s almost like the router figures out its wired backhaul and just pukes.

---

 

---

So do you have a managed switch? Whats the Mfr and model# of your switch please.

So disabling IGMP snoop seems to help on managed switches? This is good info. Was hoping there is something on these switches to help users that have them.

Thanks for letting us know. Will pass this on.

---

srgb111 wrote:

A couple of things that helped me (not sure if they are all needed)

Factory reset
set up wireless connection to satellites first then move to wired location
Network connection to router should be to one of the lan ports
Turn off diasy chain
Turn off IGMP snooping on your managed switch

I'm running stable w/ correct reporting of "good" "wired" connection in the GUI

---

 

 

---

---

srgb111 wrote:

A couple of things that helped me (not sure if they are all needed)

Factory reset
set up wireless connection to satellites first then move to wired location
Network connection to router should be to one of the lan ports
Turn off diasy chain
Turn off IGMP snooping on your managed switch

I'm running stable w/ correct reporting of "good" "wired" connection in the GUI

---

FURRYe38 wrote:

When setting up wired back haul, are you first setting up the satellite via wireless and is it working at this stage? It should be. Then connect the LAN cable between the router and satellite and give 5 minutes before you check the network? It needs a good 5 minutes. Yes the network may seem to stop working, however give it time. After 5 minutes it should be stable and working. Do one Satellite at a time. 

 

Possible that there is something wrong with the satellite in this configuration. Something to contact NG support about if you can't get it working on LAN back haul. Others including me have wired back haul working...

---

turns2stone wrote:

Yeah, this is a mess.

 

I factory-reset EVERYthing. Brought the router back up, it found the outdoor satellite no problem. Everytime I try to sync a wired satellite, the entire network crashes as its being setup. It’s almost like the router figures out its wired backhaul and just pukes.

---

 

---

 

---

Thanks. I did all that, except for turning off daisy chain. So maybe that's the source of the problems?

It's a GS108Ev3, two actually.  I have two sats - I set them both up with wireless backhaul.  I then connected a wired backhaul for the first sat - this went through one GS108Ev3.  After a short period it showed wired backhaul.  I then connected the second, this time it was going through 2 switches - I waited for 1/2 hour or more with no joy.   I then turned off IGMP snooping on both switches - for no good reason other than I've tried everything else...shortly after this change the second sat connected.  From what I could read this shouldn't have made any difference, but the change resulted in the Sat showing up wired and I've been good since that point in time.  

Now that I'm stable I don't want to tear it down to test if the IGMP snooping really was the key...

---

FURRYe38 wrote:

So do you have a managed switch? Whats the Mfr and model# of your switch please.

So disabling IGMP snoop seems to help on managed switches? This is good info. Was hoping there is something on these switches to help users that have them.

Thanks for letting us know. Will pass this on.

 

---

srgb111 wrote:

A couple of things that helped me (not sure if they are all needed)

Factory reset
set up wireless connection to satellites first then move to wired location
Network connection to router should be to one of the lan ports
Turn off diasy chain
Turn off IGMP snooping on your managed switch

I'm running stable w/ correct reporting of "good" "wired" connection in the GUI

---

 

 

---

 

---

---

srgb111 wrote:

It's a GS108Ev3, two actually.  I have two sats - I set them both up with wireless backhaul.  I then connected a wired backhaul for the first sat - this went through one GS108Ev3.  After a short period it showed wired backhaul.  I then connected the second, this time it was going through 2 switches - I waited for 1/2 hour or more with no joy.   I then turned off IGMP snooping on both switches - for no good reason other than I've tried everything else...shortly after this change the second sat connected.  From what I could read this shouldn't have made any difference, but the change resulted in the Sat showing up wired and I've been good since that point in time.  

 

Now that I'm stable I don't want to tear it down to test if the IGMP snooping really was the key...

 

 

---

Did you turn off Daisy Chain on the RBR50, as well?