Fortinet MC3200 Vlan configuration

[HereIGoAgain2601]

Hello

 

A couple of the schools in our Trust are using an ancient MC3200 for wireless access. Luckily we are due to have them replaced with CTC just as soon as the kit arrives.

 

In the meantime I need to try and configure a guest wireless VLAN. Up until now staff were just connecting to the internal network which I’m not happy with for obvious reasons.

 

Does anyone know what the crack is - I’ve tagged the controller so it can access the VLAN and done a “profile” that says use the VLAN on guest SSID but nothing actually happens when you connect to the SSID - just get a 169. If you plug into a switch port on the guest VLAN you get DHCP and everything works so an issue with my wireless controller / settings.

 

Does anyone know if the APs themselves need tagging on the VLAN - I was assuming it would just be one of these old systems where all traffic goes through the controller uplink?

 

If I can’t figure it out we will just have to soldier on until CTC goes in!

 

Cheers

[Davit2005]

Most of the time the APs need to be tagged yes. Exclusions to this are Aruba (not Instant or InstantOn for instance) and probably others where you have controllers which the APs form a tunnel to and there is no need to tagg the vlans.

 

Is there no help function in the GUI or documentation?

Edited August 31, 2023 by Davit2005

[psydii]

Meru aps tunnel their traffic back to the controller. So that should work. Is the vlan tagged on both the controller and the appropriate switch port?

 

Can the clients ping each other? (They should be able to if inter-client commms isn’t explicitly blocked)

Edited August 31, 2023 by psydii