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 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.
Hang on ... does this mean that 3.1.0 worked fine for you if you had
both IPv4 and IPv6 addresses on the server, but tried to connect from a
client with IPv4 only? If so, you're not seeing what I'm seeing.
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.
Ah. Afraid not. I'm on amd64, not i386. Sorry, should have mentioned
that earlier.
Adam
--
The fundamental cause of the trouble is that in the modern world the
stupid are cocksure while the intelligent are full of doubt.
-- Bertrand Russell
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
