FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
fwilliams
Staff & Editor
Staff & Editor
Article Id 240805
Description

This article provides technical details about the forwarding domain in FortiGate’s transparent mode and how to implement it.

Scope FortiGate v6.4, v7.2, v7.4, v7.6.
Solution

Once the FortiGate is configured in transparent mode, it starts acting like a layer 2 switch, following 802.1d standards (Ethernet MAC bridging in this case, since it is not running a spanning tree).

This means all its ports are sitting in the same Broadcast Domain and traffic received on one port is flooded to all other ports except the one the traffic came in through.

 

To segment or narrow this broadcast domain scope (like split the big broadcast domain into smaller ones), configure the 'forwarding domain'.

 

Every port (physical or virtual) which are assigned with the same forwarding domain ID or to the same forwarding domain will start acting as a broadcast domain and creating a new broadcast domain boundary.

 

The network diagram below will be used to demonstrate this article.

 

fwilliams_0-1671902028485.png

 

Topology Description:

  • HQ-SW has interface G0/1 in VLAN100, G0/2 in VLAN200, and G0/0 as trunk to FortiGate.
  • Branch-SW has interface G0/1 in VLAN300, G0/2 in VLAN400, and G0/0 as trunk to FortiGate.
  • FGT-Transparent has port1 as a trunk to HQ-SW and port2 as a trunk to Branch-SW.
  • PC100 is sitting VLAN100, PC200 in VLAN200, PC300 in vlan300 and PC400 in VLAN400.

 

With the forwarding domain configured, PC100 can communicate with PC300, because it is in the same forwarding domain (broadcast domain).

And PC200 can communicate with PC400.

 

Note.

A firewall policy is required for this to work (ensure to configure a firewall policy).

 

Configuration and verification:

Virtual interfaces are created and assigned VLAN100, 200, 300, and 400 on the FortiGate.

Then VLAN100 and 300 interfaces are assigned to forwarding domain 100300, so any device sitting in VLAN100 and 300 with the same IP subnet assigned can reach each other.

VLAN200 and 400 interfaces are assigned to forwarding domain 200400.

The below screenshot shows the configuration and the verification.

 

  1. Creating VLAN interfaces and allocating forwarding domains (ID <0 - 2147483647) to them.

 

fwilliams_1-1671902059343.png

 

  1. Configure firewall policy.

 

fwilliams_2-1671902080631.png

 

  1. Verify FDB (forwarding database):

 

diagnose netlink brctl name host <vdom_name.b>

 

fwilliams_3-1671902099853.png

 

  1. Sniffer (VLAN100 to VLAN300 ping).

 

fwilliams_4-1671902119745.png

 

  1. Sniffer (VLAN200 to VLAN400 ping).

 

fwilliams_5-1671902142946.png

 

  1. Ping (from 192.168.100.1 -> 192.168.100.3 & 192.168.200.2 -> 192.168.200.4).

 

fwilliams_6-1671902152349.png

 

Notes:

 

  1. If the VLAN interfaces are in different forwarding domains, it is also possible to allow inter-vlan traffic, but the routing part will be performed on the upstream device (firewall, router, L3 switch) and it needs to have a policy allowing the inter-vlan traffic, which is the most recommended scenario.

 

Topology:

 

2025-03-19_13_29-001697.jpg

 

VLAN configuration on FortiGate in transparent mode:

 

config system interface
    edit "VLAN10_IN"
        set vdom "root"
        set forward-domain 10
        set device-identification enable
        set role lan
        set snmp-index 8
        set interface "LACP"
        set vlanid 10
    next
    edit "VLAN10_OUT"
        set vdom "root"
        set forward-domain 10
        set device-identification enable
        set role lan
        set snmp-index 9
        set interface "port2"
        set vlanid 10
    next
    edit "VLAN20_IN"
        set vdom "root"
        set forward-domain 20
        set device-identification enable
        set role lan
        set snmp-index 10
        set interface "LACP"
        set vlanid 20
    next
    edit "VLAN20_OUT"
        set vdom "root"
        set forward-domain 20
        set device-identification enable
        set role lan
        set snmp-index 11
        set interface "port2"
        set vlanid 20
    next
end

 

Firewall Policy on the upstream device in NAT mode:

 

Inter-vlan policy.jpg

 

Firewall Policy on the FortiGate device in Transparent mode:

 

Inter-vlan policy_2.jpg

 

  1. When trying to specify the source and destination interfaces that are in different forwarding domains on the FortiGate in transparent mode, the issue below will be found:

     

 

Forward Domain.jpg

 

  1. When a VLAN interface is being used in a firewall policy, the 'forward-domain' setting can not be changed. An error message will show up as below:

 

forward-domain-error.png