(usagi-users 03097) Re: kernel cannot process an IPv6 destination options header after the AH header.

[Kazunori Miyazawa <kazunori@xxxxxxxxxxxx>]

Hello,

We had implemented the process. However inner destination option
should not have mutable field because only the final destination node
processes the option. So that we can omit the process. 

I will ask TAHI guys about it.

Thank you.

On Monday 08 November 2004 09:31, Ueki Kohei wrote:
> Hello All.
>
> I found a problem in the current Usagi kernel(usagi-linux26-s20041025).
> The kernel cannot process an Destination Options Extention Header after
> the AH Header in an IPv6 packet.
>
> According to RFC2402 and draft-ietf-ipsec-rfc2402bis-08.txt,
> the destination options extension header(s) could appear before or after
> or both before and after the AH header depending on the
> semantics desired.
> But, the function ipv6_clear_mutable_options() cannot treat the
> destination options extension header after the AH header.
>
> I tried the TAHI test item ipsec#20.
> This test item uses a destination option header after AH, and the
> test is failed.
> This test item is passed when the undermentioned patch is applied.
>
>
snip
>
> Regard,
> Ueki Kohei