Skip to main content
MrCrow
MrCrow
New Member
April 6, 2022
Solved

One port multiple vlans

  • April 6, 2022
  • 2 replies
  • 15260 views

Hello. I have a FortiGate 60F and I have a layer-2 switch attached to one of the ports. On that nameless L2 switch is my WiFi WAPs (just some old Aruba's we had laying around). I want to have a guest network on those WAP's, but also want to have normal connectivity like I currently have. I'm trying to fumble my way through, but I can't seem to figure out a way to allow multiple IP/VLANs on one port. The L2 switch is on Port3, and I have that as part of the internal VLAN Switch (default setup) as pictured.

 

Port3 > 8-port L2 switch > two Aruba WAPs with 2 VLANs (VLAN 0 and Guest VLAN)diag.JPGmain_int.JPG

Best answer by Toshi_Esumi

On the 60F, or any other FGT models, the parent interface like "internal" vlan switch/hard-switch interface, which includes port3/internal3, is non-tagged interface. On the switch it's probably equivalent to VLAN0. So 192.168.50.0/24 needs to be VLAN0 on the switch.

Then Guest VLAN n subinterface needs to be created on the internal interface, then you want to assign a GW IP in 192.168.60.0/24, like .1. Then the port3, as well as port1 and 2, carries both non-tagged/VLAN0 and VLANn traffic. You need to make the switch side port a trunk.

 

BTW, the VLAN switch you're seeing is new with 'F' series FGTs as well as a few 'E' models, which is enabled by default at least with 6.4 or later. But we had some discussion in a different thread about a month ago but nobody seems to know what exactly it does compared to the traditional "hard-switch". So just pretend you're seeing hard-switch interface in the GUI instead of Vlan switch. In CLI, it's configured in hard-switch configuration block under "config system virtual-switch" anyway. 

 

Toshi

2 replies

Toshi_Esumi
SuperUser
Toshi_EsumiAnswer
SuperUser
April 6, 2022

On the 60F, or any other FGT models, the parent interface like "internal" vlan switch/hard-switch interface, which includes port3/internal3, is non-tagged interface. On the switch it's probably equivalent to VLAN0. So 192.168.50.0/24 needs to be VLAN0 on the switch.

Then Guest VLAN n subinterface needs to be created on the internal interface, then you want to assign a GW IP in 192.168.60.0/24, like .1. Then the port3, as well as port1 and 2, carries both non-tagged/VLAN0 and VLANn traffic. You need to make the switch side port a trunk.

 

BTW, the VLAN switch you're seeing is new with 'F' series FGTs as well as a few 'E' models, which is enabled by default at least with 6.4 or later. But we had some discussion in a different thread about a month ago but nobody seems to know what exactly it does compared to the traditional "hard-switch". So just pretend you're seeing hard-switch interface in the GUI instead of Vlan switch. In CLI, it's configured in hard-switch configuration block under "config system virtual-switch" anyway. 

 

Toshi

    MrCrow
    MrCrowAuthor
    New Member
    April 6, 2022

    Thanks for the tips. I was able to connect my phone to the guest network and it got an IP address and was able to connect it to the guest VLAN (192.168.69.2 is the phones IP) but I can't get out to the internet.... I'm assuming because I don't have any firewall rules yet I think?guest.JPG

    Toshi_Esumi
    SuperUser
    Toshi_Esumi
    SuperUser
    April 6, 2022

    Mostlikely. Each VLAN interface is treated as just another interface in the policies. So if you want to connect the Guest VLAN to the internet, you need to have Guest->wan1 or 2 policy with NAT enabled.

     

    MrCrow
    MrCrowAuthor
    New Member
    April 6, 2022

    Thanks for all your help! I got it to work! Part of it I think was that I had my Aruba WAP's configured wrong....

    Terms & ConditionsAccessibility statement