Last updated: December 11, 2012 at 20:26 pm
Super-basic example of a VLAN setup. We have a WAP in our office that is dedicated as our ‘guest’ network. Our current setup is clunky right now, but just imagine that it’s a UniFi or Ruckus WAP that is tagging all incoming traffic (in = from wireless clients TO the router) with a vlan10 tag. (we have a managed switch in between the WAP and the router that is tagging the traffic, but it’s a mess. )
laptop -> WAP -> vlan10 tag gets added -> plugged into RB750GL port 3
We have vlan10 set up with it’s own DHCP server that hands out addresses on the .10.xyz subnet. Here is how it’s set up.
This is how it’s set up. Set ether3’s Master Port to none. Add a VLAN Interface (you can click the + on the Interface List or go to the VLAN tab and do the same). Give the vlan interface a name, give it a vlan tag number to use, and attach it to a port that will be receiving traffic with that tag. Note that my ether3 still has the default name even though it is no longer a ‘slave’ port. Just an example of how the Name doesn’t actually mean anything…. but I should probably get around to changing that at some point…
Now you have a whole new virtual interface on your router. Let’s give it something to do. Set up a new DHCP server and assign the Interface to the new vlan interface you just created. First step is to assign an IP address to that vlan interface.
Next, create a new DHCP Pool to use for the vlan.
Next, add a new DHCP Server and have it use the new “vlan10 dhcp” pool.
Now let’s set up a Network for that new DHCP server to use. This will give the following info to any device that gets a DHCP address from the WAP: use 192.168.10.1 as your Gateway to the internet, and use 126.96.36.199 for your DNS server.
That’s it! The WAP is now up and running and any device that connects to it will get a 192.168.10.xyz address.