Hi Cody,
>Hey Konstantin,
>Thanks for reviewing -- I see your point about this patch only removing one of
>the places where the code makes assumptions about the position of the
>fragmentation header.
>Unfortunately at the moment I don't have the resources to dedicate to writing
>the complete s
Hey Konstantin,
Thanks for reviewing -- I see your point about this patch only removing one
of the places where the code makes assumptions about the position of the
fragmentation header.
Unfortunately at the moment I don't have the resources to dedicate to
writing the complete solution and doing
Hi Cody,
>
> Add the ability to parse IPv6 extenders to find the
> IPv6 fragment header, and update callers.
>
> According to RFC 8200, there is no guarantee that the IPv6
> Fragment extension header will come before any other extension
> header, even though it is recommended.
>
> Signed-off-by
31/10/2018 03:17, Cody Doucette:
> Add the ability to parse IPv6 extenders to find the
> IPv6 fragment header, and update callers.
>
> According to RFC 8200, there is no guarantee that the IPv6
> Fragment extension header will come before any other extension
> header, even though it is recommended
Add the ability to parse IPv6 extenders to find the
IPv6 fragment header, and update callers.
According to RFC 8200, there is no guarantee that the IPv6
Fragment extension header will come before any other extension
header, even though it is recommended.
Signed-off-by: Cody Doucette
Signed-off-b
Add the ability to parse IPv6 extenders to find the
IPv6 fragment header, and update callers.
According to RFC 8200, there is no guarantee that the IPv6
Fragment extension header will come before any other extension
header, even though it is recommended.
Signed-off-by: Cody Doucette
Signed-off-b
6 matches
Mail list logo
