From: Tom Marshall <tmarshall@real.com>
To: netdev@oss.sgi.com
Subject: Problem with dual IPv4/IPv6 connect
Date: Tue, 16 Nov 2004 15:24:09 -0800 [thread overview]
Message-ID: <20041116232409.GB26264@real.com> (raw)
[-- 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 --]
reply other threads:[~2004-11-16 23:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041116232409.GB26264@real.com \
--to=tmarshall@real.com \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).