NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Can't static route on netgear firewall between two vlans on a netgear switch
Can someone take a lot at the screenshots and let me know what I'm doing wrong? This should be really quick and simple but I can't seem to get it to work. I have a created two port-based vlans (vla...
Whilst June is correct in saying the firewall does not support VLANs, I'd be very surprised if it can't do what you're asking of it - I've done something very similar with an FVS336Gv1 and an FVS338.
First - make sure you're using "multi-homing" on the firewall and you have both the 192.168.1.x & 192.168.10.x networks configured on the firewall's LAN interface - I don't see this screen in your screen shots.
Second - make sure the switch port that the firewall is connected to is on both VLANs if it's a port VLAN, and for an 802.1Q VLAN make sure it's an untagged (edge) port - this is also not shown in your screen shots.
You could also try having two completely separate port VLANs (no shared port) and connect each VLAN to the firewall with it's own cable.
Third - your static routing screenshot shows TWO static routes - only ROUTE2 is required.
There is also another potential problem area - for some reason, you have chosen not to have the firewall at it's default 192.168.1.1 address, possibly because you have another firewall at that address - if this is the case, there will probably be a default route on your PCs pointing all "non 192.168.1.x" traffic to that device (including your 192.168.10.x traffic), which will then forward it to the internet, so that it never hits the FVS336G.
First - make sure you're using "multi-homing" on the firewall and you have both the 192.168.1.x & 192.168.10.x networks configured on the firewall's LAN interface - I don't see this screen in your screen shots.
Second - make sure the switch port that the firewall is connected to is on both VLANs if it's a port VLAN, and for an 802.1Q VLAN make sure it's an untagged (edge) port - this is also not shown in your screen shots.
You could also try having two completely separate port VLANs (no shared port) and connect each VLAN to the firewall with it's own cable.
Third - your static routing screenshot shows TWO static routes - only ROUTE2 is required.
There is also another potential problem area - for some reason, you have chosen not to have the firewall at it's default 192.168.1.1 address, possibly because you have another firewall at that address - if this is the case, there will probably be a default route on your PCs pointing all "non 192.168.1.x" traffic to that device (including your 192.168.10.x traffic), which will then forward it to the internet, so that it never hits the FVS336G.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
