I have a zone on the FortiGate named "VPN Zone", which includes both SSL-VPN and IPsec.
We are now testing a ZTNA appliance that is connected via the X1 interface -> VLAN 101.
I added the VLAN 101 interface to the existing "VPN Zone" and included its subnet in the existing rules.
As a result, LAN clients can communicate with devices inside VLAN 101. However, devices inside VLAN 101 are being blocked by the FortiGate from accessing LAN.
FortiAnalyzer reports that the traffic is blocked by policy ID 0, showing the source interface as "VLAN 101". This makes sense, since there are no explicit policies referencing that interface, only the zone.
and idea why the existing permit rules for the zone do not trigger for VLAN 101 outgoing? but incomming is fine?
FG200F v7.4.8
Solved! Go to Solution.
Got it working by moving the clients to another subnet and using the VLAN101 as a transport net. So the fault was the appliance assigning IPs to the VLAN101.
FortiOS doesn't allow you to mix SSL VPN interface with other interface type.
You put it in a zone means somehow you are trying to fool him, but FortiOS can't be fooled so easily ;)
Try remove SSL VPN from the zone (use separate policy) and it should work.
Got it working by moving the clients to another subnet and using the VLAN101 as a transport net. So the fault was the appliance assigning IPs to the VLAN101.
User | Count |
---|---|
2570 | |
1362 | |
796 | |
651 | |
455 |
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 2025 Fortinet, Inc. All Rights Reserved.