KP Kirchdoerfer wrote:
> Erich;
> 
> On Monday 07 January 2008 22:27:04 Erich Titl wrote:
>> KP
>>
>> KP Kirchdoerfer schrieb:
>>> On Monday 07 January 2008 14:42:56 Erich Titl wrote:
>>>> Hi Eric
>>>>
>>>> Eric Spakman wrote:
>>>>> Hi Erich,
>>>>>
>>>>> Because it works for KP, did you make any change to the ntpd package or
>>>>> did you compile your own?
>>>> To start with, no. I am using the one that works fine with 3.1beta1. I
>>>> just compiled it today to have a debug image, but the output is
>>>> insufficient to find the individual line where it fails.
> 
> I installedd initrd from beta1 (busybox 1.5.0svn) and see the same error: 
> ntpd 
> does not start with ipv6 enabled.
> 
> running ntpd with -ddd shows:
> addto_syslog: Listening on interface #0 wildcard, 0.0.0.0#123 Disabled
> addto_syslog: bind() fd 17, family 10, port 123, scope 0, addr ::,
> in6_is_addr_multicast=0 flags=129 fails: Address already in use

I will run the same on my system to see if I hang on the ipv6 stuff, but 
I am pretty sure I don't have IPv6

> 
> I also found an explanation (for you:)):
> 
> "I've seen this problem with other programs under linux's ipv6.  The
> problem is that the linux stack unlike the Kame stack used in BSD's
> uses mapped ipv4 addresses in ipv6.  If one opens up a whildcard
> listening socket for both the ipv4 stack (with AF_INET) and then again
> for the ipv6 stack (with AF_INET6), one ends up trying to open the v4
> port a second time through the mapped-address.  The trick is to only
> open up the AF_INET6 socket - it implies the ipv4 mapping.

Makes sense to me.

> 
> I imagine this effects any daemon listening on an ipv6 socket in
> linux." 
> (Wolfgang S. Rupprecht                http://www.wsrcc.com/wolfgang/)
> 
> So there are a few options:
> 1) be shure to disable ipv6
> 2) we generate a ntpd for ipv4 only cause it doesn't work for ipv6 at all
> 3) you can change kernel behaviour like that
> "echo 1 > /proc/sys/net/ipv6/bindv6only";
> but this may affect other daemons supporting ipv4 and ipv6 as well, so it 
> needs testing and seems not a good recommendation.
> 
> I tested all of the above successfully with bb 1.7.3 and bb 1.8.2.
> 
> I tend to follow option 2.

So would I, option 3 looks appealing too, but I don't know about other 
inconveniences.

Thanks

Erich






-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace

_______________________________________________
leaf-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to