Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
I think you want private vlans, which Fortinet calls access vlans. See https://help.fortinet.com/fos60hlp/60/Content/FortiOS/fortigate-managing-fortiswitch/GlobalCLIconfig... for details.
The medium and higher level FortiSwitches support this, but I don't think the 1xxD or 1xxE switches do.
Native vlan is the vlan that an untagged frame gets assigned by default.
Allowed is (usually) other vlan IDs that are allowed on that port.
If you're working with FortiGate managed switches using 3.6.x firmware you can't force tagged or untagged frames on a port from the GUI or even the FortiGate's CLI. You can ssh to the switch, though, and set it for a specific port, by setting discard-mode to all-tagged or all-untagged.
If you're running a FortiGate on 6.0.x and a managed FortiSwitch on 6.0.x you can set the same thing, just from the config switch-controller managed-switch section.
BTW, I'd recommend you don't use and don't delete vlan1. IIRC, it may be used by the FortiSwitch.
If the switch is managed by FGT in Fortilink mode you can use it the same way like for FortiAPs, it's called Block intra-VLAN traffic and is applied at VLAN configuration level
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1688 | |
1087 | |
752 | |
446 | |
227 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.