Any chance we can get preferred source IP on NTP Client.
The number of times I run into the issue the source IP the mikrotik chooses for that service is wrong and then you have to do hijinx to mangle or static route it to fix is more than annoying.
Let me make sure I understand your problem. You have a router that has multiple IP addresses, The router NTP client is sending NTP requests either from some address that does not belong to the router or more likely from the wrong address based on what interface the packet is going out on.
I just looked the client list on my NTP server at home. All three of my routers were showing an expected address. Router 1 has a interface and IP address on the same LAN segment as the NTP server, and it showed up on the NTP server as that IP address. Routers 2 and 3 do not have a direct connection on the LAN with the NTP server, and therefore have the NTP traffic routed through router 1. Both routers 2 & 3 showed IP address of the LAN interface that they would most likely use to route to router 1. In other words, as I would expect.
Nope not even close it’s a classic problem for an ISP or company with a transit router. The router is just lots of transit links or AS routes with route tables made of statics and some BGP aka where to send packets.
So now you want to connect to an NTP server client and so your NTP request packet will exit the transit link to the NTP server WITH THE TRANSIT IP AT THE ROUTER END. That transit IP (1) not public (2) probably not unique (3) Not routable except between the two routers. Even if your packet got to the NTP server the return back is unroutable. What I want is to send via a routable IP back NOT THE TRANSIT IP.
FYI that is why on the radius server setup you can nominate the source IP and even the ping and telnet tools are well aware you may need to specify the source IP. There are in fact a bunch of mikrotik services that allow source IP but the two that currently don’t are DNS and NTP.