Skip to main content
robert44
Visitor III
October 9, 2024
Solved

60F IPSec site to site AWS NAT no ping

  • October 9, 2024
  • 1 reply
  • 970 views

Where is the problem? tunnel up no ping

OUTRzwcvc1.pngPDFXEdit_YRK115ooXm.pngPDFXEdit_BRfflKZ8HW.png

Best answer by saleha

Hi robert44,

Thank you for reaching out. I believe the issue here is about phase2 selectors missing the ippool external ip as local address on the fortigate side and would be a remote on the AWS server. This is because you are natting the traffic on the outgoing firewall policy and I see the ping is stopping at the ipsec tunnel. You can further confirm this with running the following debug then start the ping again:
di de flow filter addr 10.100.0.19

di de flow filter proto 1
di de flow show function enable

di de flow trace start 10

di de console time en

di de en

 

Thank you,

saleha

1 reply

saleha
Staff & Editor
salehaAnswer
Staff & Editor
October 9, 2024

Hi robert44,

Thank you for reaching out. I believe the issue here is about phase2 selectors missing the ippool external ip as local address on the fortigate side and would be a remote on the AWS server. This is because you are natting the traffic on the outgoing firewall policy and I see the ping is stopping at the ipsec tunnel. You can further confirm this with running the following debug then start the ping again:
di de flow filter addr 10.100.0.19

di de flow filter proto 1
di de flow show function enable

di de flow trace start 10

di de console time en

di de en

 

Thank you,

saleha

robert44
robert44Author
Visitor III
October 9, 2024

You've saved my life, thank you. I owe you a beer. It works by putting an IP from the IP pool, specifically I've put 10.0.112.230/32  on phase2 and now I can ping :D