An existing subnet works across a FortiGate site-to-site VPN, but a newly introduced subnet cannot reach the same application. Start by recording a working and failing source IP against one destination. Verify the firewall’s routes and policy for both. In designs using explicit selectors, check whether the negotiated Phase 2 security associations cover the failing source and destination.
get vpn ipsec tunnel summary
diagnose vpn tunnel list
Inspect only the relevant tunnel output in an authorized session. Compare the local and remote protected networks on both peers. What one peer treats as local should correspond to the other peer’s remote definition. If your design uses broad selectors, inspect routing and firewall policy for the specific prefixes. A healthy security association establishes only the negotiated scope.
Worked example. The original subnet appears in the negotiated selectors and has bidirectional traffic. The approved new subnet has a route and matching policy, but the peer’s explicit selectors still cover only the original subnet. The engineers align the approved definitions on both sides, verify negotiation, and test both old and new sources. Check the return path as part of the same test.
See the FortiOS IPsec handbook for the concept, and match configuration syntax to the installed release. For a broader diagnosis, see FortiGate IPsec VPN Is Up but No Traffic Passes.