From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Andrea Mayer <andrea.mayer@uniroma2.it>,
David Ahern <dsahern@kernel.org>,
netdev@vger.kernel.org
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Stefano Salsano <stefano.salsano@uniroma2.it>,
Ahmed Abdelsalam <ahabdels@cisco.com>,
Paolo Lungaroni <paolo.lungaroni@uniroma2.it>,
Justin Iurman <justin.iurman@6wind.com>,
Anthony Doeraene <anthony.doeraene@uclouvain.be>
Subject: Re: [PATCH iproute2-next 1/2] seg6: add support for lookup attribute in SRv6 encap routes
Date: Thu, 16 Jul 2026 11:48:07 +0200 [thread overview]
Message-ID: <be16e8d1-acff-44a3-ac6f-86abe512aede@6wind.com> (raw)
In-Reply-To: <20260712021155.7621-2-andrea.mayer@uniroma2.it>
Le 12/07/2026 à 04:11, Andrea Mayer a écrit :
> Add support for the new optional "lookup" attribute for seg6 encap
> routes. It selects the FIB table for the post-encap SID route lookup
> and accepts a table number or a table name.
>
> Examples:
>
> # SID route installed in the underlay table 500
> ip -6 route add fc00::100/128 via fd00::1 dev veth0 table 500
>
> # encap route in vrf-100; the first SID is looked up in table 500
> ip -6 route add cafe::1/128 vrf vrf-100 \
> encap seg6 mode encap segs fc00::100 lookup 500 dev veth0
>
> # or if the SID is already handled by the main table
> ip -6 route add cafe::1/128 vrf vrf-100 \
> encap seg6 mode encap segs fc00::100 lookup main dev veth0
>
> When the attribute is omitted, the post-encap SID route lookup behaves
> as before, using the current routing context (e.g. the tables selected
> according to the routing policy database).
>
> Signed-off-by: Andrea Mayer <andrea.mayer@uniroma2.it>
Reviewed-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>
next prev parent reply other threads:[~2026-07-16 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-12 2:11 [PATCH iproute2-next 0/2] seg6: add support for lookup attribute in SRv6 encap routes Andrea Mayer
2026-07-12 2:11 ` [PATCH iproute2-next 1/2] " Andrea Mayer
2026-07-16 9:48 ` Nicolas Dichtel [this message]
2026-07-12 2:11 ` [PATCH iproute2-next 2/2] seg6: man: document the lookup attribute for " Andrea Mayer
2026-07-16 9:49 ` Nicolas Dichtel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=be16e8d1-acff-44a3-ac6f-86abe512aede@6wind.com \
--to=nicolas.dichtel@6wind.com \
--cc=ahabdels@cisco.com \
--cc=andrea.mayer@uniroma2.it \
--cc=anthony.doeraene@uclouvain.be \
--cc=dsahern@kernel.org \
--cc=justin.iurman@6wind.com \
--cc=netdev@vger.kernel.org \
--cc=paolo.lungaroni@uniroma2.it \
--cc=stefano.salsano@uniroma2.it \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox