Cannot setup InterVLAN routing. Static route won't show up in Gateway routing tables.

Cannot setup InterVLAN routing. Static route won't show up in Gateway routing tables.

Cannot setup InterVLAN routing. Static route won't show up in Gateway routing tables.
Cannot setup InterVLAN routing. Static route won't show up in Gateway routing tables.
23 hours ago
Hardware Version:
Firmware Version: Latest firmware available

Hi! I have problem on making InterVLAN routing communication between my gateway and my switch.

 

Guide on how I do this:

 

  1. I have made sure I did every exact step described there.
  2. I did factory reset everything on my network (even find a console port and reset my switch) and create new site from scratch.
  3. Everything is up-to-date to the latest firmware. No ACL rules, nothing -- everything is set up as new, reset, and re-adopted.

 

The only difference is that my IP scheme is 10.x.x.x instead of 192.168.x.x but I don't think that matters (I've tried the IP 192.168.x.x as well, the result is still the same)

I don't know what is wrong with my configuration or my gears. Bugs? I don't know. Really stuck here.

 

My Network Topology

Devices:

  1. Gateway: Omada ER605 v2
    • IP: 10.0.0.1/24
    • Subnet: 255.255.255.0
    • VLAN 1 (default)
    • WAN Port 1: Connected to ISP modem in bridge mode
    • LAN Port 2: Connected to Main Switch (SG3218XP-M2) Port 1
  2. Main Switch: SG3218XP-M2
    • Static IP:  10.0.0.10/24
    • Subnet: 255.255.255.0
    • Default Gateway:  10.0.0.1
    • Port 1: Uplink to ER605 v2
    • Port 2: POE to Controller OC200 (IP: 10.0.0.2/24)
  3. Controller: OC200
    • IP: 10.0.0.2/24
    • Port: POE from Main Switch Port 2

 

 

VLANs -> Created via SDN Menu

Each VLAN is created on Settings > Wired Networks > LAN > Create New LAN

Purpose: VLAN & Application: Switches Only

  1. VLAN 20: Trusted Devices
    • SVI Static IP: 10.20.0.1 (This is the VLAN SVI on switch)
    • IP Range: 10.20.0.x/24
    • Default Gateway: 10.20.0.1 -> Pointing to the SVI on L2+ Switch
    • DHCP Server Enabled
  2. VLAN 30: Servers
    • SVI Static IP: 10.30.0.1 (This is the VLAN SVI on switch)
    • IP Range: 10.30.0.x/24
    • Default Gateway: 10.30.0.1

...

All other settings are created the same way as other VLANs

 

  1. VLAN 40: IoT Devices
    • IP Range: 10.40.0.x/24
  2. VLAN 50: CCTV
    • IP Range: 10.50.0.x/24

 

 

After that I have created "Static Route" on the gateway:

Destination IP/Subnet: 10.20.0.0/24 and so on for all available VLAN
Route Type: Next Hop
Next Hop: Main switch (10.0.0.10)

 

Also, I have already created the static route on the switch (0.0.0.0/0 -> next hop - 10.0.0.1 (gateway) and enabled it on the switch.

However, when I create the Static Route and having it enabled. I checked the menu Insight -> Routing Table and on the gateway tab, my defined static route doesn't show up there.

My client in each VLAN can get their IP correctly in each corresponding VLAN and can ping each other on the switch, including ping other client on another VLAN defined on the switch. The problem is it cannot reach the gateway nor the gateway can reach the SVI defined on the switch despite having defined static routes.

- My client on default VLAN (10.0.0.x) and other VLAN 20,30,40,50 CAN ping the switch (10.0.0.10)

- Client on each VLAN can ping their own VLAN gateway (SVI) AND the switch (10.0.0.10)

 

For example,

Client on SVI VLAN

  • Client IP 10.30.0.2 on VLAN30
  • ✅ can ping 10.0.0.10 (the main switch where SVIs are created)
  • ✅ can ping 10.30.0.1 (its own gateway)
  • ✅ can ping 10.40.0.1 (SVI gateway for VLAN40) ,  10.40.0.2 (client on VLAN40)
  • but cannot reach or ping beyond the switch itself (e.g. ❌ can't ping 10.0.0.1 the gateway IP), let alone internet access. It's like the SVI doesn't know the existence of the gateway at all.

Client on default VLAN (same subnet as the gateway)

  • Client IP 10.0.0.150 on VLAN1
  • ✅ can ping 10.0.0.10 (the main switch where SVIs are created)
  • ❌ can't ping SVI Interface Gateway for every VLAN defined on the switch (10.20.0.1, 10.30.0.1, ...)

 

 

These happen even when I have made sure I configured and enabled "static route" next hop to the switch.

The point is I want to offload the inter-VLAN routing to my powerhouse on my switch, which I recently bought which costs me a lot..

 

BUT what works is when I defined those VLAN as VLAN INTERFACE on the gateway and let the gateway (ER605) do the interVLAN routing, DHCP and all but it would saturate all my link speed. That is what it was working before I change the VLAN Interface to VLAN VLAN.

 

Any suggestions on why this happen? Is it a bug or misconfiguration? I did this three times and getting tired of this. Please help!

  0      
  0      
#1
Options
7 Reply
Re:Cannot setup InterVLAN routing. Static route won't show up in Gateway routing tables.
22 hours ago - last edited 21 hours ago

I think there's definitely something wrong with the static routes part on the gateway itself. I just don't know why that happens though. I tried spin up Proxmox (Trunk port, VLAN aware, got the correct IPs) and place containers into each VLAN and ping each other, ping the gateway. Tried using Mac and Windows to see if that's a firewall issue or not. Turns out nothing works.

 

FYI, when I create the VLAN "Interface", the routing table has automatically populate the route record for that subnet to the switch, that's why it works. However, when creating L2-Broadcast only, self-defined static routes don't get populate into the gateway routing tables. 😫

 

 

Last update:

I tried reproduce the problem and create new VLAN with the application applies to both Gateway and Switches

with all custom static routes defined -> then force provision the gateway, reboot, it still does not work as well. The routing table doesn't show the self-defined static route.

It looks like the static routes I am creating for the ER605 gateway are not being provisioned by the Omada Controller.

  0  
  0  
#2
Options
Re:Cannot setup InterVLAN routing. Static route won't show up in Gateway routing tables.
9 hours ago - last edited 9 hours ago

  @gabrielwang 

 

This should work

ignore the controller interface GUI being different (im on v6 beta) and it will look different on standalone but the functionality is the same


My Gateway Routes

All these vlans hop to the Switch SVI IP of my dedicated transit vlan

 

Populated Routing Table (Gateway)



Switch Routing

 

Traffic flows up and down the routes just fine.

 

These are what i call "hybrid" vlans as well - Gateway has an interface for them so i can use gateway DHCP with reservations, but all traffic is routed by the switch as the switch SVI IPs are set in DHCP as the client gateway.  I dont have any issues on another site with switch-only vlans using the same method

 

 

Now, i have another scenario where i have an ER605 v2 acting as VPN Gateway injecting direct into my core switch SG3428X over the transit vlan, with a gateway route for the target networks > switch, and a switch route for the VPN networks > ER605   This also works without a hitch so i am not seeing any issues with the same model gateway as you either

 

And the return route from the main switch

 

The VPN target networks dont even exist as interfaces on the ER605, its all just done with the routes.  works fine.

 

Some things for you to try:

- Remove the "Default Gateway" setting from the switch management SVI interface, let the 0.0.0.0/0 > Gateway route do all the work

- Make sure you dont have any ACLs that might be blocking the switch route

- Reprovision and reboot the switch, i have seen some behaviour where editing SVI and switch routed dont work properly until its been reprovisioned and rebooted

- How far does a traceroute to , say google dns 8.8.8.8 go before it stalls and you just get * * * * returned endlessly

 

 

  1  
  1  
#3
Options
Re:Cannot setup InterVLAN routing. Static route won't show up in Gateway routing tables.
2 hours ago - last edited an hour ago

  @GRL Thanks for your kind reply. I have stumbled upon your post and tried that with my subnet 10.VLAN.0.X and it doesn't work as well. Yours brilliantly preserved DHCP preservation functionality on the Gateway while maintaining SVI to communicate each other on the swicth itself. I admire that.

 

- Remove the "Default Gateway" setting from the switch management SVI interface, let the 0.0.0.0/0 > Gateway route do all the work

-> Tried that, doesn't work

- Make sure you dont have any ACLs that might be blocking the switch route

-> 100% sure there is none, as I fresh start my whole system every time

- Reprovision and reboot the switch, i have seen some behaviour where editing SVI and switch routed dont work properly until its been reprovisioned and rebooted

-> Also tried that every time

- How far does a traceroute to , say google dns 8.8.8.8 go before it stalls and you just get * * * * returned endlessly

-> "No route to host" (this is expected as there is no "logical link" between gateway and SVI)

 

May I ask have you tried my IP subnet scheme: 10.VLAN.0.X ?

Where the VLAN 1 (default) is 10.0.0.X/24 Mask 255.255.255.0 -> Router on 10.0.0.1, Switch on 10.0.0.10

VLAN20 is on 10.20.0.X/24

VLAN30 is on 10.30.0.X/24

and so on...

 

An update to the routing table problem:

When I use 10.VLAN.0.X scheme, the destination 10.VLAN.0.0/24 with next hop to 10.0.0.10 (switch) never never propagate to the routing table.

When I create static route for non-existence IP subnet on VLAN or any other random IP like

1. destination: 10.44.55.15/24 with next hop to some random public IP 202.25.4.82

2. destination: 10.0.30.0/24 with next hop to public IP 202.25.4.82

THEY ALL PROPAGATE TO THE GATEWAY ROUTING TABLE...oh my. So frustrating.

 

But when the next hop is 10.0.0.10 -> The gateway doesn't accept it as a next hop

 

--

so..

I tried that once again.. for the fourth time 😫 (spoiler: this does work!!! ✅).

1. Forget all devices from SDN. Factory reset controller, gateway, and switch. Start fresh.

2. Follow all the original and official instructions.

 

Now with different subnet.

 

10.0.0.X -> default VLAN1

Create new VLAN - Switch Only

The IP scheme is 10.0.VLAN.X (Note: the old one is 10.VLAN.0.X)

- VLAN20 10.0.20.x

- VLAN30 10.0.30.x

 

The Gateway ER605 IP = 10.0.0.1/24

The Switch IP = 10.0.0.10/24

 

Now I configure gateway static route as follow

Destination IP: 10.0.20.0/24

Next Hop: 10.0.0.10 (switch)

 

This configuration DOES ✅ propagate to the routing table.

But the old one 10.20.0.0/24 with next hop to the switch which reside in this default VLAN (10.0.0.10) DOES NOT ❌ propagate to the routing table.

 

I don't know why doesn't 10.VLAN.0.X work nor recognise 10.0.0.10 as a valid next hop while 10.0.VLAN.X does.

 

So.. it all works now but with a different IP scheme. I don't think it really matters whether I use 10.VLAN or 10.0.VLAN scheme because what really matter is the last CIDR /24, correct me if I'm wrong. Maybe a glitch or some controller validation bugs?

 

Ps. I didn't mark this post as problem solved as I still don't know why does the 10.VLAN.0.X scheme doesn't work with 10.0.0.10 as a next hop. Still want to know the reason.

 

Anyway, many thanks to you @GRL I really appreciate that. 🙏

  0  
  0  
#4
Options
Re:Cannot setup InterVLAN routing. Static route won't show up in Gateway routing tables.
an hour ago

  @gabrielwang 

 

Out of curiosity, what happens if you supernet all your vlans into one entry on the gateway route?

 

10.0.0.0/8 should cover every vlan in one go (it doesnt matter if it includes the default vlan as well), does that populate in?

 

 

  0  
  0  
#5
Options
Re:Cannot setup InterVLAN routing. Static route won't show up in Gateway routing tables.
an hour ago - last edited an hour ago

  @GRL 

Destination: 10.0.0.0/8 Next hop: 10.0.0.10 (switch)

The route doesn't propagate to the routing table as well. I don't know why. It's so strange. I wait around 3-5 minutes. Constantly refresh the routing table. Nothing shows up.

 

One more thing I experienced:

- When I create one static route -> It will propagate to the routing table.

When I disable and re-enable it again. This time it doesn't propagate to the routing table. It's like soooo unpredictable behaviour. That's why it's really pain to troubleshoot my problem now. I don't know what is the culprit now. 😫

  0  
  0  
#7
Options
Re:Cannot setup InterVLAN routing. Static route won't show up in Gateway routing tables.
an hour ago - last edited an hour ago

  @gabrielwang 

 

That is very strange indeed.  Its hard to say if this is gateway related or controller related.  I have both OC200 and OC300 and dont see this issue on either of my units with a bunch of different gateways.  Regardless im on v6, i havent seen this with previous versions of controller either.

 

I have a route for a 10.0.0.0/24 and a 10.0.20.0/22 AND a route for a 10.254.0.0 so thats the entire spectrum on 10.x.x.x and they all work fine first time.

 

 

I know @MR.S also does a lot of work with routes, if he sees this he might have an idea

 

EDIT:  Do you get any configuration failres at all?  (Devices list > Configuration Results > Failed) 

  0  
  0  
#8
Options
Re:Cannot setup InterVLAN routing. Static route won't show up in Gateway routing tables.
56 minutes ago

  @GRL 

 

Here's what I found.

 

This is the Static Route I set up with my final attempt. (The current working one)

 

This is a routing table (after enabled those routes for 5 minutes after)

 

Here's the configuration result. No failure.

  0  
  0  
#9
Options

Information

Helpful: 0

Views: 124

Replies: 7