Bug#771918: Possible fix

2014-12-04 Thread Tristan Seligmann
On 4 December 2014 at 15:58, Thomas Goirand wrote: > Do you guys think I should try to get this patch in Jessie? Or is it not > worth bothering the Debian release team? Without it, it's very hard to use miniupnpd when v6 is configured; changing the bindv6only sysctl will probably break other soft

Bug#771918: Possible fix

2014-12-04 Thread Thomas Goirand
On 12/04/2014 09:12 PM, Tristan Seligmann wrote: > On 4 December 2014 at 14:36, miniupnp wrote: >> Le 03/12/2014 14:42, Tristan Seligmann a écrit : >>> It looks like setting V6SOCKETS_ARE_V6ONLY in the config fixes this. >>> There is some detection using sysctl (which is a bit broken since the >>>

Bug#771918: Possible fix

2014-12-04 Thread miniupnp
Le 03/12/2014 14:42, Tristan Seligmann a écrit : > It looks like setting V6SOCKETS_ARE_V6ONLY in the config fixes this. > There is some detection using sysctl (which is a bit broken since the > settings on the build system may not match the settings on the target > system) for this on *BSD, but not

Bug#771918: Possible fix

2014-12-04 Thread Tristan Seligmann
On 4 December 2014 at 14:36, miniupnp wrote: > Le 03/12/2014 14:42, Tristan Seligmann a écrit : >> It looks like setting V6SOCKETS_ARE_V6ONLY in the config fixes this. >> There is some detection using sysctl (which is a bit broken since the >> settings on the build system may not match the setting

Bug#771918: Possible fix

2014-12-03 Thread Tristan Seligmann
It looks like setting V6SOCKETS_ARE_V6ONLY in the config fixes this. There is some detection using sysctl (which is a bit broken since the settings on the build system may not match the settings on the target system) for this on *BSD, but nothing to set this flag for Linux. -- mithrandi, i Ainil e