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
| ||
|
Message-ID: <4c04b1a9-d8e7-169e-d337-c061f6e600c2@6wind.com> Date: Mon, 3 Oct 2022 11:37:18 +0200 From: Nicolas Dichtel <nicolas.dichtel@...nd.com> To: Eyal Birger <eyal.birger@...il.com>, netdev@...r.kernel.org Cc: dsahern@...il.com, stephen@...workplumber.org, steffen.klassert@...unet.com, razor@...ckwall.org Subject: Re: [PATCH iproute2-next 2/2] ip: xfrm: support adding xfrm metadata as lwtunnel info in routes Le 03/10/2022 à 11:12, Eyal Birger a écrit : > Support for xfrm metadata as lwtunnel metadata was added in kernel commit > 2c2493b9da91 ("xfrm: lwtunnel: add lwtunnel support for xfrm interfaces in collect_md mode") > > This commit adds the respective support in lwt routes. > > Example use (consider ipsec1 as an xfrm interface in "external" mode): > > ip route add 10.1.0.0/24 dev ipsec1 encap xfrm if_id 1 > > Or in the context of vrf, one can also specify the "link" property: > > ip route add 10.1.0.0/24 dev ipsec1 encap xfrm if_id 1 link_dev eth15 > > Signed-off-by: Eyal Birger <eyal.birger@...il.com> Reviewed-by: Nicolas Dichtel <nicolas.dichtel@...nd.com>
Powered by blists - more mailing lists