From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, razor@blackwall.org,
mirsad.todorovac@alu.unizg.hr
Subject: Re: [PATCH net] selftests: vxlan_mdb: Fix failures with old libnet
Date: Tue, 26 Mar 2024 11:40:30 +0000 [thread overview]
Message-ID: <171145323041.5270.10718978656923412689.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240325075030.2379513-1-idosch@nvidia.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 25 Mar 2024 09:50:30 +0200 you wrote:
> Locally generated IP multicast packets (such as the ones used in the
> test) do not perform routing and simply egress the bound device.
>
> However, as explained in commit 8bcfb4ae4d97 ("selftests: forwarding:
> Fix failing tests with old libnet"), old versions of libnet (used by
> mausezahn) do not use the "SO_BINDTODEVICE" socket option. Specifically,
> the library started using the option for IPv6 sockets in version 1.1.6
> and for IPv4 sockets in version 1.2. This explains why on Ubuntu - which
> uses version 1.1.6 - the IPv4 overlay tests are failing whereas the IPv6
> ones are passing.
>
> [...]
Here is the summary with links:
- [net] selftests: vxlan_mdb: Fix failures with old libnet
https://git.kernel.org/netdev/net/c/f1425529c33d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-03-26 11:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 7:50 [PATCH net] selftests: vxlan_mdb: Fix failures with old libnet Ido Schimmel
2024-03-26 11:40 ` patchwork-bot+netdevbpf [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=171145323041.5270.10718978656923412689.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mirsad.todorovac@alu.unizg.hr \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=razor@blackwall.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.