New Member

Solved

error - reverse path check fail, drop

7 replies
20762 views

Hi everyone

We're trying to connect 2 sites with an VPN IPSEC. with the tunnel up and working. we have the next issue:

Scenario:

Triying to connect 192.168.0.102 --> 10.58.152.10

Having the following issue:

Anyone can help please?

FortiGate

JLopezM22Answer

New Member

Finally solved restoring backup :)

sagha

Staff

Hi,

Please provide the output for the following:

get router info routing-table details 192.168.0.102

get router info routing-table details 10.58.152.10

Once you share these outputs, we can clarify what might be going wrong here.

Thank you.

Shahan

JLopezM22Author

New Member

Routing table for VRF=0
Routing entry for 192.168.0.0/22
Known via "connected", distance 0, metric 0, best
* is directly connected, VLAN-A.

FGT01 (root) ## get router info routing-table details 10.58.152.1

Routing table for VRF=0
Routing entry for 10.58.152.0/24
Known via "static", distance 10, metric 0
10.58.152.1, via port14

Routing entry for 10.58.152.0/24
Known via "connected", distance 0, metric 0, best
* is directly connected, port14

sagha

Staff

Hi,

If you could see that there is no route for 192.168.0.102 via IPsec Interface, that is why you are seeing reverse path check.

Routing table for VRF=0
Routing entry for 192.168.0.0/22
Known via "connected", distance 0, metric 0, best
* is directly connected, VLAN-A.

You are receiving the traffic from source interface IPsec and you should also have a route that points at the Ipsec interface for 192.168.0.102.

Please add a static route and it should fix this.

Thanks,

Shahan

sagha

Staff

Hi,

You can also check the following article for details: https://community.fortinet.com/t5/FortiGate/Technical-Note-Details-about-FortiOS-RPF-Reverse-Path-Forwarding/ta-p/190100

Thank you.

Shahan

JLopezM22AuthorAnswer

New Member

Finally solved restoring backup :)

Sign up

Login with SSO

Login to the community

Login with SSO