NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Routing with a VLANS - changing subnets
I inherited a network on a weird internal subnet (100.100.100.x) the gateway (issued by Windows DHCP server) for clients is a firewall and the switch isn't currently used for routing. I want t...
Here is a quick network diagram which may help visualise this better.
I would like to have a follow up on this thread. Please let us know if everything works ok now or you still need further assistance.
Regards,
Hi there,
I was on holiday for the last week, so I've just got back today, My switch is a NETGEAR GS752TPSB
When I try to tell the netgear to route VLAN 121 to VLAN 1 I get a message.... that I'm not allowed to set up a route on the management vlan. So I tried to change the management VLAN to 100, and set all ports to be untagged on vlan 100 and now I can't manage my switchthrought http OR through the SmartCenter I've a feeling I should have set it to tag vlan 100 rather than untagged, or configured a port with a PVID of 100.I don't suppose you can suggest a fix to this other than a factory reset and restoring the latest backup of my settings.
ThanksChanging the management VLAN will definitely result to unaccessible UI if it is not properly configured. Management VLAN pertains to the VLAN where you can only access the admin page. If you change the Management VLAN to 100, then you can only access the admin page if the computer that you are using is under VLAN 100. Routing is not supported on the switch that you have. You may need to do the routing from your firewall and not from the switch. You may reset the switch to factory default in order to access the admin page again.
Regards,
Hi John,
I've got that sorted, I'm now a the stage where I have the following setup. I want my Netgear stack to be my router, not my firewall. And I want to separate equipment out on to different subnets and VLANs and have all the 10.12 subnets and the 100.100.100.x co-existing. Once the migration of equipment to the new subnets is complete (this may take several weeks). I will remove the 100.100.100.x subnet.VLAN 1 - 100.100.100.x (all equipment currently on this network) Netgear Stack 100.100.100.5 and Firewall 100.100.100.222
VLAN 99 - DMZ (Stack on 10.12.99.254, firewall on 10.12.99.1)
VLAN 100 (Management VLAN)
VLAN 121 - 10.12.1.x - New Subnet and VLAN for PCs and Laptops
VLAN 122 - 10.12.2.x - New Subnet for production equipment.
VLAN 123 - 10.12.3.x - New Subnet for Servers
I am now at the stage where 10.12.x.x subnets can see the 100.100.100.x network and get internet access fine. However, the 100.100.100.x network can't see the 10.12.x.x subnets.
I've uploaded a screen shot of the routing table.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
