Arch Linux

lmello

Member

From: Brazil

Registered: 2012-11-06

Posts: 300

ntpd and ipv6

Hi,

When starting ntpd, I always get on my journal something like this:

May 15 16:10:40 maxwell ntpd[5712]: bind(24) AF_INET6 fe80::864b:f5ff:fedc:1155%3%3#123 flags 0x11 failed: Cannot assign requested address
May 15 16:10:40 maxwell ntpd[5712]: unable to create socket on wlan0 (6) for fe80::864b:f5ff:fedc:1155%3#123
May 15 16:10:40 maxwell ntpd[5712]: failed to init interface for address fe80::864b:f5ff:fedc:1155%3

Is there something *terribly* wrong? My ntp.conf file:

# With the default settings below, ntpd will only synchronize your clock.
#
# For details, see:
# - the ntp.conf man page
# - http://support.ntp.org/bin/view/Support/GettingStarted
# - https://wiki.archlinux.org/index.php/Network_Time_Protocol_daemon

# Associate to public NTP pool servers; see http://www.pool.ntp.org/
server 0.pool.ntp.org iburst
server 1.pool.ntp.org iburst
server 2.pool.ntp.org iburst

# Only allow read-only access from localhost
restrict default noquery nopeer
restrict 127.0.0.1
restrict ::1

# Location of drift file
driftfile /var/lib/ntp/ntp.drift

?

Last edited by lmello (2014-05-15 19:33:23)

---

Fundamental Axiom of the Universe (aka Murphy's Law): Whatever can go wrong, will go wrong.
First Digital Deduction: Nothing obeys Murphy's Law so well as computers.
Second Digital Deduction: Everything go wrong at least once.
Third Digital Deduction: Things go wrong even when there's absolutely no possibility of anything go wrong.

rsmarples

Member

Registered: 2009-05-12

Posts: 287

Re: ntpd and ipv6

IPv6 addresses start off in the Tentative state.
This means whilst they can be seen via ip and ifconfig they cannot be used until Duplicate Address Detection has completed.
Once completed, the kernel notifiers listeners the address can now be used.

NTP listens for new addresses, but doesn't check the state - it only does when it starts up.
Basically NTP needs to listen for the tentative flag to be removed before using the address.