Olivier Péningault [EMAIL PROTECTED] writes:
le ven 25-10-2002 à 10:25, Niels Möller a écrit :
Sure, but do you really want them to run fully separately? It's common
(although not required by any standard, afaik), that an ipv6 socket
bound to the ipv6 wildcard interface should be able to
Olivier Péningault [EMAIL PROTECTED] writes:
le jeu 24-10-2002 à 21:49, Niels Möller a écrit :
ipv4 and ipv6 can run separatly.
Sure, but do you really want them to run fully separately? It's common
(although not required by any standard, afaik), that an ipv6 socket
bound to the ipv6 wildcard
BTW: the Plan9 approach to this separation is pretty similar:
There is a kernel namespace that provides ethernet functionality
(typically at /net/ether*), but a separate one that provides
IP,UDP,TCP on top of ethernet. Those were put into one,
as ICMP was needed for all and t reduce code
le ven 25-10-2002 à 10:25, Niels Möller a écrit :
Sure, but do you really want them to run fully separately? It's common
(although not required by any standard, afaik), that an ipv6 socket
bound to the ipv6 wildcard interface should be able to accept ipv4
connections.
In my opinion, we can
le jeu 24-10-2002 à 09:59, Niels Möller a écrit :
My advice is that you start by designing and implementing some kind of
ethernetdevice (kernelspace or part kernel, part userspace translator)
that can support running several pfinets in parallell. Perhaps it
should look like the bsd tunnel
le jeu 24-10-2002 à 21:49, Niels Möller a écrit :
You need one piece of code that links between glibc and your ip
interfaces, and that also performs packetforwarding, source and
destination address selection, and such stuff. That code should be
installed as the translator for
On Fri, Oct 25, 2002 at 01:08:30AM +0200, Olivier Péningault wrote:
le jeu 24-10-2002 à 21:49, Niels Möller a écrit :
I.e. when I call socket(), connect() to create a tcp connection, I
call some function in -lsocket
I see what you mean. For the layer 3+ translators, at first I thought
that
