[ntp:questions] Is there something with greater detail on "interface" besides the manpage?

Harlan Stenn stenn at ntp.org
Wed Nov 20 11:23:46 UTC 2013


Rob writes:
> Harlan Stenn <stenn at ntp.org> wrote:
> > Rick Jones writes:
> >> Harlan Stenn <stenn at ntp.org> wrote:
> >> > You might want:
> >> 
> >> >  interface ignore all
> >> >  interface listen 127.0.0.1     # if you want localhost ntpq to work
> >> >  interface listen a.b.c.d       # enumerate the IPs you want to use
> >> 
> >> Thanks.  I take it then that wildcard charaters in matching on
> >> interface names aren't a go :)
> >
> > Not yet, as best as I can recall.
> >
> >> My further complication is these systems get their IPs via DHCP (I
> >> should have listed that in the first place, sorry) and some are bonded
> >> and some are not bonded, but the component names of the interfaces in
> >> the bond(s) are the same "namespace" as when they are not bonded.  For
> >> example I may have systems with a bond0 using eth2 and eth3 and some
> >> systems just using eth2.  I *may* though be able to split the config
> >> files between such systems - that remains to be determined and if not
> >> is, arguably a failing at my end.
> >
> > How much info that NTP would care about would come from DHCP?
> 
> - the address of the local system
> - the addresses of the local NTP servers

So all of the other information (bonded interfaces, etc.) are handled
locally?  Does ntpd listen using the address of the local system or
some other address?

H


More information about the questions mailing list