On Sun, Mar 16, 2008 at 08:46:04PM +0100, Stefan Fritsch wrote: > On Friday 14 March 2008, Michael Mende wrote:
Sorry for late reply, I haven't got copy of this mails. >> From apache docs [1]: >> >> "On the other hand, on some platforms such as Linux and Tru64 the >> only way to handle both IPv6 and IPv4 is to use mapped addresses." >> Mapping is default on Linux (in contrary to FreeBSD, NetBSD, and >> OpenBSD). > > I think the problem here is that for Apache, enable/disable-v4-mapped > is a compile-time option, but for linux the behaviour can be changed > at runtime by writing to /proc/sys/net/ipv6/bindv6only. Supporting > both variants without recompiling apache looks like a valid feature > request. It is possible that apache upstream is not aware of > the /proc interface. 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. Cheers, Jarek. -- Linux jest darmowy, jeśli twój czas nie przedstawia żadnej wartości. Jeśli jest coś warty(czas), Linux jest po prostu tańszy od innych. Jarek Kamiński gg# 453620 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]