Answer is "D". If it was dropped by RPF, the log would've been "reverse path check fail, drop"
See KB ==> https://kb.fortinet.com/kb/documentLink.do?externalID=FD31702
The answer is D:
Root causes for "Denied by forward policy check"
1- There is no firewall policy matching the traffic that needs to be routed or forwarded by the FortiGate (Traffic will hit the Implicit Deny rule)
2- The traffic is matching a DENY firewall policy
3- 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.
In this case we are in the first situation because at the end of the log it says policy 0.
For more details check the link:
https://kb.fortinet.com/kb/documentLink.do?externalID=FD31702
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
moneim
Highly Voted 3 years, 8 months agozqrni
3 years, 7 months agozqrni
Highly Voted 3 years, 8 months agoSandroAlex
Most Recent 3 years, 1 month agokemi01
3 years, 1 month agosteef1982
3 years, 8 months agoyadavarya97
3 years, 8 months ago