[ntp:questions] ntp broadcast not working with IPv6

Danny Mayer mayer at ntp.org
Thu Dec 8 04:28:23 UTC 2011


On 12/7/2011 11:15 PM, rakesh v wrote:
> Thanks for your inputs Danny.
> 
> Hi Dave,
> Can you give your inputs on this below issue?
> Is the socket bind failing due to the reuse of the udp port 123. But I
> assume for ntp multicast client also we use the same port for listening.
> Or Is it due to some other issue?
> 

I think it is trying to bind to the incorrect address but I'd have to
look carefully at the code to figure out exactly what is going on.

Danny

> 
> 
> On Wed, Dec 7, 2011 at 6:34 PM, Danny Mayer <mayer at ntp.org
> <mailto:mayer at ntp.org>> wrote:
> 
>     On 12/7/2011 4:53 AM, rakesh v wrote:
>     > Hi Danny,
>     > Actually I ran the ntpd with Debug option before with a downloaded
>     > source code (ntp-4.26p4).
>     >
>     >
>     > These are the logs Iam seeing on the client side...
>     >
>     > /6 Dec 06:11:52 ntpd[2884]: set_process_priority: Leave priority
>     alone:
>     > priority_done is <2>/
>     > / 6 Dec 06:11:52 ntpd[2884]: proto: precision = 0.208 usec/
>     > / 6 Dec 06:11:52 ntpd[2884]: ntp_io: estimated max descriptors: 1024,
>     > initial socket boundary: 16/
>     > / 6 Dec 06:11:52 ntpd[2884]: Listen and drop on 0 v4wildcard
>     0.0.0.0 UDP
>     > 123/
>     > / 6 Dec 06:11:52 ntpd[2884]: Listen and drop on 1 v6wildcard ::
>     UDP 123/
>     > / 6 Dec 06:11:52 ntpd[2884]: Listen normally on 2 lo 127.0.0.1 UDP
>     123/
>     > / 6 Dec 06:11:52 ntpd[2884]: Listen normally on 3 eth1 10.16.34.6
>     UDP 123/
>     > / 6 Dec 06:11:52 ntpd[2884]: Listen normally on 4 lo ::1 UDP 123/
>     > / 6 Dec 06:11:52 ntpd[2884]: Listen normally on 5 eth2 2000::2 UDP
>     123/
>     > / 6 Dec 06:11:52 ntpd[2884]: Listen normally on 6 eth1
>     > fe80::a00:27ff:fe68:7b4c UDP 123/
>     > / 6 Dec 06:11:52 ntpd[2884]: Listen normally on 7 eth2
>     > fe80::a00:27ff:fe38:605 UDP 123/
>     > / 6 Dec 06:11:52 ntpd[2884]: peers refreshed/
>     > / 6 Dec 06:11:52 ntpd[2884]: Listening on routing socket on fd #24 for
>     > interface updates/
>     > / *6 Dec 06:11:52 ntpd[2884]: bind(25) AF_INET6 ff02::101#123
>     > (multicast) flags 0x0 failed: Invalid argument*/
>     > / 6 Dec 06:11:52 ntpd[2884]: multicast address ff02::101 using
>     wildcard
>     > interface #1 v6wildcard/
>     > / 6 Dec 06:11:52 ntpd[2884]: Joined :: socket to multicast group
>     ff02::101/
>     > /
>     > /
>     > Actually Iam able to see only one Broadcast packet being received on
>     > client side in wireshark. Packets are not received.
>     > Here Iam not sure why the socket bind is failing for ntpd? Any
>     inputs on
>     > this?
> 
>     That sounds like a bug. I haven't looked at that area of the code
>     recently but being unable to bind to the socket would prevent it
>     receiving packets. Dave Hart has touched this area recently may will
>     likely know more. I do remember some issues with multicast but I don't
>     remember this one.
> 
>     Danny
> 
> 
> 
> 
> -- 
> Thanks & Regs,
> Rakesh
> 
> 



More information about the questions mailing list