netdev
[Top] [All Lists]

Re: RFC 3484 support

To: kuznet@xxxxxxxxxxxxx
Subject: Re: RFC 3484 support
From: Ulrich Drepper <drepper@xxxxxxxxxx>
Date: Thu, 13 Nov 2003 15:12:37 -0800
Cc: netdev@xxxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx
In-reply-to: <200311131007.NAA23770@xxxxxxxxxxxxxxx>
Organization: Red Hat, Inc.
References: <200311131007.NAA23770@xxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20030925 Thunderbird/0.3
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

kuznet@xxxxxxxxxxxxx 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-----



<Prev in Thread] Current Thread [Next in Thread>