Might want to check firewall policy config, ipsec selectors and routing config. If you still have trouble check out my video on sniffer. Then it might be good to call support
Yes, you should always expect traffic on port 500 regardless of NATT, NATT is specific to phase2 Here's the ports/protocols to expect depending on whether NATT is in use or not: NATT NOT being used: phase1 = UDP 500 phase2 = ESP (ie. IP protocol 50) NATT being used: phase1 = UDP 500 phase2 = UDP 4500
Brilliant, this would really help FortiGate engineers to fix all the s2s related issues.Awesome.......
just great. thanks for sharing.
It was really to the point. Thanks mate.
Interesting video, well done ! Thanks
Amazing content! Thanks so much!
Excellent video!
thanks for sharing
great job, tks!
Thank you very much for the video !!
i love ti, thanks
Amazing 🎉
thanks mate, very usefull information for me
great content 🤝
Wow what great content!
Thanks (Y)
❤
i already creat site to site.its successful to connect but the other side i cant ping thier ip (local ip's).
Sir my problem is that all Connections are up but no Incoming Data and Outgoing data were made.
Might want to check firewall policy config, ipsec selectors and routing config. If you still have trouble check out my video on sniffer. Then it might be good to call support
tks, nice vide, if you allow me to make a question, if nat t is enable I should expect traffic in port 500 as well in phase1 ? or 4500 ? I am confuse
Yes, you should always expect traffic on port 500 regardless of NATT, NATT is specific to phase2
Here's the ports/protocols to expect depending on whether NATT is in use or not:
NATT NOT being used:
phase1 = UDP 500
phase2 = ESP (ie. IP protocol 50)
NATT being used:
phase1 = UDP 500
phase2 = UDP 4500
@@tothepointfortinet3823 tks a lot for the reply..you are a nice person :)