NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Cannot access web management interface from a routed VLAN
Model 4100 G12D Firmware 10.0.0.1.28 I am having issues managing the web gui interface from a routed vlan. I have the switch configured with layer 3 vlans, and it is working fine. This is follow...
Still cannot get the management vlan to change to a Layer 3 vlan, regardless of what RFC1918 address I use. However, I can now access the webgui from any of the ip addresses of the routed vlans, so there is no need to configure the management vlan to be accessible from any of the routed vlans. The issue was local to some of the pc's, these addresses had to be exempt from the proxy configuration for local LAN access.
Thanks for your time and patience resolving this issue.
Thanks for your prompt reply. I took ports 0/1-2 out of VLAN 1 (default) and assigned them to VLAN 4, which is a 192.168.4.0/24 subnet. I plugged a laptop in port 0/1 and I can now access the web interface at 192.168.4.1(I had tried this before I posted)However, another pc plugged into another port in the same vlan cannot access the webgui, but can connect via ssh to 192.168.4.1
However, when I change the Management VLAN ID to a current VLAN, I get the error message "IP Address/Netmask entered cannot be used on a routed vlan" I also tried creating another Layer 2 vlan first, without any ip addresses. I then changed the management vlan Id to this new vlan. I had already added the pvid's and ports as you suggested before I changed the management vlan id. I then added an ip address to the vlan and got the same error message as before, "your ip address/subnet conflicts with an existing subnet range on an existing vlan"
Maybe I am doing something wrong here to change the management vlan id--
many thanks for your help
Hi bignewf93,
I suggest you to set the management VLAN on a different LAN IP segment that is different from the usual LAN IP network since this works to others. For example: if the VLANs you have such as 192.168.0.x or 192.168.4.x, then set the management VLAN to 10.0.0.x and check if same error message will appear.
Hope it helps.
Regards,
DaneA
Netgear Community Team
- Should I create another routed vlan in the 10.X.X.X. subnet range first and then change the vlan PVID to this routed vlan, or just change the web management interface ip first to a 10.X.X,.X subnet , then create a routed vlan in that subnet, then change the management vlan id of 1 to the new routed vlan pvid?
Thanks for your help
Hi bignewf93,
You may create another VLAN, let say for example: VLAN10 which is going to be within the 1010.0.0.x subnet range. Then assign port(s) to VLAN10 then change the port PVID to 10 then change the management VLAN to VLAN10. Lastly, make sure to set the IP Address to the 10.0.0.x subnet range.
Test it by connecting a PC to the port(s) assigned on VLAN10 and check that the PC is within the 10.0.0.x subnet range and you should be able to get a reply when you ping the IP Address you have assigned on the switch.
Regards,
DaneA
Netgear Community Team
Thanks again. I will give that a try.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
