Debian Bug report logs - #574837
listen_ipv6 should set IPV6_V6ONLY socket option

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: David Madore <david+bugs@madore.org>

To: submit@bugs.debian.org

Subject: vsftpd: listen_ipv6 should set IPV6_V6ONLY socket option to its desired value

Date: Sun, 21 Mar 2010 16:49:43 +0100

Package: vsftpd
Version: 2.3.0~pre1-1

There seems to be a trend in Debian and/or Linux to activate the
sysctl net.ipv6.bindv6only=1 by default, meaning that binding on the
IPv6 unspecified address (::) will not also bind IPv4 (contrarily to
the former Linux tradition).  This means that running vsftpd with
listen_ipv6=YES will ONLY listen on IPv6, not IPv4, whereas formerly
it listened to both.  (I discovered this by noticing that my ftp
server had stopped responding to IPv4 and was only reachable through
IPv6.)

Possible solutions:

* Advise sysadmins installing vsftpd to set net.ipv6.bindv6only=0.
  This does not seem desirable, however, as it goes against the
  current trend.

* Advise sysadmins to run two different copies of vsftpd, one for IPv4
  only and one for IPv6 only.  This is inconvient with the startup
  scripts provided by Debian, however.

* Advise sysadmins to run vsftpd from inetd or xinetd.  This also goes
  against current trends, however, since all flavors of inetd seem to
  be dying out.

* Use setsockopt(..., IPPROTO_IPV6, IPV6_V6ONLY, ...) to set
  IPV6_V6ONLY to 0 on the vsftpd socket when listening on IPv6, so as
  to request binding on IPv4 only.  Or, even better, make this an
  option.  This would be my preferred solution.

* Allow vsftpd to run with both listen and listen_ipv6.

-- 
     David A. Madore
   ( http://www.madore.org/~david/ )

Message #12 received at 574837@bugs.debian.org (full text, mbox, reply):

From: Jan Wagner <waja@cyconet.org>

To: 574837@bugs.debian.org

Cc: control@bugs.debian.org

Subject: Re: vsftpd: listen_ipv6 should set IPV6_V6ONLY socket option to its desired value

Date: Thu, 24 Jan 2013 11:15:05 +0100

[Message part 1 (text/plain, inline)]

tags 574837 + patch
thanks

Hi there,

Am 21.03.2010 16:49, schrieb David Madore:
> * Allow vsftpd to run with both listen and listen_ipv6.

is there any chance to get that fixed. Using the following works on IPv4
and IPv6:

listen=NO
listen_ipv6=YES

So there is just a fix for the documentation needed. I'll attached the
patch from fedora.

Many thanks, Jan.
-- 
Never write mail to <waja@spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GIT d-- s+: a C+++ UL++++ P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS
PE Y++
PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h---- r+++ y++++
------END GEEK CODE BLOCK------

[vsftpd-2.3.4-listen_ipv6.patch (text/x-patch, attachment)]

[signature.asc (application/pgp-signature, attachment)]

Message #19 received at 574837@bugs.debian.org (full text, mbox, reply):

From: Daniel Baumann <daniel.baumann@progress-technologies.net>

To: Jan Wagner <waja@cyconet.org>

Cc: 574837@bugs.debian.org

Subject: Re: Bug#574837: vsftpd: listen_ipv6 should set IPV6_V6ONLY socket option to its desired value

Date: Thu, 24 Jan 2013 11:24:04 +0100

On 01/24/2013 11:15 AM, Jan Wagner wrote:
> is there any chance to get that fixed.

if you send a patch, which you did (thanks), surely ;)

-- 
Address:        Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern
Email:          daniel.baumann@progress-technologies.net
Internet:       http://people.progress-technologies.net/~daniel.baumann/

Message #24 received at 574837@bugs.debian.org (full text, mbox, reply):

From: Thorsten Glaser <tg@mirbsd.de>

To: 574837@bugs.debian.org

Subject: Listening on [::] will *not* always listen on 0.0.0.0

Date: Thu, 24 Jan 2013 17:26:46 +0100 (CET)

Hi,

on “doble stack” systems, listening on [::] will only receive
IP connections, not Legacy IP connections, so you *must* be
able to listen on both.

Examples for “doble stack” operation are the KAME BSD IPv6
stack, and Linux with the net.ipv6.bindv6only sysctl set to
1, which is intended to be the default eventually.

Ideally, a “just works” configuration would bind to [::],
then try to bind to 0.0.0.0 too (on a second socket()),
and just not fail if that fails, when asked to bind to “all”.

bye,
//mirabilos
-- 
«MyISAM tables -will- get corrupted eventually. This is a fact of life. »
“mysql is about as much database as ms access” – “MSSQL at least descends
from a database” “it's a rebranded SyBase” “MySQL however was born from a
flatfile and went downhill from there” – “at least jetDB doesn’t claim to
be a database”	(#nosec)    ‣‣‣ Please let MySQL and MariaDB finally die!

Send a report that this bug log contains spam.