Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
Zhuo
New Contributor III

FortiGate NTP config interface-select-method specify

Use custom source interface to exit, but the traffic will check the default route and exit through the found route interface, not the custom interface ip.
But after configuring the source ip, there is no problem.

Why is this?

 

config system ntp
set ntpsync enable
set type custom
set syncinterval 1
config ntpserver
edit 1
set server "10.0.0.17"
next
end
set source-ip 10.0.64.114---------------Can
end

------------------------------------------------------------

config system ntp
set ntpsync enable
set type custom
set syncinterval 1
config ntpserver
edit 1
set server "10.0.0.17"
set interface-select-method specify
set interface "port1"----------------------Can't
next
end
end

 

port1=10.0.64.114

12 REPLIES 12
Toshi_Esumi

There is no specific route than those 0/0 routes. Do you see all four routes in "get router info routing-t detail 10.0.0.17"?
Then do you happen to have any policy routes or SD-WAN rules?
But if you set a specific route like,

config router static

  edit 0

    set dst 10.0.0.17/32

    set gateway 10.0.64.x  <-- GW IP
    set device port1

  next

end
you would accomplish what you want.

Toshi

saneeshpv_FTNT

Hi @Zhuo 

 

The "set interface-select-method" command is used when you have more than one available routes to the destination like in the case of SDWAN and where you want self-orginating traffic to consider SDWAN rules/routes. Here with your setup I am not able to see any route available via the Port1 to reach your NTP server. So specifying that interface will not work as expected. The solution is to use "set source-ip" so the traffic will always leave FGT using this IP as source even though it exit out of Port2 as per your routing.

 

https://community.fortinet.com/t5/FortiGate/Technical-Tip-Functionality-of-set-interface-select-meth...

 

Best Regards,

Saneesh

 

Toshi_Esumi

Maybe a knit-picking, but this KB describes only "...(DNS, FortiGuard, RADIUS, LDAP)..." instead of "...(DNS, FortiGuard, RADIUS, LDAP, etc.)..."

Does this apply to NTP traffic as well?

 

Toshi

Announcements

Select Forum Responses to become Knowledge Articles!

Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.

Labels
Top Kudoed Authors