Denied by forward policy check"Actually it means one of three things; No firewall policy matching the traffic that needs to be routed or forwarded by the FortiGate (Traffic will hit the Implicit Deny rule) The traffic is matching a DENY firewall policy The traffic is matching a ALLOW firewall policy, but DISCLAIMER is enabled, in this case, traffic will not be accepted unless end user will accept the HTTP disclaimer purposed by Fortigate while browser external site. Now back to what your doing, can you draft a clear map of the topology? I' m still scratching my head trying figuring out what your trying to do. Maybe a simple topodrawg and w/quick note on the drawing, will steer someone else into chime on a better or simpler way to get what you want. But what I gather you want to DNAT some ip_address with port-forward on port 80. My 1st question what or why would you need this over a vpn mesh? How do you have the phase2 proposal set ( take into consideration the DNAt and possible SNAT ) ? is this a route-based vpn ? And on this;
but I think I' m running into an issue with the ' mapped IP' being in the remote ' site2' subnet.That might now work as you concluded unless we are missing something else.
PCNSE
NSE
StrongSwan
PCNSE
NSE
StrongSwan
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1737 | |
1107 | |
752 | |
447 | |
240 |
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 2024 Fortinet, Inc. All Rights Reserved.