Technical Tip: How to configure FortiGate forward broadcast
Description
Scope
FortiGate.
Solution
end
- Configure broadcast forwarding on the interface:
set broadcast-forward enable
next
edit wan1
set broadcast-forward enable
end
- Configure broadcast address:
edit "allbroadcast"
set type broadcastmask
set subnet 255.255.255.255 255.255.255.255
end
- Configure multicast policy:
edit 1
set srcintf "any"
set dstintf "any"
set srcaddr "all"
set dstaddr "allbroadcast"
next
end
It is important to know that on some broadcast services, the server will send the reply on a broadcast IP.
The above policy will allow both sessions:
- The one from the client to the broadcast IP. For example:
DMZ_in 10.44.5.23.57 -> 255.255.255.255.57: udp 20
Broad_out 10.44.5.23.57 -> 255.255.255.255.57: udp 20
- The other one for the server replies with a broadcast packet:
Broad_in 10.56.5.5.57 -> 255.255.255.255.57: udp 20
DMZ_out 10.56.5.5.57 -> 255.255.255.255.57: udp 20
Enable logging on the multicast policy to see the traffic logs under Log & Report -> Multicast Traffic.
Note: This configuration might have worked in earlier versions, but it is not supported in the latest releases (verified in 7.4.8). The explanation is as follows:
The broadcast-forward enable option is used to control direct broadcasts, not traffic destined for 255.255.255.255. Therefore, it is not possible to allow traffic to 255.255.255.255.
For example, if the DMZ interface is configured with the subnet 192.168.0.0/24, the directed broadcast address would be 192.168.0.255.
For a detailed explanation, see this article: Troubleshooting Tip: FortiGate Operating in NAT Mode does not allow Broadcast Traffic destined to 255.255.255.255.
Note: The any/any multicast-policy above is a baseline example. For production, limit it to the required ingress/egress interfaces (and address ranges) to avoid unintended flooding across the forwarding domain.
Related document:
