netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Problem with dual IPv4/IPv6 connect
@ 2004-11-16 23:24 Tom Marshall
  0 siblings, 0 replies; only message in thread
From: Tom Marshall @ 2004-11-16 23:24 UTC (permalink / raw)
  To: netdev

[-- Attachment #1: Type: text/plain, Size: 936 bytes --]

I'm using kernel 2.6.9 from kernel.org and I think I found a small problem
in the dual IPv4/IPv6 connect code.  Here's what happens:

[Note both peer addresses are the same (Solaris 9) machine]

  s = socket(AF_INET6, SOCK_STREAM, 0)
  connect(s, [fec0::203:baff:fe88:5a15]:1554) => EINPROGRESS
  Put socket in select's write set
  Kernel sends TCPv6 SYN
  Kernel receives ICMPv6 Time Exceeded (routing error)
  Socket becomes writable
  getsockopt(s, SO_ERROR) => EHOSTUNREACH
  connect(s, 192.168.168.241:1554) => ECONNABORTED

At this point, if I call connect again with the same arguments, it behaves
normally: EINPROGRESS followed by success.  This leads me to believe that
the IPv6 connect has not updated the socket state properly.

-- 
At Group L, Stoffel oversees six first-rate programmers, a managerial
challenge roughly comparable to herding cats.
        -- The Washington Post Magazine, 9 June, 1985

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2004-11-16 23:24 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-11-16 23:24 Problem with dual IPv4/IPv6 connect Tom Marshall

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).