Debian Bug report logs - #751418
irssiproxy does not work with bindv6only = 1

Reply or subscribe to this bug.

Display info messages

Message #5 received at [email protected] (full text, mbox, reply):

From: Thijs Kinkhorst <[email protected]>

To: Debian Bug Tracking System <[email protected]>

Subject: irssiproxy does not work with bindv6only = 1

Date: Thu, 12 Jun 2014 13:31:13 +0200

Package: irssi
Version: 0.8.15-5+b1
Severity: normal
Tags: ipv6

Hi,

When using irssiproxy with kernel setting bindv6only = 1 (which is the
default in Debain), irssi only binds to IPv6 and no longer accepts
IPv4 connections to the proxy. The only reason I found to fix this
is to disable bindv6only system-wide which is obviously undesirable.


Cheers,
Thijs


-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.13.7 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages irssi depends on:
ii  libc6                       2.19-1
ii  libglib2.0-0                2.40.0-3
ii  libncurses5                 5.9+20140118-1
ii  libperl5.18                 5.18.2-4
ii  libssl1.0.0                 1.0.1h-2
ii  libtinfo5                   5.9+20140118-1
ii  perl                        5.18.2-4
ii  perl-base [perlapi-5.18.1]  5.18.2-4

irssi recommends no packages.

Versions of packages irssi suggests:
ii  irssi-scripts  20131030

-- no debconf information

Message #10 received at [email protected] (full text, mbox, reply):

From: Gerfried Fuchs <[email protected]>

To: Thijs Kinkhorst <[email protected]>, [email protected]

Subject: Re: Bug#751418: irssiproxy does not work with bindv6only = 1

Date: Tue, 8 Jul 2014 14:50:10 +0200

* Thijs Kinkhorst <[email protected]> [2014-06-12 13:31:13 CEST]:
> When using irssiproxy with kernel setting bindv6only = 1 (which is the
> default in Debain), irssi only binds to IPv6 and no longer accepts
> IPv4 connections to the proxy. The only reason I found to fix this
> is to disable bindv6only system-wide which is obviously undesirable.

 Do I misunderstand something here?  The kernel says that things should
bind to v6 only, but you want it to ignore that and bind to v4, too?  Or
do I misinterpret that kernel setting?  Can you be more specific?
Either one wants stuff to bindv6only or one doesn't, I am uncertain why
an application should ignore the kernel preference here?

 Thanks for enlightning me,
Rhonda
-- 
Fühlst du dich mutlos, fass endlich Mut, los      |
Fühlst du dich hilflos, geh raus und hilf, los    | Wir sind Helden
Fühlst du dich machtlos, geh raus und mach, los   | 23.55: Alles auf Anfang
Fühlst du dich haltlos, such Halt und lass los    |

Message #15 received at [email protected] (full text, mbox, reply):

From: "Thijs Kinkhorst" <[email protected]>

To: [email protected]

Subject: Re: Bug#751418: irssiproxy does not work with bindv6only = 1

Date: Tue, 8 Jul 2014 15:17:00 +0200

On Tue, July 8, 2014 14:50, Gerfried Fuchs wrote:
> * Thijs Kinkhorst <[email protected]> [2014-06-12 13:31:13 CEST]:
>> When using irssiproxy with kernel setting bindv6only = 1 (which is the
>> default in Debain), irssi only binds to IPv6 and no longer accepts
>> IPv4 connections to the proxy. The only reason I found to fix this
>> is to disable bindv6only system-wide which is obviously undesirable.
>
>  Do I misunderstand something here?  The kernel says that things should
> bind to v6 only, but you want it to ignore that and bind to v4, too?  Or
> do I misinterpret that kernel setting?  Can you be more specific?
> Either one wants stuff to bindv6only or one doesn't, I am uncertain why
> an application should ignore the kernel preference here?

The short summary of the bug is: "On a default Debian installation,
irssiproxy is only reachable on IPv6, not IPv4.", so it's not something I
explicitly chose to change.

The reason is that Debian (as do other OS'es BTW) sets the kernel option
bindv6only to true. All the background can be read in this post by Marco:
https://lists.debian.org/debian-devel/2009/10/msg00541.html
but it boils down that if you would bind an AF_INET6 listening socket to
in your application, you used to get IPv4 "for free". With the setting
changed, the kernel behaves differently and the application needs to
explicitly create the AF_INET socket for IPv4 traffic. Nearly all
applications do this, it seems irssiproxy still needs to be changed to
account for this.


Cheers,
Thijs

Send a report that this bug log contains spam.