Closed GoogleCodeExporter closed 9 years ago
Seems that this will happen on a machine with IPv4 and IPv6 addresses enabled,
I'm
not sure if the burden should be on the server to have two listening sockets,
or on
the Client to filter out by IPv4.
I'm leaning towards the server now though, since it assures forward
compatibility
with IPv6.
Original comment by warrior...@gmail.com
on 7 Jan 2009 at 2:36
Through more investigation, this is still a bug. TcpClient defaults to
InterNetwork
as the AddressFamily, so even if I updated my server with IPv6 support (Created
a
separate listener) it still will fail when the DNS tries to resolve.
Original comment by warrior...@gmail.com
on 7 Jan 2009 at 2:48
Original comment by myndf...@valhallalegends.com
on 1 Aug 2009 at 4:59
Original comment by myndf...@valhallalegends.com
on 15 Jul 2011 at 1:23
Fixed in r41.
Original comment by myndf...@valhallalegends.com
on 15 Jul 2011 at 1:27
Original issue reported on code.google.com by
warrior...@gmail.com
on 7 Jan 2009 at 2:28