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 switch for each VLAN are 192.168.80.254 and 192.168.90.254.
PC #1 is set to 192.168.80.200 and PC #2 is set to 192.168.90.201. From each PC I can ping both of the .x.254 routing IP's but I can't ping either of the PC's. I did put both PC's on the same VLAN and verify that the PC's could ping each other with no issue first (i.e. no firewall issues).
I'm not sure what I'm missing in the config at this point to be able to access devices across VLANs.
This config was done on an M4200, but basically the same as M4300 from a configuration point of view which I'm also working with.
!Current Configuration:
!
!System Description "M4200-10MG-PoE+ ProSAFE 8-port 2.5 Gigabit L2+ Intelligent Edge Managed Switch with 2 10G Uplinks, 12.0.2.20, 1.0.0.6"
!System Software Version "12.0.2.20"
!System Up Time "0 days 5 hrs 4 mins 46 secs"
!Additional Packages QOS,IPv6,IPv6 Management,Routing
!Current SNTP Synchronized Time: SNTP Last Attempt Status Is Not Successful
!
serviceport protocol none
vlan database
vlan 80,90
vlan routing 1 1
vlan routing 80 2
vlan routing 90 3
exit
configure
line console
exit
line telnet
exit
line ssh
exit
!
interface 0/1
vlan pvid 80
vlan participation auto 1
vlan participation include 80
exit
interface 0/2
vlan pvid 90
vlan participation auto 1
vlan participation include 90
exit
interface 0/3
vlan pvid 80
vlan participation auto 1
vlan participation include 80
exit
interface 0/4
vlan pvid 90
vlan participation auto 1
vlan participation include 90
exit
interface 0/5
vlan pvid 80
vlan participation auto 1
vlan participation include 80
exit
interface vlan 80
routing
ip address 192.168.80.254 255.255.255.0
exit
interface vlan 90
routing
ip address 192.168.90.254 255.255.255.0
exit
router rip
exit
exit
Thanks.
Model: GSM4328S|M4300-28G - Stackable Managed Switch with 24x1G and 4x10G including 2x10GBASE-T and 2xSFP+ Layer 3
Re: M4300/M4200 Inter-VLAN routing not over default gateway
Ignore the "over default gateway" part of the subject above. It auto-suggested that from previous topics and didn't realized it entered that (I had already read through all of those hoping to find my answer but didn't....)
Re: M4300/M4200 Inter-VLAN routing not over default gateway
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.
Re: M4300/M4200 Inter-VLAN routing not over default gateway
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...
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.
Re: M4300/M4200 Inter-VLAN routing not over default gateway
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?
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.
Re: M4300/M4200 Inter-VLAN routing not over default gateway
Kurt,
As I clearly stated in the last post, each PC has a static gateway set that matches the routing interface of the single switch I have here.
Gateway Config of switch from post #1:
interface vlan 80
routing
ip address 192.168.80.254 255.255.255.0
exit
interface vlan 90
routing
ip address 192.168.90.254 255.255.255.0
exit
And as I said in the last post, the config of the 2 devices are:
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
The last set of addresses there is the Gateway IP I set in those devices statically.
As I said before this is a sandbox setup and often will NOT have any connection to the Internet, as is the case with the config right now. There is nothing in the network other than the single L3 switch and the (2) PC's. No gateway connection to the Internet.
I'm just trying to get a ping between 2 devices on different subnets on the SAME swtich.
Re: M4300/M4200 Inter-VLAN routing not over default gateway
Scott,
Can you send me the tech-support file from the switch. It looks like you've got things correct but want to see everything to see whats wrong. If you can ping one gateway on the switch you will be able to ping them all, this is just how our switch works. Get me the TS and I'll be able to figure out what we're missing.
Re: M4300/M4200 Inter-VLAN routing not over default gateway
Thanks Casey.
Here's the TS file from the M4200. It's a bit more terse in info than the latest M4300 TS files provide.
Here's the routing table for my laptop below too if it helps. All interfaces were disabled except my wired connection. Same on the other laptop. My laptop was in Port 0/4 but I pulled the connection to grab the TS file from the OOB.
I'll email you the TS file directly. It wouldn't let me attach here and was too big to paste the contents into the body.
