Message-ID:

Not only is UNIX dead, it's starting to smell really bad. -- Rob Pike

devel / comp.protocols.time.ntp / Re: ntp broadcast not working with IPv6

Re: ntp broadcast not working with IPv6

<8698002d-e374-426a-ab34-c89fcd0d3733n@googlegroups.com>

https://www.rocksolidbbs.com/devel/article-flat.php?id=271&group=comp.protocols.time.ntp#271

copy link Newsgroups: comp.protocols.time.ntp

X-Received: by 2002:ad4:4ee9:: with SMTP id dv9mr4852432qvb.41.1644497911800;
Thu, 10 Feb 2022 04:58:31 -0800 (PST)
X-Received: by 2002:a05:6808:1b0e:: with SMTP id bx14mr840268oib.9.1644497911397;
Thu, 10 Feb 2022 04:58:31 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.protocols.time.ntp
Date: Thu, 10 Feb 2022 04:58:31 -0800 (PST)
In-Reply-To: <b40f90a0-a435-4b2b-b814-8bb5065fd57b@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=94.188.251.12; posting-account=ZUvKMAoAAAB6eDwKOnHGVi2c9REG-RTP
NNTP-Posting-Host: 94.188.251.12
References: <CAG59Y3P9_CX1HZe8OKz9j=Y2kjm1aJbBCocsvJd7pJSWXF80_g@mail.gmail.com>
<4EDEDC88.7000506@ntp.org> <CAG59Y3Oum6ot7+u=rRhPfoy9RoqgCNQ7RF+JkXk7UEZFNk3kEQ@mail.gmail.com>
<4EDF6463.8090904@ntp.org> <CAG59Y3PNxH2tfqz1SLPiH-7BmhEsPYFHZY1mQ24X-B0qST2Gdg@mail.gmail.com>
<4EE03CE7.2070109@ntp.org> <b40f90a0-a435-4b2b-b814-8bb5065fd57b@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <8698002d-e374-426a-ab34-c89fcd0d3733n@googlegroups.com>
Subject: Re: ntp broadcast not working with IPv6
From: yuval05261@gmail.com (יובל פלד)
Injection-Date: Thu, 10 Feb 2022 12:58:31 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

by: יובל פלד - Thu, 10 Feb 2022 12:58 UTC

ב-יום חמישי, 9 בפברואר 2017 בשעה 00:16:32 UTC+2, ngr...@gmail.com כתב/ה:
> On Thursday, December 8, 2011 at 1:28:23 AM UTC-3, Danny Mayer wrote:
> >
> > 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.
> >
> Sorry to refloat this old thread, but this bug is still present on 4.2.6p5 and I think I discovered the cause:
>
> Ntpd is trying to bind() to the link-local multicast address ff02::101 *WITHOUT* specifying the scope id of the link local interface. The bind() strace is:
>
> bind(24, {sa_family=AF_INET6, sin6_port=htons(123), inet_pton(AF_INET6, "ff02::101", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = -1 EINVAL (Invalid argument)
>
> Note sin6_scope_id=0.
>
> Defining "multicastclient [ff02::101]%2" or "multicastclient [ff02::101]%eth0" or "multicastclient ff02::101" in ntp.conf also results in sin6_scope_id=0 and the same error.
>
> If you call bind() specifying sin6_scope_id=2 (the scope id of my link-local interface), the bind() call works. (I'm trying this on Ubuntu 16.10).

hi,

on the new ntpd, there is option to configure sin6_scope_id=2 from the ntp.conf file?
can we also configure one of mreq6.ipv6mr_interface or iface->ifindex on the ntp.conf?

thanks ,
Yuval Peled

Subject	Author
Re: ntp broadcast not working with IPv6	יובל פלד