This guide will show you how to enable inter-vlan routing through your L2+ or L3 switch, keeping full DHCP reservations working without the need for a seperate DHCP server, and without the need for static routes.

Applies to:

Any Controller based or Standalone based Omada network with at least one L2+ / L3 switch at the core

My guide will be based on OC200 controller, but the same method can be applied to the router and core switch in standalone mode in their respective GUIs.

Benefits:

Allows the switch to handle inter-vlan routing so that traffic is kept off all your router uplink trunks.

Allows full DHCP reservations to work without the need for DHCP relay or a seperate DHCP server device on the network

Step One:

Setting up the VLANs

Settings > Wired Networks > LANs

Add your VLANs with the 802.11Q tags as needed, configured as INTERFACE and not VLAN

Step 2:

Enable each interface on the switch and configure its static IP per VLAN and configure its subnet mask to match what was set up for the VLAN

(devices > switch > Config > VLANs)

Step 3:

Configure DHCP server for the VLAN (Settings > Wired Networks > LAN) to assign DHCP range, DNS servers and set the Gateway to point to the switch static IP set above, Repeat for each VLAN

Thats it!

Now, your normal DHCP reservations will still work as the gateway is still the DHCP server for the VLAN, and the L3 switch will be handling all inter-vlan routing as allowed by your ACLs.

In this image below, my computer is on the 192.168.100.X network, and running a traceroute to the copier on the Office network shows it first hits the Switch Interface for the VLAN its on (192.168.100.253) then immediately hops to the copier at 192.168.10.252, without having to hit the gateway at all.

All internet traffic will hop to the gateway as normal.  This also allows you flexability when setting static IPs on devices - you can choose to set the gateway to the Router IP or the Switch IP, depending on use case, and both will work perfectly.

NOTES

Only set up the switch interfaces on ONE SWITCH, ideally the one closest to the gateway depending on your topology

I recommend only setting this up for non-management VLANs