Your message dated Mon, 20 Dec 2010 16:37:37 +0100 with message-id <20101220153737.GV5063@radis.liafa.jussieu.fr> and subject line Re: Bug#607305: Unblock request: prayer/1.3.3-dfsg1-3 (Re: Bug#607261) has caused the Debian Bug report #607305, regarding Unblock request: prayer/1.3.3-dfsg1-3 (Re: Bug#607261) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 607305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607305 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Unblock request: prayer/1.3.3-dfsg1-3 (Re: Bug#607261)
- From: Magnus Holmgren <holmgren@debian.org>
- Date: Thu, 16 Dec 2010 22:38:51 +0100
- Message-id: <[🔎] 201012162238.51914@proffe.kibibyte.se>
- In-reply-to: <201012162002.31103@proffe.kibibyte.se>
- References: <4D09E49F.8070205@m-taube.de> <201012162002.31103@proffe.kibibyte.se>
Package: release.debian.org Please consider unblocking prayer/1.3.3-dfsg1-3. It merely adds a patch setting the IPV6_V6ONLY socket option. * ipv6_v6only.patch (new): Set the IPV6_V6ONLY socket option on AF_INET6 sockets; since Prayer by default enumerates available address families and calls bind() once for each, conflicts will occur otherwise. On torsdagen den 16 december 2010, Magnus Holmgren wrote: > Actually, the bug is that Prayer tries to bind IPv4 and IPv6 sockets > separately without setting the IPV6_V6ONLY flag. That fails because when > the sysctl net.ipv6.bindv6only is set to 0 (after a long debate, the > default value on Debian), IPv6 sockets listening on [::] will also handle > IPv4 packets (with the remote address looking like ::ffff:1.2.3.4). > > So the problem occurs on dual-stack systems whether IPv6 actually works or > not, but not on systems without any IPv6 support at all. But thanks for > reporting anyway. I should have noticed it myself but for some reason never > really tried starting Prayer with net.ipv6.bindv6only=0. -- Magnus Holmgren holmgren@debian.org Debian DeveloperAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
- To: Magnus Holmgren <holmgren@debian.org>, 607305-done@bugs.debian.org
- Subject: Re: Bug#607305: Unblock request: prayer/1.3.3-dfsg1-3 (Re: Bug#607261)
- From: Julien Cristau <jcristau@debian.org>
- Date: Mon, 20 Dec 2010 16:37:37 +0100
- Message-id: <20101220153737.GV5063@radis.liafa.jussieu.fr>
- In-reply-to: <[🔎] 201012162238.51914@proffe.kibibyte.se>
- References: <4D09E49F.8070205@m-taube.de> <201012162002.31103@proffe.kibibyte.se> <[🔎] 201012162238.51914@proffe.kibibyte.se>
On Thu, Dec 16, 2010 at 22:38:51 +0100, Magnus Holmgren wrote: > Package: release.debian.org > > Please consider unblocking prayer/1.3.3-dfsg1-3. It merely adds a patch > setting the IPV6_V6ONLY socket option. > Unblocked, thanks. Cheers, JulienAttachment: signature.asc
Description: Digital signature
--- End Message ---