Netdev List
 help / color / mirror / Atom feed
From: Nicolas Dichtel <nicolas.dichtel@6wind.com>
To: Andrea Mayer <andrea.mayer@uniroma2.it>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: David Ahern <dsahern@kernel.org>, Simon Horman <horms@kernel.org>,
	Shuah Khan <shuah@kernel.org>,
	Justin Iurman <justin.iurman@6wind.com>,
	Anthony Doeraene <anthony.doeraene@uclouvain.be>,
	Stefano Salsano <stefano.salsano@uniroma2.it>,
	Ahmed Abdelsalam <ahabdels@cisco.com>,
	Paolo Lungaroni <paolo.lungaroni@uniroma2.it>,
	netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] selftests: seg6: add test for post-encap SID route lookup
Date: Thu, 16 Jul 2026 11:46:15 +0200	[thread overview]
Message-ID: <b517ef0e-d499-47e2-aac6-1950c5946e55@6wind.com> (raw)
In-Reply-To: <20260711162907.6521-3-andrea.mayer@uniroma2.it>



Le 11/07/2026 à 18:29, Andrea Mayer a écrit :
> Add a selftest for the SEG6_IPTUNNEL_TABLE attribute, which selects the FIB
> table for the post-encap SID route lookup. This looks up the route for the
> first SID, the outer destination of the encapsulated packet.
> 
> Two routers provide L3 VPN services over an IPv6 underlay. Each router uses
> a separate VRF per tenant, with default blackhole routes (IPv4 and IPv6)
> that drop unmatched traffic. Tenant traffic is encapsulated, then
> decapsulated with an End.DT46.
> The encap routes are installed in the tenant VRF, but the routes that match
> the first SIDs live in a separate underlay table (500). The "lookup 500"
> attribute points the lookup there rather than to the VRF.
> 
> The test covers both the input path, where forwarded host traffic triggers
> encapsulation, and the output path, where a router originates traffic from
> its own loopback inside a VRF.
> With the "lookup" attribute, traffic reaches its destination on both paths.
> Without it, on the input path the lookup stays in the VRF and hits the
> blackhole, and on the output path it falls through to the main table, which
> has no matching route.
> 
> Signed-off-by: Andrea Mayer <andrea.mayer@uniroma2.it>

Reviewed-by: Nicolas Dichtel <nicolas.dichtel@6wind.com>

      reply	other threads:[~2026-07-16  9:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-11 16:29 [PATCH net-next 0/2] seg6: add FIB table attribute for post-encap SID route lookup Andrea Mayer
2026-07-11 16:29 ` [PATCH net-next 1/2] " Andrea Mayer
2026-07-11 17:04   ` David Ahern
2026-07-11 16:29 ` [PATCH net-next 2/2] selftests: seg6: add test " Andrea Mayer
2026-07-16  9:46   ` Nicolas Dichtel [this message]

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=b517ef0e-d499-47e2-aac6-1950c5946e55@6wind.com \
    --to=nicolas.dichtel@6wind.com \
    --cc=ahabdels@cisco.com \
    --cc=andrea.mayer@uniroma2.it \
    --cc=anthony.doeraene@uclouvain.be \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=justin.iurman@6wind.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paolo.lungaroni@uniroma2.it \
    --cc=shuah@kernel.org \
    --cc=stefano.salsano@uniroma2.it \
    /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