From: Ulrich Drepper <drepper@redhat.com>
To: kuznet@ms2.inr.ac.ru
Cc: netdev@oss.sgi.com, yoshfuji@linux-ipv6.org
Subject: Re: RFC 3484 support
Date: Thu, 13 Nov 2003 15:12:37 -0800 [thread overview]
Message-ID: <3FB40FE5.5040709@redhat.com> (raw)
In-Reply-To: <200311131007.NAA23770@yakov.inr.ac.ru>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
kuznet@ms2.inr.ac.ru wrote:
>>1. use the existing kernel functionality and provide an interface to it
>> which userlevel can use
>
>
> This interface is connect() for example. Essentially, connect() on
> datagram socket with subsequent getsockname() makes exactly this.
Wouldn't this require to set up a socket and connect it to each target
address? The point of the whole source and destination address
selection is it to avoid making connections with addresses/via
interfaces which might have problems. getaddrinfo returns a list of
addresses which a client program then tries in the order they are
provided. The address which has the highest rate of success and the
highest quality for the connection should be tried first. And all this
is subject to all the customization and configuration going in the kernel.
- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE/tA/l2ijCOnn/RHQRAiYcAKCjgzJXwd/zV7KaWBUnaIqNEUdHrgCeKq5g
pQm7ViT1UChv0DtqKaxkdiY=
=/Jay
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-11-13 23:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-12 1:05 RFC 3484 support Ulrich Drepper
2003-11-13 10:07 ` kuznet
2003-11-13 13:26 ` Pekka Savola
2003-11-13 23:17 ` Ulrich Drepper
2003-11-13 23:29 ` Pekka Savola
2003-11-13 23:12 ` Ulrich Drepper [this message]
2003-11-14 23:45 ` kuznet
2003-11-18 8:59 ` Ulrich Drepper
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=3FB40FE5.5040709@redhat.com \
--to=drepper@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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).