guest network using tagged VLANs
glenn.satchell at uniq.com.au
glenn.satchell at uniq.com.au
Tue Jan 14 02:36:20 UTC 2020
Hi Steve,
There is an even simpler solution.
Configure a single VLAN on the switch, send untagged packets to the port
the WAP is plugged into.
Run the two IP address ranges on the single VLAN. On the dhcp server
configure these as a shared network.
Use your rules about known devices, etc, to decide which pool of
addresses to assign to a given client.
This VLAN does not need to go all the way to the dhcp server, just make
sure routing is in place with a dhcp forwarder on the router - same as
you would do for any non-local subnet.
regards,
-glenn
On 2020-01-13 19:28, Simon Hobson wrote:
> To expand on Rudy's reply ...
> As said, configure the AP to connect one SSID to one VLAN, and another
> SSID to another VLAN - this is then functionally equivalent to having
> two APs on separate physical LANs.
> At the DHCP server, have the daemon listen on the two VLAN interfaces
> and define subnets to match. Again, this is functionally the same as
> having two interfaces connected to two seoarate LANs.
> The rest just happens automagically - no special rules in your DHCP
> config.
> This is something I've done a few times both internally and for
> clients.
>
> Simon
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
More information about the dhcp-users
mailing list