netdev - Re: [PATCH iproute2-next v2 0/2] Support for IOAM encap modes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <d920c307-a04f-4fc1-0d57-cf6c2a60ecfb@gmail.com>
Date:   Sat, 9 Oct 2021 17:39:20 -0600
From:   David Ahern <dsahern@...il.com>
To:     Justin Iurman <justin.iurman@...ege.be>, netdev@...r.kernel.org
Cc:     davem@...emloft.net, dsahern@...nel.org, stephen@...workplumber.org
Subject: Re: [PATCH iproute2-next v2 0/2] Support for IOAM encap modes

On 10/5/21 9:10 AM, Justin Iurman wrote:
> v2:
>  - Fix the size of ioam6_mode_types (thanks David Ahern)
>  - Remove uapi diff from patch #1 (already merged inside iproute2-next)
> 
> Following the series applied to net-next (see [1]), here are the corresponding
> changes to iproute2.
> 
> In the current implementation, IOAM can only be inserted directly (i.e., only
> inside packets generated locally) by default, to be compliant with RFC8200.
> 
> This patch adds support for in-transit packets and provides the ip6ip6
> encapsulation of IOAM (RFC8200 compliant). Therefore, three ioam6 encap modes
> are defined:
> 
>  - inline: directly inserts IOAM inside packets (by default).
> 
>  - encap:  ip6ip6 encapsulation of IOAM inside packets.
> 
>  - auto:   either inline mode for packets generated locally or encap mode for
>            in-transit packets.
> 
> With current iproute2 implementation, it is configured this way:
> 
> $ ip -6 r [...] encap ioam6 trace prealloc [...]
> 
> The old syntax does not change (for backwards compatibility) and implicitly uses
> the inline mode. With the new syntax, an encap mode can be specified:
> 
> (inline mode)
> $ ip -6 r [...] encap ioam6 mode inline trace prealloc [...]
> 
> (encap mode)
> $ ip -6 r [...] encap ioam6 mode encap tundst fc00::2 trace prealloc [...]
> 
> (auto mode)
> $ ip -6 r [...] encap ioam6 mode auto tundst fc00::2 trace prealloc [...]
> 
> A tunnel destination address must be configured when using the encap mode or the
> auto mode.
> 
>   [1] https://lore.kernel.org/netdev/163335001045.30570.12527451523558030753.git-patchwork-notify@kernel.org/T/#m3b428d4142ee3a414ec803466c211dfdec6e0c09
> 

applied to iproute2-next. Thanks,