Julien Cristau wrote:
An AF_INET6 socket, by default, can receive both ipv4 and ipv6
connections (unless configured otherwise with the net/ipv6/bindv6only
sysctl, or the IPV6_V6ONLY setsockopt).
Adam, what does /proc/sys/net/ipv6/bindv6only contain on your system?
0
approx calls bind() to in
On Sat, Apr 5, 2008 at 12:27:59 -0400, Eric Cooper wrote:
> On Sat, Apr 05, 2008 at 10:26:27AM -0400, Adam Spragg wrote:
> > The reason is due to the nature of the IPv6 support that has been added.
> > This seems to stop IPv4 being used if an IPv6 address is found. While
> > the server I run
Eric Cooper wrote:
I've added code that attempts to listen on both an IPv6 and IPv4
socket, but once it creates the IPv6 socket and binds it to port ,
the subsequent attempt to bind an IPv4 socket to fails with
"address already in use". (I don't know IPv6 well enough to
understand this.
On Sat, Apr 05, 2008 at 10:26:27AM -0400, Adam Spragg wrote:
> The reason is due to the nature of the IPv6 support that has been added.
> This seems to stop IPv4 being used if an IPv6 address is found. While
> the server I run approx on has an IPv6 address, my network is not
> properly config
Sorry for the regression: I don't have a very advanced IPv6 setup
here, and just tried a few simple tests before assuming it was OK.
I opened a bug against approx with your email.
I'll make the server listen on both kinds of sockets, if possible, or
else I'll provide a config parameter to force
Package: approx
Version: 3.1.0
Severity: grave
Just wanted to say that I've been using approx for a while now and am
generally a big fan of it, but a recent upgrade to 3.1.0 broke my setup. :(
The reason is due to the nature of the IPv6 support that has been added.
This seems to stop IPv4 bei
6 matches
Mail list logo
