Bug 10702 - xntpd doesn't allow to specify the bind interface(s)
xntpd doesn't allow to specify the bind interface(s)
Product: Red Hat Linux
Classification: Retired
Component: xntp3 (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnson
Depends On:
  Show dependency treegraph
Reported: 2000-04-10 13:44 EDT by samkaski
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-04-10 13:44:33 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description samkaski 2000-04-10 13:44:33 EDT
Reading the SRPMS of the newest xntpd it appears to me that
xntpd always binds to all active interfaces including ip aliases.
This might not be the wanted behaviour. Eg. named allows to specify
the interfaces that are bound to. Now I'm forced to add firewall
rules for all the ip aliases I don't want to offer NTP.
Comment 1 Pekka Savola 2000-07-18 03:15:03 EDT
In ntp-4.0 (e.g. ntp-4.0.99j-0.1), ntpd will only bind to the primary interface,
not aliases.

Work is in progress (probably due 4.1) to allow you to define interfaces to bind
to in /etc/ntp.conf.

Note You need to log in before you can comment on or make changes to this bug.