| To: | insel@xxxxxxxxxxxxxxx |
|---|---|
| Subject: | Re: IPV6_HOPOPTS |
| From: | YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxx> |
| Date: | Mon, 12 Nov 2001 17:39:36 +0900 |
| Cc: | kuznet@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <3BEF7BD3.C6DAB8F8@xxxxxxxxxxxxxxx> |
| References: | <200111100536.IAA00423@xxxxxxxxxxxxxx> <3BEF7BD3.C6DAB8F8@xxxxxxxxxxxxxxx> |
| Sender: | owner-netdev@xxxxxxxxxxx |
In article <3BEF7BD3.C6DAB8F8@xxxxxxxxxxxxxxx> (at Mon, 12 Nov 2001 08:35:47 +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. --yoshfuji |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: IPV6_HOPOPTS, root |
|---|---|
| Next by Date: | Re: IPV6_HOPOPTS, root |
| Previous by Thread: | Re: IPV6_HOPOPTS, root |
| Next by Thread: | Re: IPV6_HOPOPTS, root |
| Indexes: | [Date] [Thread] [Top] [All Lists] |