On Tue, 2007-07-17 at 15:21 +0100, Mike Williams wrote:
> On Tuesday 17 July 2007 15:12, Bernd Petrovitsch wrote:
> > > > If you fix your networking (i.e. get rid of the gratuitous IPv6 crap)
> > > > when you install your server, I don't think this is a problem.
> > >
> > > I disagree. If the system has IPv6 and IPv4, qpsmtpd of course should
> > > bind to both protocol versions and not only IPv6. This is clearly a
> > > bug.
> >
> > It's even more confusing: The Linux kernel (and only the Linux kernel)
> > has a feature that "bind on all interfaces" takes both of IPv4 and IPv6
> > interfaces/ip addresses. This is controlled via the the
> > "net.ipv6.bindv6only" sysctl.
> > Per default this is usually activated (which is IMHO a bad decision
> > because I wouldn't expect that) - at least on Debian/Sarge IIRC.
>
> Ahh, now that's even more interesting.
> I don't use Debian, and all my systems have net.ipv6.bindv6only set to 0,
> with
I try to keep away but I fail for various reasons. Fedora/CentOS is not
different in that thing BTW ....
> it set to 1 qpsmtpd behaves like Johan described.
It's (probably?) the intention that "everything works without change
now" is seen by admins (and up to FC6, there was some environment
variable somewhere where one could deactivate IPv6. FC7 doesn't have
that and now you must deactivate the loading of the IPv6 modules if you
do not want it).
Personally I think it's educating people in the wrong direction because
if they actually learn IPv6 and put their first "[::]:80"
into /etc/http/conf/httpd.conf (or similar), Apache won't start any
longer with "IP address in use" ....
> Just had a co-worker check a couple of his Debian boxes, and all of those
> have
> bindv6only set to 0.
Set it to "1" if you want to separate IPv4 from IPv6 configuration. It's
in my world somewhat standard nowadays .....
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
