Olivier Péningault <[EMAIL PROTECTED]> writes:
> I don't know where you saw this use of IPv6 address that automagically
> include IPv4 addresses.
I'm talking about the "IPv4-mapped IPv6 address", as defined in section 2.5.4 in
RFC 2373 (you've found it already).
The hack to let an ipv6 socket ac
Olivier Péningault <[EMAIL PROTECTED]> writes:
> le sam 26-10-2002 à 20:13, Niels Möller a écrit :
> > like, it could be the current pfinet interface (where is that defined?
> in /hurd/socket.defs
Thanks. There's one thing I don't understand: What's an "address"?
Like in
/* Create an address f
le sam 26-10-2002 à 20:13, Niels Möller a écrit :
I have one remark, and some questions about your proposal.
> Layer 3 (IPv4 and IPv6), part 1
> ~~~
> Tells the interface that we're interested in packets with the given
> ip-address. Can be a unicast or multicast a
Attn: Sir,
It is with heart full of hope that I write to seek your help in the context below. I
am Mr. Mr.Maxwell Ibu, the Personal Assistant to the late Nigerian former Sport
Minister, Late Mr. Mark Aku, who until his death in a domestic plane crash weeks
before the Japan / Korea world cup wa
le sam 26-10-2002 à 20:13, Niels Möller a écrit :
> Layer 4 interface
>
> like, it could be the current pfinet interface (where is that defined?
in /hurd/socket.defs
This is interesting, when I will have finished the update of the
implementation I propose, I will send it (tomorrow, I hope).
olivi
I've tried to ponder on what the interfaces to the layer2 and layer3
code should look like. I'm thinking primarily of ipv4 and ipv6 over
ethernet, but I hope it's not too difficult to generalize to other
media.
Summary
~~~
I propose splitting the code into the following parts: layer 2 (device
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 a
