On Sat, Jun 07, 2008 at 03:46:23PM +0200, Stefan Fritsch wrote:
>> Yup, that's my case.
>> #v+
>> [EMAIL PROTECTED] ~]% /sbin/sysctl net.ipv6.bindv6only
>> net.ipv6.bindv6only = 1
>> #v-
>> 
>>> Maybe we should put a hint in README.Debian that our apache supports 
>>> only net.ipv6.bindv6only = 0 at the moment.
>> 
>> Please don't require reconfiguring whole system. If it's only
>> configuration supported by apache, maybe it should setsockopt
>> (IPV6_V6ONLY) its sockets? This way it could revert to
>> net.ipv6.bindv6only=0 only on its sockets, without touching rest of
>> system.
> 
> if you have the time, you could try recompiling apache2 with the line
> "017_fix_ipv6" removed from the file debian/patches/00list and check if that 
> fixes the problem.
Yes, with the patch removed everything works fine.

I have tested two configurations, one with
#v+
Listen [::]:80
Listen 0.0.0.0:80
#v-
and one with Listen [::]:80 only (both with net.ipv6.bindv6only = 1).
Apache behaves identically in both cases and listens only on [::]:80,
but accepts also IPv4 connections (so it sets IPV6_V6ONLY).

Thanks for identifying cause of problem and sorry for late reply,
Jarek.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to