NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
M4300/M4200 Inter-VLAN routing not over default gateway
I'm having some issues working out Inter-VLAN routing. I've doing a simple test config with 2 VLANs (80 and 90) and trying to ping between 1 device located on each VLAN. My routing IP's in the swit...
Still, we talk of a static IPv4 routing environment. There is no "magic" inter-VLAN routing. So either the two test systems have the connected VLAN-IP as the default gateway, or the effective default gateway has working static routes to the other subnet. Based on the switch config only, we can just guess.
If you could provide some better guidance it would be appreciated. I'm trying to test this in a sandbox network here. In some cases I'll have a gateway connection from this switch to the internet, in many cases I won't. I'm looking for how to use the L3 features of the switch so that I can establish routing between the two VLANs whether I have an external gateway present or not...
sblair wrote:
I'm looking for how to use the L3 features of the switch so that I can establish routing between the two VLANs whether I have an external gateway present or not...
In this case the direct connected VLAN IPv4 address must be the default gateway configured on the connected systems.
The "Inter-VLAN" routing does not work on some dynamic or protocol analysis - it must be configued on all systems properly.
The system connected to the VLAN with the 192.168.80.0/24 subnet must use 192.168.80.254 for the default gateway.
The system connected to the VLAN with the 192.168.90.0/24 subnet must use 192.168.90.254 for the default gateway.
The point is that the IP stack say on a system with the example IP 192.168.80.123 can either communicate with addresses on the same subnet (so 192.168.80.0/24) - any other traffic will be sent to the default gateway.
The point is that the IP stack say on a system with the example IP 192.168.90.234 can either communicate with addresses on the same subnet (so 192.168.90.0/24) - any other traffic will be sent to the default gateway.
That's static IPv4 routing. Your switch must become a core part of the IPv4 routing. Anything he can't handle then can be sent ahead to the "next hop" gateway, e.g. to the Internet.
So let me be very clear here in what I'm trying to test. I have 1 switch here, the config file for it is in the first post. I have 2 VLAN's I've created in addition to VLAN1. VLANs 80 and 90. Networks are 192.168.80.0/24 and 192.168.90.0/24 respectively.
PC 1: is in VLAN80. Static IP is: 192.168.80.201 255.255.255.0 192.168.80.254
PC 2: is in VLAN90. Static IP is: 192.168.90.200 255.255.255.0 192.168.90.254
PC1 can ping both gateways: 192.168.80.254 and 192.168.90.254.
PC2 can ping both gateways: 192.168.80.254 and 192.168.90.254.
PC1 can NOT ping PC2.
PC2 can NOT ping PC1 either.
There should not be anything else I'm aware of I would need to configure on the client PC's since I do have proper gateways set.
Can you please provide a sample config file for this simple example that would allow PC1 to ping PC2 and vice-versa across 2 different VLANs?
Thanks.
Scott
Scott,
sblair wrote:
There should not be anything else I'm aware of I would need to configure on the client PC's since I do have proper gateways set.
What is "proper gateway set" in your opinion? If this translates to your common Internet router LAN IP - afraid, then it's wrong, and you have to re-think how static IPv4 routing does work please.
-Kurt
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
