Alternatives to orbi?? (considering replacing already)

So with your assistance i've managed to downgrade from V4.6.3.16_2.0.51 to V3.2.18.1_1.4.14

things appear to be working now... (famous last words!!) I'm going to monitor it over the next couple of days and report back. 

Ok keep us posted maybe buy the weekend or next week...

---

stu3886 wrote:

So with your assistance i've managed to downgrade from V4.6.3.16_2.0.51 to V3.2.18.1_1.4.14

things appear to be working now... (famous last words!!) I'm going to monitor it over the next couple of days and report back. 

---

---

stu3886 wrote:

So with your assistance i've managed to downgrade from V4.6.3.16_2.0.51 to V3.2.18.1_1.4.14

things appear to be working now... (famous last words!!) I'm going to monitor it over the next couple of days and report back. 

---

You may want to go one more step back.  I BELIEVE that's the one that was giving a lot of people DNS issues (if using as router) and why they came out with the now infamous v4 firmware (that's even worse).

Of course, if you have that version and it's running as AP behind another router, DNS is a non-issue.since it will be the main router handling DNS.

Wish i knew that before i spent the time downgrading. thanks for the heads up though. fortunately for now I'm in AP mode. 

Is there a specific stable recommend firmware?

this one is still glitchy, notifications on mobile can take time to come through and devices don't appear to connect to nearest satellite, they still connect to the orbi router meaning a decrease in speeds when not close to the router.

You can double check the old posts, but I BELIEVE the 3.2.18 had DNS lookup issues for a lot of people (but NOT ALL), which prompted NG to come out with the v4.

So the least problematic would be one step back at 3.2.17.

Be aware though, if you're NOT using a firewalled/protected router ahead of the Orbi, I recall what prompted the .18 update was a known vulnerability for many NG routers (not just Orbi).

IT's up to devices to pick and choose where they connect too. Some may not have good roaming features as well.

Try turning down the power output of the RBRs wifi radios from 100% to 50% and see if this changes anything. Under Advanced Tab/Advanced Settings/Wireless Settings

If your in AP mode, you'll be fine on what you have loaded.

---

stu3886 wrote:

Wish i knew that before i spent the time downgrading. thanks for the heads up though. fortunately for now I'm in AP mode. 

 

Is there a specific stable recommend firmware?

 

this one is still glitchy, notifications on mobile can take time to come through and devices don't appear to connect to nearest satellite, they still connect to the orbi router meaning a decrease in speeds when not close to the router.

---

---

stu3886 wrote:

Wish i knew that before i spent the time downgrading. thanks for the heads up though. fortunately for now I'm in AP mode. 

 

Is there a specific stable recommend firmware?

 

this one is still glitchy, notifications on mobile can take time to come through and devices don't appear to connect to nearest satellite, they still connect to the orbi router meaning a decrease in speeds when not close to the router.

---

didn't notice you're in AP.  if you're running it as AP, just stay where you are since your main router does the DNS so the DNS issue is NOT going to be a problem (unless your router has a DNS issue as well).

there was a problem with dnsmasque that affected a lot of brands (not just NG/Orbi).  I don't remember if it was just a security issue, or if it was a combo of security and query issue.  whatever it was (it was a year or two ago), most every brand fixed/moved on from the problem.

my PERSONAL theory at  the time was that NG uses a modified dnsmasque to sniff DNS queries for data gathering.  When they tried to fix it, it borked the thing entirely which gravy trained in to v4.

UPDATE:

So I manged to get it downgraded to V3.2.18.1_1.4.14 last week. it was glitchy to say the least with satellite and router drop outs but at least when it was up stuff was loading. 

NG support advised that after any firmware downgrade they recommend a factory reset. (wish I never listened to them!!!)

Anyway... did the factory reset and it tried to do the FW upgrade as part of the setup. i exited out of the app and wherever possible clicked skip. 

Fastforward to today and guess what... The orbi has automatically upgraded its own firmware back to V4.6.3.16_2.0.51 :smileymad:

I had blocked the site address "devcom.up.netgear.com" on my sky q hub as well, but this clearly hasn't blocked the FW update coming through.

back to square one with a useless paperweight of a system!!!! 

The more I read about this orbi the more I understand why NG has so many angry customers.

resets are sometimes a necessary troubleshooting step. Someting to try as it can and has recolved various problems. Others have mentioned that it has worked for them as well. Something to listen too. But of course, you don't have too. 

---

stu3886 wrote:

UPDATE:

 

So I manged to get it downgraded to V3.2.18.1_1.4.14 last week. it was glitchy to say the least with satellite and router drop outs but at least when it was up stuff was loading. 

 

NG support advised that after any firmware downgrade they recommend a factory reset. (wish I never listened to them!!!)

 

Anyway... did the factory reset and it tried to do the FW upgrade as part of the setup. i exited out of the app and wherever possible clicked skip. 

 

Fastforward to today and guess what... The orbi has automatically upgraded its own firmware back to V4.6.3.16_2.0.51 :smileymad:

 

I had blocked the site address "devcom.up.netgear.com" on my sky q hub as well, but this clearly hasn't blocked the FW update coming through.

 

back to square one with a useless paperweight of a system!!!! 

 

The more I read about this orbi the more I understand why NG has so many angry customers.

 

 

---

So i have downgraded again to V3.2.18.1_1.4.14 and everything appears to be working ok again... but the app has an "Update" button... clearly I wont be pressing this ever. 

But I'm assuming if that's there its just going to force another automatic update on me? :(

Any other way I can prevent these forced automatic updates?

Do you have a router or ISP modem with a built in router in front of the RBR? 

I have a sky q hub Er115 which has built-in modem and router. 

I have the wireless on it turned off and use the orbi in AP mode for my wifi.

Potentially upgrading to fttp next week and getting the latest Sky Q Hub SR203UK

Check to see if your ISP modem/router has blocking or firewall rule features where you can block certain host names or host IP addresses. 

If it does then you can load up last working v3 version of FW for your orbi AX and block the auto updates from happening with the modem/router.

---

stu3886 wrote:

I have a sky q hub Er115 which has built-in modem and router. 

 

I have the wireless on it turned off and use the orbi in AP mode for my wifi.

 

Potentially upgrading to fttp next week and getting the latest Sky Q Hub SR203UK

---

it does have the option to put firewall blocks in place, but only via IP. do you know what IP's need blocking? 

Try 13.225.0.117

thanks, is that http or https? or something else?

currently I've got it as HTTP, so it's 13.225.0.117 (80)

Usually TCP or UDP or ANY. Not sure what your ISP modem supports. 

Try just the IP only and see if the modem accept it. Or does it required a HTTP something? 

When you test this out, have the RBR online and go to it's FW update page, select on Check Updates. The status should return "service not reachable" if you have the up stream router configured right to block. 

Yep i was able to select "Any" so hopefully that solves it.

Put that IP address in WAN servers. 
I think for LAN you can put the IP address the RBR is getting from the modem here. 

Should be all thats needed. 

Hopefully this is looking correct now...

Yes, apply that and then check for FW updates on the RBR. You should see service not reachable. 

looks like it hasnt worked :(

Current Firmware Version V3.2.18.1 and in the status column for the RBR and RBS its showing V4.6.3.16

Add this address to the list as well:

52.42.72.107

Exit the page or navigate off that page then go back and check again. 

If your not seeing service not reachable, I presume the modem isn't blocking correctly. I have tried the first IP and it does work when I block it thought I don't have same modem/router you have. You might ask your ISP if these are correct input usage settings for there modem/router to block to be sure.