| To: | dlstevens@xxxxxxxxxx |
|---|---|
| Subject: | Re: IPV6 RFC3542 compliance [PATCH] |
| From: | YOSHIFUJI Hideaki / 吉藤英明 <yoshfuji@xxxxxxxxxxxxxx> |
| Date: | Tue, 07 Jun 2005 16:55:36 +0900 (JST) |
| Cc: | davem@xxxxxxxxxxxxx, netdev@xxxxxxxxxxx, yoshfuji@xxxxxxxxxxxxxx |
| In-reply-to: | <20050607.164749.62298775.yoshfuji@linux-ipv6.org> |
| Organization: | USAGI Project |
| References: | <20050607.160521.73986501.yoshfuji@linux-ipv6.org> <OF2D6866A4.ACD65B11-ON88257019.0027E8B0-88257019.002A2862@us.ibm.com> <20050607.164749.62298775.yoshfuji@linux-ipv6.org> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
In article <20050607.164749.62298775.yoshfuji@xxxxxxxxxxxxxx> (at Tue, 07 Jun
2005 16:47:49 +0900 (JST)), YOSHIFUJI Hideaki / 吉藤英明
<yoshfuji@xxxxxxxxxxxxxx> says:
> No, kernel should send 5, if application use old API, of course.
This can be implemented like this (based on codes from our repository):
/* RFC2292bis */
if (np->rxopt.bits.rxhbh && opt->hop) {
u8 *ptr = skb->nh.raw + opt->hop;
put_cmsg(msg, SOL_IPV6, IPV6_HOPOPTS, (ptr[1]+1)<<3, ptr);
}
/* RFC2292 */
if (np->rxopt.bits.rxhbh2292 && opt->hop) {
u8 *ptr = skb->nh.raw + opt->hop;
put_cmsg(msg, SOL_IPV6, IPV6_2292HOPOPTS, (ptr[1]+1)<<3, ptr);
}
--yoshfuji
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: IPV6 RFC3542 compliance [PATCH], YOSHIFUJI Hideaki / 吉藤英明 |
|---|---|
| Next by Date: | Re: IPV6 RFC3542 compliance [PATCH], David Stevens |
| Previous by Thread: | Re: IPV6 RFC3542 compliance [PATCH], YOSHIFUJI Hideaki / 吉藤英明 |
| Next by Thread: | Re: IPV6 RFC3542 compliance [PATCH], David Stevens |
| Indexes: | [Date] [Thread] [Top] [All Lists] |