DHCP over VLAN or something

wizdum

[H]ard|Gawd
Joined
Sep 22, 2010
Messages
1,943
We're trying to replace an existing Meraki install with UniFi APs, but our network configuration is making it difficult. We have one large subnet across multiple sites. To prevent students/teachers from pluggin their devices into the LAN, we have a MAC address whitelist on our DHCP server. This wireless network is for BYOD and guest access, so we do not want to have to approve everyone's personal smartphone/laptop/tablet/etc. Currently, we whitelist the Meraki AP MAC address, and the Meraki "cloud" software hands out DHCP addresses. If we try this with the UniFi controller, by default it is expecting the DHCP server to hand out addresses to all the wireless clients.

Is there some way to replicate the Meraki setup with UniFi APs? Could we set up some sort of VLAN configuration where the UniFi APs are connected directly back to an EdgeRouter that hands out DHCP addresses over that VLAN only?



Any help is appreciated, this is for a public school so resources are limited.
 
"To prevent students/teachers from pluggin their devices into the LAN, we have a MAC address whitelist on our DHCP server"

So they can plug in and statically set an IP?

Anyway...

If it's really for guest access you should already be having all of that on a separate VLAN. Create a guest VLAN, put all the APs on the guest VLAN and create a DHCP scope or server for that VLAN.
 
Yeah, you're trying to "hack" it into working. At the VERY least, I'd create a guest VLAN with it's own DHCP server and then do the firewalling/routing as needed to your main network if the devices even need to access your internal network.

Better yet would be to route each site vs one large subnet and then at each site create VLANs for wireless, desktops, etc. As said, one could easily assign a static IP or clone a MAC address. Both easily doable. I'd also consider complete isolation of the wireless and have what's needed VPN into the private network.
 
"To prevent students/teachers from pluggin their devices into the LAN, we have a MAC address whitelist on our DHCP server"

So they can plug in and statically set an IP?

Anyway...

If it's really for guest access you should already be having all of that on a separate VLAN. Create a guest VLAN, put all the APs on the guest VLAN and create a DHCP scope or server for that VLAN.

Yeah... This system has been in place for probably 18+ years. We're actually having switches die of old age. The whole network really needs to be overhauled, we have no monitoring at all.

The desktops are all LTSP Thick Clients, so they get their addresses from the LTSP servers. This is primarily for student and teacher portable devices, along with true "guests" that visit for sporting events.

I've never done anything with VLANs before, and really have no idea how they work (yet). Is it something that could be set up on the AP and the router, or do I need to configure any managed switches that are in the middle?

Ideally, i'd like to have two VLANs for the wireless portion. One that goes to our internal LAN (connected to a password protected SSID), and one that just routes to the internet(guest access). As it is right now, any teachers or students that connect using their own devices lose access to our private resources, like printers and security cameras.

This also makes me wonder how people usually secure wired networks. Is there some kind of LAN authentication that works with Mac, Windows, and Linux? I imagine Microsoft has something that works with Active Directory, but we're sort of a multicultural shop.


EDIT:
Also, it sounds like the VLAN would need to be set up on the box that hands out DHCP addresses? I guess the problem is that i'm looking at a VLAN more like a tunnel. So I wont be able to just set up one VLAN for WiFi traffic, right? At the very least i'd have to have a WiFi VLAN and an "everything not wifi" VLAN?
 
Last edited:
Also, it sounds like the VLAN would need to be set up on the box that hands out DHCP addresses? I guess the problem is that i'm looking at a VLAN more like a tunnel. So I wont be able to just set up one VLAN for WiFi traffic, right? At the very least i'd have to have a WiFi VLAN and an "everything not wifi" VLAN?

Depending on how you go you usually have VLAN's created on the switches in conjunction with the router via router on stick topology method (as per Cisco's standards), a separate VLAN would be created for guests and then you would have ACL's to allow or deny various traffic flowing through that VLAN to another subnet belonging to another VLAN or so. You would need to have a DHCP pool to allocate the range of addresses you have specified, then have an address that is allocated to the server and on the exclude to issue/release list of the DHCP rule back on the router side so the router can look for the DHCP server which is providing the 4 states of the server's role.

Since all traffic is routed back to the router as switches don't do layer 3 routing (unless you use higher grade enterprise switches that can do partial layer 3 routing), normal scenarios you'd have the wireless AP connected to a switch which is connected to a router, VLAN's can be configured on the switch and a sub-interface back on the router for that network address/subnet to be recognized for traffic routing, the router can have DHCP pool/rules configured (also pointing to an assigned DHCP server), as soon as users join the wireless AP the user's will have an allocated DHCP request address.

Each VLAN is a virtual and logical lan/subnetwork as some large organisations can have up to 1000 subnet's, it'd be a major cabling, effort and time consuming clusterfuck having 1000 physical nodes/hosts connected to a switch (which comes in 12-24-32 and 48 port flavors), so VLAN's can cut this down to a very manageable and scaled down degree.
 
Last edited:
I think I understand how VLANs work at the switch level. What i'm having trouble with is how that is routed up through the network. Is it like a VPN tunne where I just set up the two end nodes and the hardware between doesn't matter (assuming there is a path connecting them), or would I have to start from the top and configure each switch between the AP and the EdgeRouter Lite?

I'll have to confirm on Tuesday, but I believe the network is set up as follows

SonicWall Gateway/firewall -> "Core" District Switch -> "Core" School Switch -> LAN Switches

There's probably 2 - 3 48 port "LAN Switches" at each school that are connected to the "Core" School Switch at each school. So an AP at the Elementary school would have to travel the following path: Elem. LAN Switch -> Elem. Core Switch -> Core District Switch -> EdgeRouter DHCP Server.

Would I have to go to each one of those switches and configure it to understand the VLAN?
 
Good to see the school is using infrastructure layering or aggregation of switches having core switches/router right after the firewall then normal grade switches connected for each lan/subnet usage. There might be redundancy in between those links should one fail.
 
Back
Top