[ntp:questions] ntp server with two default routes misbehaving after upgrade

Rob nomail at example.com
Sun Apr 20 07:37:40 UTC 2014

Caecilius <nospam at spamless.invalid> wrote:
> I guess that something has been added between 4.2.4p4 and 4.2.6p2
> that's making ntp take notice of the two different routes. But I don't
> understand why it should care: that's the network layer's problem, and
> there will often be multiple routes between the source and destination
> that are invisible to ntp anyway.

ntpd is much too involved in network stuff.  it should just bind to
:::123 and be done with it.

I read that a recent change now finally makes this possible, but it
has not yet landed in the stable version.

You can then config:

listen-on all ignore
listen-on wild

More information about the questions mailing list