On Wed, 09 Dec 2009 03:00:38 -0500 Jacob Heider <[email protected]> wrote:
> I tried using 4.1.1+X4.3.0-34 but it would only bind to the IPv6 port.
> After reverting, I read the bug report for #550789. It looks like the
> patch respects the value of /proc/sys/net/ipv6/bindv6only, which the
> submitter claims defaults to 0. I have an /etc/sysctl.d/bindv6only.conf
> (which doesn't seem to belong to any package) which states the
> following:
>
> ----
>
> # This sysctl sets the default value of the IPV6_V6ONLY socket option.
> #
> # When disabled, IPv6 sockets will also be able to send and receive IPv4
> # traffic with addresses in the form ::ffff:192.0.2.1 and daemons
> # listening
> # on IPv6 sockets will also accept IPv4 connections.
> #
> # When IPV6_V6ONLY is enabled, daemons interested in both IPv4 and IPv6
> # connections must open two listening sockets.
> # This is the default behaviour of all modern operating systems.
>
> net.ipv6.bindv6only = 1
>
> ----
>
> Now, I don't have any reason to retain that file that I know of, but my
> concerns are two-fold:
>
> 1) some package has created this file at some point
This file is introduced by a very recent update to netbase:
netbase (4.38) unstable; urgency=low
* Create /etc/sysctl.d/bindv6only.conf on upgrades and new installs
to set net.ipv6.bindv6only=1.
<...>
-- Marco d'Itri <[email protected]> Sun, 06 Dec 2009 17:09:41 +0100
This will break many other apps too, e.g. http://bugs.debian.org/560056
To fix the issue you'll need to change that setting back to 0:
sudo sed -i 's/net.ipv6.bindv6only\ =\ 1/net.ipv6.bindv6only\ =\ 0/' \
/etc/sysctl.d/bindv6only.conf && sudo invoke-rc.d procps restart
There's a discussion on the matter here:
http://old.nabble.com/defaulting-to-net.ipv6.bindv6only%3D1-for-squeeze-td26041698.html
--
With respect,
Roman
signature.asc
Description: PGP signature
