NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New Online Update 4.6.3.16 (RBR850/RBS850)
Just did a downgrade from 4.6.3.9 to 3.2.18.1, factory resetted and I see Netgear are pushing an update automatically to 4.6.3.16. (see attached screenshot) This firmware is not available as an o...
FURRYe38 wrote:v3.2.11.2 was last version with telnet in the debug.htm UI.
jayeshm wrote:Thanks.
I will throw it up in my guest room and see how it holds up for a few days.
Just for checking, if one has to stick with a 3.xx firmware which one do you personally recommend?
Firstly thanks for all the help furry. You have been patiently helping everyone here, and while i was being sarcastic earlier, your help is much appreciated.
Using PFsense i threw up on an old nuc, i was able to block all updates and manually shift to 3.2.18xx which is the last v3 update. So far it seems to work. Taking your advice i reset them entirely, kept them off for half a day, and then plugged them back in and added them back. I think one of my satellites is a bit wonky, since it oddly loses connection once in a while, but the rest of them seem to be holding up fine.
I have been able to successfully block updates via pfsense, since whenever i check via firmware updates manually, it gives a connection error. I looked up all the names suggested here in the various threads and added all of them to a small blocklist.
I set up opendns and was able to block all firmware updates by blocking
| http.fw.updates1.netgear.com |
I tried to block using a custom DNS, but it still ended up updating. How long have you been running v3 firmware with the OpenDNS solution?
Are you blocking with the telnet solution or a router or blocking device in front of the RBR?
GoldenRetroGame wrote:
I tried to block using a custom DNS, but it still ended up updating. How long have you been running v3 firmware with the OpenDNS solution?
I was blocking by taking my provider's router out of gateway mode and using the block list on that. I had to stop that, as their router mode has a bunch of issues that cause be trouble with connections I make for work.
For now, I've stopped using the Orbi, as the V4 firmware is way too unreliable. I've gone back to my older Asus AI Mesh setup and have been waiting for an Orbi update that fixes this mess. If a fix isn't available soon, my Orbi is going up on eBay.
I tried blocking all of these addresses on my Fios Router (my Orbi is in AP mode) to no success. When I go to the webpages below, I get a blocked message, so I know something is working.
I'm wondering if the file is getting cached on the RBR or already was there prior to you blocking.
No sure if a factory reset could clear that out and try again?
Or something isn't being blocked right on your host router...
Very well could be something my router is not blocking....the parental controls on the fios router don't seem that robust. Perhaps it only blocks http/https and not ftp? Today my connection was dropping randomly. I robooted the fios router, did the factory reset again (on version 4.6.3.13) & brought up everything one at a time. The interfaces are still not consistant between the web and app, and still not showing devices connected to one of my satellites (even though if you log into each satellite, they show connections). My telnet access did not survive the factory reset. The saga continues......
I just put my 850 back online at main home router. Connected the RBR first and setup it up.
CAX80 in modem only mode. Rebooted when RBR was turned ON and connected.
Manual channels 1 and 40. 100% power output. WMM enabled on both radios, CTS at 64 and AX mode enabled on both radios. I may disable AX mode on 2.4Ghz since I don't have anything that uses AX mode on 2.4Ghz.
Armor not enabled and already expired on Orbi app.
Traffic Meter enabled and set to None.
No SPC seen on Orbi app. Yet.
After RBR was online and up and running, I turned on each RBS while in same room as RBR one at a time. I noticed that the RBRs web page reported the RBS initially as being wired, when I had NOT connected them via ethernet. Odd behavior seen here. After RBS were connected wirelessly, I set a IP addres reservation for each at .149 and .150. My DHCP is 192.168.0.1 and range is .100 to .150. After IPs were reserved. I powered OFF The RBS and place them in there remote locations. Powered them on 1 at a time. Both are ONLINE and both reading 5G wireless on the RBRs web page and wireless in Orbi app. Both RBS show connected devices as well as the Orbi app showing same. Though "unknown" devices are seen on the RBS web pages. :smileyfrustrated:
Wired PC connected to RBR speeds:
WIreless Speed with a ASUS GT-AX11000 in wireles bridge mode connected to a RBS:
RBR Onboard speed test results:
Going to leave this run for a few days.
I'm dredding to see what my 3rd gen NEST is going to do. :smileyembarrassed:
What firmware are the 8 series on furry?
No **bleep** sherlock N3tworkDud3
I was asking what FIRMWARE he has on his particular ones, since we have all been DOWNGRADING across the forums.
NO REALLY THANKS MORON.
Your too funny.
I had v16 on. Went down to v3 to see if all that worked. Kind of a hassle but it does work. I then updated back to v16 using the update ALL button on the RBR. Powered OFF, then back ON. I had the system off for a couple of weeks as Ive been tasked testing other systems. FInally wanted to put the 8 series back online and see what or if I saw any problems with it being live again. So far, system has been stable since. Only saw one RBS loop thru front LED which was solved by ethernet connection for a while then back to wireless connection. No more front LED loops.
Even my 3rd gen NEST is stable. No low battery problems.
jayeshm wrote:
What firmware are the 8 series on furry?
Thanks.
I will throw it up in my guest room and see how it holds up for a few days.
Just for checking, if one has to stick with a 3.xx firmware which one do you personally recommend?
If you have a host router that you can block updates with, then you could use last v3 version, if you don't have a up stream router to block with, then you need to use,,,great, now I can't find the specific version, it was either V3.2.15.25 or v3.2.11.2 as one of these has telnet still enabled in the debug page that you can use the telnet process to block FW updates on the RBR. I'll check this again when I get him as I marked which files had telnet and which one didn't.
jayeshm wrote:
Thanks.
I will throw it up in my guest room and see how it holds up for a few days.
Just for checking, if one has to stick with a 3.xx firmware which one do you personally recommend?
jayeshm wrote:No **bleep** sherlock N3tworkDud3
I was asking what FIRMWARE he has on his particular ones, since we have all been DOWNGRADING across the forums.
NO REALLY THANKS MORON.
Ok then, couldn't believe you were asking that question which is why I started with "Really??" Let me help you with an english lesson that may assist you with getting responses in the future:
"What firmware are the 8 series on furry?" As the only sentence in your post without reference to anythign else, should have been "What firmware are on YOUR 8 series, Furry? That YOUR is an important part of the communication. One may otherwise think you are asking waht the latest 8 series firmware availabilty is - such as what may have been released on the 7 series is now available on th 8 series.
See - that's civil. Not hard. No need to react the way you did. Oh - and I'm not downgrading, it's a pain in the ass. The better option is replacement with another brand NOT owned by Netgear or any partent or subsidiary thereof.
Seeing something odd lately: I notice after several hours my devices no longer have IPV6 access. I can reboot my entire network - router, switch, modem - and the problem persists. The only way to clear it is to go into the Orbi admin and reset the IPV6 connection type to auto and let it update the settings. After that, my PC will show IPV6 internet access. I did this early this morning and by noon, IPV6 was dead again. It could be the Orbi, the modem, or just Xfinity mucking around doing something. Anyone else seeing anything like this?
You'd have to connect a PC to the modem with out the RBR online to see if same thing happens there.
Did the just start happening today? If so, possible ISP issue...
bullm00n wrote:
Seeing something odd lately: I notice after several hours my devices no longer have IPV6 access. I can reboot my entire network - router, switch, modem - and the problem persists. The only way to clear it is to go into the Orbi admin and reset the IPV6 connection type to auto and let it update the settings. After that, my PC will show IPV6 internet access. I did this early this morning and by noon, IPV6 was dead again. It could be the Orbi, the modem, or just Xfinity mucking around doing something. Anyone else seeing anything like this?
FURRYe38 wrote:You'd have to connect a PC to the modem with out the RBR online to see if same thing happens there.
Did the just start happening today? If so, possible ISP issue...
bullm00n wrote:Seeing something odd lately: I notice after several hours my devices no longer have IPV6 access. I can reboot my entire network - router, switch, modem - and the problem persists. The only way to clear it is to go into the Orbi admin and reset the IPV6 connection type to auto and let it update the settings. After that, my PC will show IPV6 internet access. I did this early this morning and by noon, IPV6 was dead again. It could be the Orbi, the modem, or just Xfinity mucking around doing something. Anyone else seeing anything like this?
Not sure how that would work with a PC, plus major disruption to do that. I have no idea how long it's been going on - I'd never know unless I check the PC's network status which I don't normally do unless there's an issue. Yesterday, some sites were acting slow, so that's what prompted me to look and noticed I had no ipv6 connection. I'll keep a closer eye on it - it's odd that rebooting everything doesn't help - it's like the RBR needs to "renegotiate" its ipv6 connection with the modem/ISP and must be made to do it on the admin page.
Instead of rebooting everyhing, try a full power OFF of the ISP modem and RBR for 1 minute then back ON.
You'll need to see when this happens and if it does again, try a wired PC connected to the modem to see if the problem happens there as well. Might ask the ISP if they see any odd things in this area between them and you in there logs when you notice this. Keep track of time frames and dates. If nothing happens on the ISP or Modem side, could be a FW issue. Not the first time IPv6 is been a problem. :smileyfrustrated:
bullm00n wrote:
Not sure how that would work with a PC, plus major disruption to do that. I have no idea how long it's been going on - I'd never know unless I check the PC's network status which I don't normally do unless there's an issue. Yesterday, some sites were acting slow, so that's what prompted me to look and noticed I had no ipv6 connection. I'll keep a closer eye on it - it's odd that rebooting everything doesn't help - it's like the RBR needs to "renegotiate" its ipv6 connection with the modem/ISP and must be made to do it on the admin page.
N3tworkDud3 wrote:
jayeshm wrote:No **bleep** sherlock N3tworkDud3
I was asking what FIRMWARE he has on his particular ones, since we have all been DOWNGRADING across the forums.
NO REALLY THANKS MORON.
Ok then, couldn't believe you were asking that question which is why I started with "Really??" Let me help you with an english lesson that may assist you with getting responses in the future:
"What firmware are the 8 series on furry?" As the only sentence in your post without reference to anythign else, should have been "What firmware are on YOUR 8 series, Furry? That YOUR is an important part of the communication. One may otherwise think you are asking waht the latest 8 series firmware availabilty is - such as what may have been released on the 7 series is now available on th 8 series.
See - that's civil. Not hard. No need to react the way you did. Oh - and I'm not downgrading, it's a pain in the ass. The better option is replacement with another brand NOT owned by Netgear or any partent or subsidiary thereof.
Firstly shut up and mind your own business. This question is directed at another user; you lack the comprehension to discern facts and understand that little nuance. Secondly, an English language lesson is the ultimate bourgeois move. When people like you don't have anything to add to a discussion, you will descend into pedantic posting like this for self-validation.
Hint you are not adding anything to this discussion. So be on your merry way before you make yourself look further like a fool and a troll.
FURRYe38 wrote:v3.2.11.2 was last version with telnet in the debug.htm UI.
jayeshm wrote:Thanks.
I will throw it up in my guest room and see how it holds up for a few days.
Just for checking, if one has to stick with a 3.xx firmware which one do you personally recommend?
Firstly thanks for all the help furry. You have been patiently helping everyone here, and while i was being sarcastic earlier, your help is much appreciated.
Using PFsense i threw up on an old nuc, i was able to block all updates and manually shift to 3.2.18xx which is the last v3 update. So far it seems to work. Taking your advice i reset them entirely, kept them off for half a day, and then plugged them back in and added them back. I think one of my satellites is a bit wonky, since it oddly loses connection once in a while, but the rest of them seem to be holding up fine.
I have been able to successfully block updates via pfsense, since whenever i check via firmware updates manually, it gives a connection error. I looked up all the names suggested here in the various threads and added all of them to a small blocklist.Oh i forgot to add, for now my network is staying on my old Unifi gear. That's very stable but i will gradually introduce the 4.6xx firmware to the orbis and see if they settle down. I am guessing netgear will issue a fix for this sooner than later.
Some people don't understand the concept of ABC conversations. LOL Your good man.
Glad the blocking worked for you. Should keep your system from dating until NG comes out with a fix. :smileyembarrassed:
Yes the system should report either Services Not Reachable or an error when checking for FW updates. Means it's blocked.
jayeshm wrote:
Firstly thanks for all the help furry. You have been patiently helping everyone here, and while i was being sarcastic earlier, your help is much appreciated.
Using PFsense i threw up on an old nuc, i was able to block all updates and manually shift to 3.2.18xx which is the last v3 update. So far it seems to work. Taking your advice i reset them entirely, kept them off for half a day, and then plugged them back in and added them back. I think one of my satellites is a bit wonky, since it oddly loses connection once in a while, but the rest of them seem to be holding up fine.
I have been able to successfully block updates via pfsense, since whenever i check via firmware updates manually, it gives a connection error. I looked up all the names suggested here in the various threads and added all of them to a small blocklist.Sorry if this is totally obvious but you need to reboot all your clients (computers, phones...) after the system reboot to ensure that you have sticky ipv6. At least that's what works for me.
Just wanted to get back after running it in homelab for a few days.
It's been not very stable, but oddly when i switched it entirely to AP (i setup a pfsense in front to block updates) it has been running like a champ.
RBR - 3.2.18xx - DNS issues persistent but i am using an intel nuc to route it so it stays okay. Very hesitant to upgrade to 4.6xx series till i see someone give me an all clear on this. I know you have been able to get it working, but only a daily basis most people are unable to get it to stay working consistently.
TLDR;
FURRYe38 wrote:Some people don't understand the concept of ABC conversations. LOL Your good man.
Glad the blocking worked for you. Should keep your system from dating until NG comes out with a fix. :smileyembarrassed:
Yes the system should report either Services Not Reachable or an error when checking for FW updates. Means it's blocked.
jayeshm wrote:Firstly thanks for all the help furry. You have been patiently helping everyone here, and while i was being sarcastic earlier, your help is much appreciated.
Using PFsense i threw up on an old nuc, i was able to block all updates and manually shift to 3.2.18xx which is the last v3 update. So far it seems to work. Taking your advice i reset them entirely, kept them off for half a day, and then plugged them back in and added them back. I think one of my satellites is a bit wonky, since it oddly loses connection once in a while, but the rest of them seem to be holding up fine.
I have been able to successfully block updates via pfsense, since whenever i check via firmware updates manually, it gives a connection error. I looked up all the names suggested here in the various threads and added all of them to a small blocklist.Thanks for letting us know. I'd keep v3 running for now.
jayeshm wrote:
Just wanted to get back after running it in homelab for a few days.
It's been not very stable, but oddly when i switched it entirely to AP (i setup a pfsense in front to block updates) it has been running like a champ.
RBR - 3.2.18xx - DNS issues persistent but i am using an intel nuc to route it so it stays okay. Very hesitant to upgrade to 4.6xx series till i see someone give me an all clear on this. I know you have been able to get it working, but only a daily basis most people are unable to get it to stay working consistently.
