From: Rick Jones <rick.jones2@hp.com>
To: Linux Network Development list <netdev@vger.kernel.org>
Subject: specifying scopid's for link-local IPv6 addrs
Date: Mon, 23 Jul 2007 12:01:19 -0700 [thread overview]
Message-ID: <46A4FAFF.8010809@hp.com> (raw)
Folks -
People running netperf have reported that they have trouble with IPv6 under
Linux. Specifically, wereas the use of link-local IPv6 addresses "just works"
in netperf under a number of "other OSes" they do not under Linux. I'm
ass-u-me-ing 2.6 here, but not sure exactly which ones - I've seen it on a
2.6.18-based RHEL5.
Some poking about and conversation has suggested that one has to set a
sin6_scope_id in the sockaddr_in6. This needs to be an index of one of the
interfaces in the system, which I presume means walking some additional structures.
Is this a requirement which might be expected to remain in the future, or is it
something which might just go away? That will have an effect on netperf future
development.
thanks,
rick jones
next reply other threads:[~2007-07-23 19:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 19:01 Rick Jones [this message]
2007-07-24 7:01 ` specifying scopid's for link-local IPv6 addrs Bill Fink
2007-07-24 17:13 ` Rick Jones
2007-07-24 17:23 ` Rick Jones
2007-07-24 17:28 ` Sridhar Samudrala
2007-07-25 6:15 ` Bill Fink
2007-08-01 14:25 ` Vlad Yasevich
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=46A4FAFF.8010809@hp.com \
--to=rick.jones2@hp.com \
--cc=netdev@vger.kernel.org \
/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).