From: Justin Iurman <justin.iurman@6wind.com>
To: netdev@vger.kernel.org
Cc: andrea.mayer@uniroma2.it, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, justin.iurman@gmail.com,
nicolas.dichtel@6wind.com, stefano.salsano@uniroma2.it,
Justin Iurman <justin.iurman@6wind.com>
Subject: [PATCH net-next v5 0/2] Add support for per-route seg6 tunsrc
Date: Tue, 24 Mar 2026 10:14:32 +0100 [thread overview]
Message-ID: <20260324091434.359341-1-justin.iurman@6wind.com> (raw)
This series adds support for the new per-route seg6 "tunsrc" parameter.
Selftests are extended to make sure it works as expected.
Example with the iproute2-next companion patch:
ip -6 r a 2001:db8:1::/64 encap seg6 mode encap tunsrc 2001:db8:ab::
segs 2001:db8:42::1,2001:db8:ffff::2 dev eth0
Justin Iurman (2):
seg6: add per-route tunnel source address
selftests: add check for seg6 tunsrc
include/uapi/linux/seg6_iptunnel.h | 1 +
net/ipv6/seg6_iptunnel.c | 114 +++++++++++++-----
.../net/srv6_hencap_red_l3vpn_test.sh | 109 +++++++++++++++--
3 files changed, 180 insertions(+), 44 deletions(-)
---
v5: tunsrc support detection for non-backward compatible kernels, fix two nits
v4:
https://lore.kernel.org/netdev/20260320135909.1729313-1-justin.iurman@6wind.com/
v3:
https://lore.kernel.org/netdev/20260316162955.1253225-1-justin.iurman@6wind.com/
v2:
https://lore.kernel.org/netdev/20260311152845.278354-1-justin.iurman@6wind.com/
v1:
https://lore.kernel.org/netdev/20260310141057.3353333-1-justin.iurman@6wind.com/
--
2.39.2
next reply other threads:[~2026-03-24 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-24 9:14 Justin Iurman [this message]
2026-03-24 9:14 ` [PATCH net-next v5 1/2] seg6: add per-route tunnel source address Justin Iurman
2026-03-24 9:14 ` [PATCH net-next v5 2/2] selftests: add check for seg6 tunsrc Justin Iurman
2026-03-25 1:55 ` Andrea Mayer
2026-03-27 1:50 ` [PATCH net-next v5 0/2] Add support for per-route " patchwork-bot+netdevbpf
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=20260324091434.359341-1-justin.iurman@6wind.com \
--to=justin.iurman@6wind.com \
--cc=andrea.mayer@uniroma2.it \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=justin.iurman@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--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