netdev
[Top] [All Lists]

Re: IPV6_HOPOPTS

To: insel@xxxxxxxxxxxxxxx
Subject: Re: IPV6_HOPOPTS
From: YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx>
Date: Mon, 12 Nov 2001 20:18:37 +0900
Cc: netdev@xxxxxxxxxxx
In-reply-to: <3BEF94F2.FBF6080B@xxxxxxxxxxxxxxx>
References: <3BEF7BD3.C6DAB8F8@xxxxxxxxxxxxxxx> <20011112173936T.yoshfuji@xxxxxxxxxx> <3BEF94F2.FBF6080B@xxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
In article <3BEF94F2.FBF6080B@xxxxxxxxxxxxxxx> (at Mon, 12 Nov 2001 10:22:58 
+0100), root <insel@xxxxxxxxxxxxxxx> says:

> > > RFC2292 provides a way of accessing these options and to add new ones to
> > > the ipv6-kernel-stack so there should be a way to get them out of the
> > > kernel-space with somekind of advanced API, maybe I'am wrong???
> > 
> > IPV6_HOPOPTS is only for source / destination nodes.
> > We cannot use it at intermediate nodes.
> We cannot use, not even intercept them at intermediate nodes?
> 
> But why and whats the difference to IPV6_DSTOPTS then??

Userland code (/ kernel) of source node can generate hbh / dst option(s).
(userland code uses advanced API for this.)

Kernels of intermediate and destination nodes handle hbh option(s), but 
userland code of intermediate destination nodes can NOT receive dst / 
hbh option(s) via the advanced API such as IPV6_{HOP,DEST}OPTS.

Kernels of final destination node handles dst option(s), and also
userland code of final destination node can receive dst / hbh option(s)
via the advanced API.

Note: Kernel of two or more nodes may act as destination if you 
      use routing header.

--yoshfuji

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