- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- « Previous
-
- 1
- 2
- Next »
Access control issue/bug with Orbi 2.7.1.60
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Access control issue/bug with Orbi 2.7.1.60
Will do. I've tried to downgrade but the Orbi auto-updated itself back to current version. I attempted to disable auto update the hard way (via telnet) and things got a little wonky so I'm probably not going to do that...I'm perfectly comfortable doing stuff like that but it just didn't seem stable after I flupped the auto-update settings. Would be nice if auto-update was an option in the UI.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Access control issue/bug with Orbi 2.7.1.60
You can see if this works:
1) Go to Advanced, Security, Block Sites and add the following sites.
http.fw.updates1.netgear.com
updates1.netgear.com
downloads.netgear.com
Kept digging on this and learned the following:
TCP port 443 (HTTPS): http.fw.updates1.netgear.com
TCP port 21 (FTP): updates1.netgear.com
I believe those two are all that's necessary to block. Orbi tries HTTPS first, then FTP.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Access control issue/bug with Orbi 2.7.1.60
That didn't seem to work...I woke up this morning and my FW was back on 2.7.2.104 😞
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Access control issue/bug with Orbi 2.7.1.60
I'd try a full factory reset and setup from scratch.
You might contact NG support and ask them to take your system of there auto update servers until they can fix this...
@jbrown316 wrote:That didn't seem to work...I woke up this morning and my FW was back on 2.7.2.104 😞
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Access control issue/bug with Orbi 2.7.1.60
@FURRYe38 wrote:I'd try a full factory reset and setup from scratch.
You might contact NG support and ask them to take your system of there auto update servers until they can fix this...
@jbrown316 wrote:That didn't seem to work...I woke up this morning and my FW was back on 2.7.2.104 😞
wow...why isn't this widely known..??
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Access control issue/bug with Orbi 2.7.1.60
@jbrown316 , I don't know if anyone mentioned this to you or not, but if you aren't using Armor or the other add-ons from Netgear, and are just limiting access to your network through a Byzantine password and Access Control (like me), you might want to downgrade to v2.6.1.40, the other "fork" in NETGEAR's software path. I had a hell of a time with the v2.7, and things got much better when I went back to 2.6. I'm running v.2.6.1.40 and have not been a victim of un-solicited upgrades.
But a word of warning: Don't use the iOS Orbi app to manage accesses -- it seems to screw up the device database in the router (something I learned once the hard way, and foolishly repeated that mistake a week ago). I've reported the issue.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Access control issue/bug with Orbi 2.7.1.60
Thanks for the advice. I do have Armor and Circle installed so I'm guessing I should stick with 2.7 for now, but thanks again.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Access control issue/bug with Orbi 2.7.1.60
@vajim wrote:
@jbrown316 wrote:That didn't seem to work...I woke up this morning and my FW was back on 2.7.2.104 😞
wow...why isn't this widely known..??
It is not clear (to me) that the Orbi (itself) uses the Orbi DNS mechanism to reach sites such as updates1.netgear.com. There is also an issue that Block Sites works only with "http" URL's (which are rapidly becoming obsolete) and does NOT block "https". To truly block the Orbi from reaching Netgear, there would have to be a DNS server "upstream" of the Orbi.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Access control issue/bug with Orbi 2.7.1.60
Is there a way to do this without a support subscription? I just cannot stop this thing from updating. Literally every day I have to roll it back. I've tried turning off any update settings via telnet that seem appropriate.
@FURRYe38 wrote:I'd try a full factory reset and setup from scratch.
You might contact NG support and ask them to take your system of there auto update servers until they can fix this...
@jbrown316 wrote:That didn't seem to work...I woke up this morning and my FW was back on 2.7.2.104 😞
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Access control issue/bug with Orbi 2.7.1.60
@Stev3D wrote:@jbrown316 , I don't know if anyone mentioned this to you or not, but if you aren't using Armor or the other add-ons from Netgear, and are just limiting access to your network through a Byzantine password and Access Control (like me), you might want to downgrade to v2.6.1.40, the other "fork" in NETGEAR's software path. I had a hell of a time with the v2.7, and things got much better when I went back to 2.6. I'm running v.2.6.1.40 and have not been a victim of un-solicited upgrades.
But a word of warning: Don't use the iOS Orbi app to manage accesses -- it seems to screw up the device database in the router (something I learned once the hard way, and foolishly repeated that mistake a week ago). I've reported the issue.
More of what I've been saying all along
these firmwares come out without proper testing and trial
this is been going on for a long time The ones that suffer are those that are told or they feel they MUST upgrade, to include those who fully support this madness and slam those who oppose
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Access control issue/bug with Orbi 2.7.1.60
Vajim's lack of knowledge and experience, is your mileage may vary. >vajim. User beware.
Historical posts prove it:
https://community.netgear.com/t5/Orbi/Orbi-RSR50-firmware-2-5-1-16/m-p/1903734/highlight/true#M90556
https://community.netgear.com/t5/Orbi/Problems-with-new-Orbi-RBK53-setup/m-p/1876257#M85028
https://community.netgear.com/t5/Orbi/Constant-VPN-reconnecting-since-upgrading-to-firmware-V2-5-1-8...
https://community.netgear.com/t5/Orbi/Netgear-drops-the-ball-again-RBR50-on-FW2-5-1-8/td-p/1876302/j...
https://community.netgear.com/t5/Orbi/Orbi-RBR50-was-working-amp-changed-modem-now-not-working/m-p/1...
https://community.netgear.com/t5/Orbi/Orbi-RBK50-Speeds-Drop/td-p/1891090/jump-to/first-unread-messa...
https://community.netgear.com/t5/Orbi/dropped-bandwidth-on-Orbi-RBR50-with-cm1000-modem/m-p/1901910#...
https://community.netgear.com/t5/Orbi/Orbi-RBR50-bricked-during-update-to-2-3-5-30/m-p/1897073/highl...
Sad that he has to spread false and inaccurage information and bager and troll others that are just providing help to others. Must have a sad life.
- « Previous
-
- 1
- 2
- Next »
• Introducing NETGEAR WiFi 7 Orbi 770 Series and Nighthawk RS300
• What is the difference between WiFi 6 and WiFi 7?
• Yes! WiFi 7 is backwards compatible with other Wifi devices? Learn more