Description
This describes how to parameter 'vlanforward'.
Solution
'vlanforward' is meaningful at OSI Layer2, so in Transparent (TP) mode.
In TP mode, the 'vlanforward' parameter allows control of what will happen to an incoming VLAN tagged packet when there is not a VLAN interface configured like:
If disabled then the packet is dropped.
If the FortiGate has the parameter 'vlanforward' enable on the physical interface, then, the VLANs will cross the FortiGate.
To control the traffic of VLANs, disable 'vlanforward' and configure interface with a specific vlanid.
'vlanforward' can also be enabled to transfer vlanid that does not have a specific VLAN interface configured.
Consider also the parameter forwarding domain.
The VLAN interfaces are all in the default forwarding domain of 0.
Due to the behavior of the FortiGate this will cause flooding of packets between interfaces and VLAN's in the same VDOM when operating in transparent mode.
If VLANs interfaces are defined and create accordingly forwarding-domain and Firewall policies, the FortiGate will inspect the traffic until application level when a protection profile is attached to the firewall policy.
The parameter is defined in FortiOS CLI Reference version 5.4.1 as follows:
'vlanforward' = Enable/disable VLAN forwarding.
The default value is disable.
The default setting was previously enabled.
If 'vlanforward' is enabled under all interfaces in TP mode, even without any firewall policy config, traffic with VLAN tags can go through the FortiGate.
This introduced a potential security issue, the default was moved to disable starting with firmware versions v5.0.10
The value of the parameter is not modified under upgrade.
This describes how to parameter 'vlanforward'.
# config system interface
edit interface-name
set type physical
set vlanforward [enable/disable]
end
Solution
'vlanforward' is meaningful at OSI Layer2, so in Transparent (TP) mode.
In TP mode, the 'vlanforward' parameter allows control of what will happen to an incoming VLAN tagged packet when there is not a VLAN interface configured like:
# config system interfaceIf 'vlanforward' is enabled, then the packet is forwarded out the appropriate egress port without any inspection of the traffic inside the VLAN tagged packet.
edit "VLAN_110"
set vdom "TP"
set interface "wan1"
set vlanid 110
next
end
If disabled then the packet is dropped.
If the FortiGate has the parameter 'vlanforward' enable on the physical interface, then, the VLANs will cross the FortiGate.
To control the traffic of VLANs, disable 'vlanforward' and configure interface with a specific vlanid.
'vlanforward' can also be enabled to transfer vlanid that does not have a specific VLAN interface configured.
Consider also the parameter forwarding domain.
The VLAN interfaces are all in the default forwarding domain of 0.
Due to the behavior of the FortiGate this will cause flooding of packets between interfaces and VLAN's in the same VDOM when operating in transparent mode.
If VLANs interfaces are defined and create accordingly forwarding-domain and Firewall policies, the FortiGate will inspect the traffic until application level when a protection profile is attached to the firewall policy.
The parameter is defined in FortiOS CLI Reference version 5.4.1 as follows:
'vlanforward' = Enable/disable VLAN forwarding.
The default value is disable.
# config system interfaceThe 'vlanforward' default setting has been modified for security reasons.
edit "wan1"
set vdom "root"
set allowaccess ping fgfm
set type physical
set snmp-index 2
set vlanforward disable
next
The default setting was previously enabled.
If 'vlanforward' is enabled under all interfaces in TP mode, even without any firewall policy config, traffic with VLAN tags can go through the FortiGate.
This introduced a potential security issue, the default was moved to disable starting with firmware versions v5.0.10
The value of the parameter is not modified under upgrade.
Related Articles