For some reason, my Fortigate 40F (v7.0.13 build0566) is losing the date and time settings when it loses power (maybe the battery is dead) and when the power comes back on, the Fortigate displays the message "Fortigate time is out of sync". I have already set the Fortigate to use the NTP server 200.160.0.8 but it does not work. When running the command "diagnose sniffer packet any 'host 200.160.0.8' 4" I can see the UDP requests being generated from my public IP, but no response is received.
In "Fortiview sessions" no sessions are displayed.
If I define this NTP server on a LAN host it works perfectly.
It seems that the problem only occurs when the traffic is generated by the Fortigate itself towards the IP 200.160.0.8. Could this be a bug in this firmware version?
1 Solution
I think my internet provider is blocking source port 123. When enabled, NTP uses the valid IP of a WAN interface and default source port 123 for the NTP request. I will validate this with my internet provider.
Just out of curiosity, I tried to set the source IP of the NTP request as the IP of the LAN interface and Fortigate uses this private IP and sends it directly through the WAN interface, without NAT. The behavior I would expect when setting the source IP as the IP of the LAN interface is that Fortigate NATs this request, passes through the SDWAN rules and only then goes to the internet.
I think my internet provider is blocking source port 123. When enabled, NTP uses the valid IP of a WAN interface and default source port 123 for the NTP request. I will validate this with my internet provider.
Just out of curiosity, I tried to set the source IP of the NTP request as the IP of the LAN interface and Fortigate uses this private IP and sends it directly through the WAN interface, without NAT. The behavior I would expect when setting the source IP as the IP of the LAN interface is that Fortigate NATs this request, passes through the SDWAN rules and only then goes to the internet.
