From: Ido Schimmel <idosch@nvidia.com>
To: Jack Ma <jack4it@gmail.com>
Cc: David Ahern <dsahern@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, Shuah Khan <shuah@kernel.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net-next v4 3/3] selftests: net: add coverage for fdb nexthop dst_port
Date: Thu, 23 Jul 2026 10:49:16 +0300 [thread overview]
Message-ID: <20260723074916.GC3189375@shredder> (raw)
In-Reply-To: <20260723-b4-vxlan-fdb-port-v4-3-46e3a2dd88a3@gmail.com>
On Thu, Jul 23, 2026 at 01:17:55AM +0000, Jack Ma wrote:
> Add coverage for the new per-nexthop VXLAN destination port
> (NHA_DST_PORT).
>
> In fib_nexthops.sh, new ipv4_fdb_port_fcnal() and ipv6_fdb_port_fcnal()
> tests check that a dst_port is accepted on an fdb nexthop that has a
> gateway and echoed back on dump, that it is rejected without a gateway
> and rejected when zero, that a group may hold legs that differ only in
> UDP port, and that a portless fdb nexthop omits the attribute. The
> tests SKIP when iproute2 lacks the "dst_port" keyword.
>
> In test_vxlan_nh.sh, basic_tx_common() gains a second fdb nexthop group
> whose nexthop carries a destination port that differs from the VXLAN
> device default, plus a flower filter keyed on that port, to confirm the
> per-nexthop port is used on the wire. The test now requires an iproute2
> with dst_port support.
>
> Signed-off-by: Jack Ma <jack4it@gmail.com>
Reviewed-by: Ido Schimmel <idosch@nvidia.com>
next prev parent reply other threads:[~2026-07-23 7:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 1:17 [PATCH net-next v4 0/3] net: nexthop: per-nexthop UDP dst port for fdb (VXLAN) nexthops Jack Ma
2026-07-23 1:17 ` [PATCH net-next v4 1/3] net: nexthop: add NHA_DST_PORT for fdb nexthops Jack Ma
2026-07-23 7:48 ` Ido Schimmel
2026-07-23 14:40 ` David Ahern
2026-07-23 1:17 ` [PATCH net-next v4 2/3] vxlan: honor per-nexthop fdb destination port Jack Ma
2026-07-23 7:48 ` Ido Schimmel
2026-07-23 14:41 ` David Ahern
2026-07-23 1:17 ` [PATCH net-next v4 3/3] selftests: net: add coverage for fdb nexthop dst_port Jack Ma
2026-07-23 7:49 ` Ido Schimmel [this message]
2026-07-23 14:44 ` David Ahern
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=20260723074916.GC3189375@shredder \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jack4it@gmail.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=shuah@kernel.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