RE: ntp-unstable-simple
On Tue, 6 May 2003, Jeroen Massar wrote:
> > me has usagi
> > as well. I am not sure still where the problem is located in
> > the code but
> > this is a workaround:
> >
> > /etc/init.d/ntp-unstable-simple stop
> > echo 1 > /proc/sys/net/ipv6/bindv6only
> > /etc/init.d/ntp-unstable-simple start
> > echo 0 > /proc/sys/net/ipv6/bindv6only
> >
> > that i will implement in the init.d script for -2 until a
> > proper fix will be available.
>
> Aha, this is the eeky part, as USAGI is a bit more like *BSD
> who bind to both IPv4 and IPv6 at the same time. Stock kernels
> don't do that though, so the ntpd code probably binds to both
> IPv4 and IPv6 seperatly...
>
> The "fix" is in ignoring the failure when binding to IPv4 after
> you have succesfully bound to IPv6 already. Though logging the
> failure with a warning/informational message is quite nice.
Actually the behaviour is quite weird. on stock kernels it binds
correctly:
tedfabi@vega:~$ netstat -an | grep 123
udp 0 0 130.XXX.254.2:123 0.0.0.0:*
udp 0 0 213.YYY.189.100:123 0.0.0.0:*
udp 0 0 127.0.0.1:123 0.0.0.0:*
udp 0 0 0.0.0.0:123 0.0.0.0:*
udp 0 0 :::123 :::*
USAGI with bindv6only = 0 should behave like a stock kernel and instead it
binds only in ipv4 with that error message reported.
with bindv6only = 1 USAGI behaves like BSD.
So actually I am quite confused on what is wrong where. I would expected
the other way around on USAGI kernels.... cosmic rays interfering with my
wires? :-)
Fabio
--
Our mission: make IPv6 the default IP protocol
"We are on a mission from God" - Elwood Blues
http://www.itojun.org/paper/itojun-nanog-200210-ipv6isp/mgp00004.html
Reply to: