NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
bug
3 TopicsBUG: Cannot edit "Internet" VLAN settings (e.g. Priority, VLAN ID)
Router Firmware Version V2.0.0.74 Steps to reproduce: 1) Sign in to orbilogin.com (or whatever method) 2) Click the "Advanced" tab 3) Expand the "Advanced Setup" section in the left list, then scroll down within the list until you see "VLAN/Bridge Settings". Click "VLAN/Bridge Settings". 4) Click "Enable VLAN/Bridge group" and then "By VLAN tag group". 5) Highlight the existing/default "Internet" VLAN tag group and click "EDIT" 6) Change the VLAN ID (e.g. to 201, as I need to do for CenturyLink Fiber internet). 7) Click "APPLY" Expected results: VLAN tag group page is shown with the new settings specified above. Actual results: VLAN tag group page is shown with old settings; any changes are not respected/retained/saved. Using the exact steps above, the entire VLAN settings are disabled / not enabled. If you already have VLAN settings enabled, then the "Internet" group will simply remain in VLAN ID 10 -either way, it is uneditable. Looking for Netgear help here, as this seems to be a bug in their firmware or router settings. Also very interested if others can reproduce, or whether this is just my device.SolvedOrbi Access Control Firmware 1.3.0.12
I just updated my Orbi Router and Satellite to the latest firmware, 1.3.0.12. I'm using Access Control to limit access to the network. I have a Tivo Mini hooked up to the ethernet port of the satellite, and it was connected and allowed to network access before the firmware update. Now when I enter access control, the Tivo Mini shows as "blocked", and even if I select the device and click "allow", it stays blocked. That's the first issue. The second issue is that it's not actually blocked (nor do I want it to be). It's able to connect to the network and access the internet just fine. I tried to block and unblock it and it didn't work. Not sure what the issue could be except a firmware bug.Can not create a static route to single IP (Orbi 2.0.0.74)
When adding a static route to a single IP it is not applied. I'm trying to block access to certain IP's by adding static routes and directing them to the local interface on the Orbi. I enter the IP, Subnet 255.255.255.255, Gateway 10.0.0.1 and Metric 2. I press apply but it does not. Does not show up in the list of static routes. (10.0.0.1 is the Orbi's internal IP) If I enter the same IP and a 24bit subnet (255.255.255.0). Press apply and it is applied and saved. Shows up in the list of static routes.