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 configured for IPv6 yet, due to issues(tm). Which means that
> some of my other computers are unable to connect to the approx server,
> despite a perfectly good IPv4 network existing between them.
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 9999,
the subsequent attempt to bind an IPv4 socket to 9999 fails with
"address already in use". (I don't know IPv6 well enough to
understand this. Do you?)
But my IPv4 clients can still connect fine, even though the server is
only listening on an IPv6 socket at this point. I suppose this is
what gave me (false?) confidence that it was working well enough to
release.
Anyway, the new version is at
http://www.cs.cmu.edu/~ecc/approx_3.2.0_i386.deb
Would you be able to see if it works in your environment? If so, I'll
go ahead and upload it to unstable.
--
Eric Cooper e c c @ c m u . e d u
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
