It seems likely the OP has moved on to other problems, but another solution
that should work occurs to me. To control the local IP address used for
communication with upstream servers, two NTPD instances could be used on
the same host.
One instance would be configured to operate on a non-standard
On Thu, Sep 29, 2022, 9:36 AM Blažej Krajňák
wrote:
> Well, my server has dummy interface and multiple /32 IP addresses.
> They are announced via OSPF to IGP.
>
> The idea is to anycast 2 IPs (HA solution) and when primary server
> goes down, secondary will response to primary's IP address also.
I would of expected the routing table to be used to determine which
interface IP address interface to use to send to the specified NTP
server address so its not really a NTP server setup
Ross Wilson
On 29/09/2022 5:33 pm, Blažej Krajňák wrote:
Hi there,
I read the documentation a few
Well, my server has dummy interface and multiple /32 IP addresses.
They are announced via OSPF to IGP.
The idea is to anycast 2 IPs (HA solution) and when primary server
goes down, secondary will response to primary's IP address also.
Primary server has the following config:
interface ignore
In comp.protocols.time.ntp, you wrote:
> Hi there,
>
> I read the documentation a few times but can not find if it's possible
> to specify IP address for outgoing connections?
>
> I have server with multiple IP addresses and I need to specify the
> concrete one to be used to sync with
Hi there,
I read the documentation a few times but can not find if it's possible
to specify IP address for outgoing connections?
I have server with multiple IP addresses and I need to specify the
concrete one to be used to sync with servers/peers. For now, ntpd
selects one of the listening
