LinuxQuestions.org
Visit Jeremy's Blog.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices


Reply
  Search this Thread
Old 12-05-2014, 06:48 AM   #1
tpotter01
LQ Newbie
 
Registered: Dec 2014
Location: Lapeer, MI
Posts: 2

Rep: Reputation: Disabled
ntpd fails to bind on multicast address


I am trying to setup an ntpd client where it receives its ntp updates from a multicast address. I have a very simple ntp.conf file:

Code:
# This is the most basic ntp configuration file
driftfile /etc/ntp.drift
disable auth
multicastclient ff02::101 
server 127.127.1.0
But in the log file I am getting a binding error:
Code:
31 Mar 21:35:45 ntpd[1323]: ntpd 4.2.7p482@1.2483-o Thu Dec  4 19:26:52 UTC 2014
 (1): Starting                                                                  
31 Mar 21:35:45 ntpd[1323]: Command line: /usr/bin/ntpd -g -p /var/run/ntpd.pid 
-l /tmp/ntp.log                                                                 
31 Mar 21:35:45 ntpd[1324]: proto: precision = 3.458 usec (-18)                 
31 Mar 21:35:45 ntpd[1324]: Listen and drop on 0 v6wildcard [::]:123            
31 Mar 21:35:45 ntpd[1324]: Listen and drop on 1 v4wildcard 0.0.0.0:123         
31 Mar 21:35:45 ntpd[1324]: Listen normally on 2 lo 127.0.0.1:123               
31 Mar 21:35:45 ntpd[1324]: Listen normally on 3 lo [::1]:123                   
31 Mar 21:35:45 ntpd[1324]: Listen normally on 4 eth0 [2001:0:bc:6a:29:c6:d4:85]
:123                                                                            
31 Mar 21:35:45 ntpd[1324]: Listen normally on 5 eth0 [fe80::be6a:29ff:fec6:d485
%3]:123                                                                         
31 Mar 21:35:45 ntpd[1324]: Listen normally on 6 eth1 [2001:0:bc:6a:29:c6:d4:86]
:123                                                                            
31 Mar 21:35:45 ntpd[1324]: Listen normally on 7 eth1 [fe80::be6a:29ff:fec6:d486
%4]:123                                                                         
31 Mar 21:35:45 ntpd[1324]: Listening on routing socket on fd #24 for interface 
updates                                                                         
31 Mar 21:35:45 ntpd[1324]: bind(25) AF_INET6 ff02::101#123 (multicast) flags 0x
0 failed: Invalid argument                                                      
31 Mar 21:35:45 ntpd[1324]: multicast address ff02::101 using wildcard interface
 #0 v6wildcard                                                                  
31 Mar 21:35:45 ntpd[1324]: Joined :: socket to multicast group ff02::101
Using tcpdump I can see that my client is receiving the ntp messages:
Code:
21:37:03.219064 IP6 2001::e:c6:89:4c:95.ntp > ff02::101.ntp: NTPv4, Broadcast, l
ength 48                                                                        
21:38:09.218618 IP6 2001::e:c6:89:4c:95.ntp > ff02::101.ntp: NTPv4, Broadcast, l
ength 48                                                                        
21:39:14.222485 IP6 2001::e:c6:89:4c:95.ntp > ff02::101.ntp: NTPv4, Broadcast, l
ength 48                                                                        
21:40:21.217755 IP6 2001::e:c6:89:4c:95.ntp > ff02::101.ntp: NTPv4, Broadcast, l
ength 48                                                                        
21:41:25.219654 IP6 2001::e:c6:89:4c:95.ntp > ff02::101.ntp: NTPv4, Broadcast, l
ength 48                                                                        
21:42:29.215868 IP6 2001::e:c6:89:4c:95.ntp > ff02::101.ntp: NTPv4, Broadcast, l
ength 48                                                                        
21:43:34.214342 IP6 2001::e:c6:89:4c:95.ntp > ff02::101.ntp: NTPv4, Broadcast, l
ength 48
As you can see from the time stamps, ntp is not adjusting the time (this was done at 7:50 AM EST on Dec 5 2014).

I have this running on Linux 3.12. It is versoin 4.2.7p482 of ntpd.
 
Old 12-05-2014, 07:31 AM   #2
tpotter01
LQ Newbie
 
Registered: Dec 2014
Location: Lapeer, MI
Posts: 2

Original Poster
Rep: Reputation: Disabled
I think I just found a fix. I used the following multicast address:

ff05::101

Apparently this is the one assigned to NTP. Once I did that the bind error went away and my time synced.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
service ntpd restart fails ramseyrt Linux - Newbie 2 04-23-2013 07:25 AM
bind() fails with EADDRNOTAVAIL after calling an SIOCSIFADDR ioctl for IPV6 address lprasanna Linux - Networking 2 08-15-2011 02:29 PM
Getting Multicast Address from recvfrom tara Programming 1 03-04-2010 11:44 AM
How to ping to multicast address ? vino87 Linux - Newbie 1 06-26-2009 08:46 AM
ntpd time synchonization fails ... shamilson Linux - Networking 9 08-11-2006 01:17 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Server

All times are GMT -5. The time now is 07:52 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration