Assigning WiFi users to VLANs dynamically

Facebooktwittergoogle_plusredditpinterestlinkedinFacebooktwittergoogle_plusredditpinterestlinkedin

Virtual LANs (VLANs) are used to assign wireless users to different networks without requiring the use of multiple SSIDs. Each user’s VLAN assignment is stored in the user database of the RADIUS server that authenticates the users.

This example creates dynamic VLANs for the Techdoc and Marketing departments. The RADIUS server is a FortiAuthenticator.

Find this recipe for other FortiOS versions
5.2 | 5.4

1. Configure the FortiAuthenticator

Go to Authentication > RADIUS Service > Clients to register the FortiGate as a client.
Enter a Secret (a password) and remember it. It will also be used in the FortiGate configuration.
fac-reg-fgt
Go to Authentication > User Management > Local Users and create local user accounts as needed. fac-user
For each user, add these RADIUS attributes which specify the VLAN information to be sent to the FortiGate.
Tunnel-Private-Group-Id specifies the VLAN ID.
In this example, jsmith is assigned VLAN 100 and twhite is assigned VLAN 200.
fac-user-radius-attr

2. Add the RADIUS server to the FortiGate configuration

 Go to User & Device > RADIUS Servers. Select Create New.
Enter the FortiAuthenticator IP address and the server secret that you entered on the FortiAuthenticator. Optionally, you can click Test Connectivity. Enter a RADIUS user’s ID and password. The result should be “Successful”.

radius

 3. Create an SSID with dynamic VLAN assignment

Go to WiFi Controller > SSID. Create a new SSID. ssid-basic
Set up DHCP service. ssid-dhcp
Select WPA2 Enterprise security and select your RADIUS server for authentication.
Set the default VLAN ID to 10. This VLAN is used when RADIUS doesn’t assign a VLAN.
ssid-security
Go to the Dashboard and use the CLI Console to enable dynamic VLANs on the SSID. config wireless-controller vap
  edit example-wifi
    set dynamic-vlan enable
  end

4. Create the VLAN interfaces

Go to Network > Interfaces.

Create the VLAN interface for default VLAN-10 and set up DHCP service.

vlan10

Create the VLAN interface for marketing-100 and set up DHCP service.

vlan100
Create the VLAN interface for techdoc-200 and set up DHCP service. vlan200

5. Create security policies

Go to Policy & Objects > IPv4 Policy.
Create a policy that allows outbound traffic from marketing-100 to the Internet. 
policy-100
In Logging Options, enable logging for all sessions. log-options

Create a policy that allows outbound traffic from techdoc-200 to the Internet.

For this policy too, in Logging Options enable logging for all sessions.

policy-200

6. Create the FortiAP Profile

Go to WiFi Controller > FortiAP Profiles.

Create a new profile for your FortiAP model and select the new SSID for both Radio 1 and Radio 2.

fap-profile

7. Connect and authorize the FortiAP

Go to Network > Interfaces and choose an unused interface.
Set Addressing mode to Dedicated to Extension Device.
Connect the FortiAP unit to the this interface and apply power.

Go to WiFi Controller > Managed FortiAPs.
Right-click on the FortiAP unit. Select Authorize.
Right-click on the FortiAP unit again. Select Assign Profile and select the FortiAP profile that you created.
auth-fap

Results

The SSID will appear in the list of available wireless networks on the users’ devices.
Both twhite and jsmith can connect to the SSID with their credentials and access the Internet.
(If a certificate warning message appears, accept the certificate.)

Go to Log & Report > Forward Traffic.

Note that traffic for jsmith and twhite pass through
different policies.

(The column selections were customized for clarity.)

The security policies could be made different so that Marketing and Techdoc departments were allowed different access, but didn’t think that was fair.

log

 

Jonathan Coles

Jonathan Coles

Technical Writer at Fortinet
Jonathan Coles is part of the FortiOS Technical Documentation team in Ottawa. He has a B.A. in English from the University of Waterloo and an Electronics Technologist diploma from Conestoga College. Long ago at another company he convinced a documentation manager that he could write. After writing about telephone PBXs, text search software, cell tower planning software, and some less memorable things, he joined Fortinet around the time that FortiOS 3.0 was released.
Jonathan Coles

Latest posts by Jonathan Coles (see all)

  • Was this helpful?
  • Yes   No
  • nanomoog

    Does the client need to use a 802.1x supplicant for this to work?