Skip to main content
chocolateeater
New Member
January 29, 2023
Question

Bridged SSID not getting DHCP

  • January 29, 2023
  • 10 replies
  • 8540 views

Hi, all. 


I have two switches - Dell Powerconnect and Fortiswitch. There are several FortiAPs connected to both switches, broadcasting the same set of SSIDs.

 

All SSIDs that are tunneled are working fine on both switches. I have one SSID that is bridged to a LAN, as they need to be interconnected. When connecting to APs on the Powerconnect, everything works fine. But when connecting through the FortiSwitch, the clients cannot reach DHCP. Authentication is set to local, so everyone gets a connection.

 

I have attached a basic scheme of the setup. Could anyone point me towards what I am missing, here? Why cannot the clients connecting through FS get an IP?

 

SSID Tech.png

 

10 replies

ebilcari
Staff
Staff
January 30, 2023

When using a bridged SSID the users VLAN should be spanned across the switches. Is the user VLAN tagged on the switch ports connecting the APs and configured on FSW/Fortilink?

If you want to use the same VLAN on different ports of FGT you have to create software/hardware switch on FortiGate: https://docs.fortinet.com/document/fortigate/7.2.3/administration-guide/100999/hardware-switch

Emirjon
chocolateeater
New Member
February 22, 2023

Hi, ebilcari.

I have a SW switch enabled, but I think you are on to something. The VLAN (40) tagging the WLAN traffic was not defined as allowed on the Fortilink, and not on the ports that the APs are connected to.

I have now defined this, but it still does not work, so there is still something I'm missing - probably how to connect the traffic from the Fortilink to the SW switch. The VLAN defined on the Fortilink is not possible to include in the SW switch. Any ideas?

ebilcari
Staff
Staff
February 23, 2023

The trick is that the VLAN that can be included in a Software switch should be pure Layer 2, no IP configuration or address object should exist for that VLAN.

Try to create a new VLAN on FortiSwitch VLANs without selecting anything related to IP (Layer 3 configurations)

ebilcari_0-1677141362280.png

Layer 3 configuration should be done on Software switch interface only.

Emirjon
AEK
SuperUser
SuperUser
January 30, 2023

Hello Choco

Try configure a static IP on the client, then try ping your FGT and use sniffer to see if you are really on the same VLAN with your FGT.

 

AEK
chocolateeater
New Member
February 22, 2023

Hi.

Took a while for me to get back to this problem. I have set a static IP, and have no connection to anything. Seems the access points are not sending traffic from this network across the FortiSwitch at all, and so the problem must be with the bridged mode - as all other networks works. 

 

Any tips on how to debug this any further?

Thought Leadership. Security Summit. Thursday, November 12th, PGA National Resort, Palm Beach Gardens, FL.
Thought Leadership. Security Summit. Thursday, October 8th. Disney's Grand Californian Hotel & SPA, Anaheim, CA.
Security Operations Summit: Modernize SecOps. Operate AI-Native.AMER: November 4 | 9:00 AM PST. India and SAARC: November 5 | 10:00 AM IST. EMEA: November 5 | 10:30 AM CET. APAC: November 5 | 11:00 AM SGT