From: Simon Horman <horms@kernel.org>
To: Oscar Maes <oscmaes92@gmail.com>
Cc: netdev@vger.kernel.org, bacs@librecast.net, brett@librecast.net,
kuba@kernel.org, pabeni@redhat.com, davem@davemloft.net,
dsahern@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH net v4] selftests: net: add test for destination in broadcast packets
Date: Fri, 29 Aug 2025 12:19:21 +0100 [thread overview]
Message-ID: <20250829111921.GI31759@horms.kernel.org> (raw)
In-Reply-To: <20250828114242.6433-1-oscmaes92@gmail.com>
On Thu, Aug 28, 2025 at 01:42:42PM +0200, Oscar Maes wrote:
> Add test to check the broadcast ethernet destination field is set
> correctly.
>
> This test sends a broadcast ping, captures it using tcpdump and
> ensures that all bits of the 6 octet ethernet destination address
> are correctly set by examining the output capture file.
>
> Signed-off-by: Oscar Maes <oscmaes92@gmail.com>
> Co-authored-by: Brett A C Sheffield <bacs@librecast.net>
...
> +test_broadcast_ether_dst() {
> + local rc=0
> + CAPFILE=$(mktemp -u cap.XXXXXXXXXX)
> + OUTPUT=$(mktemp -u out.XXXXXXXXXX)
> +
> + echo "Testing ethernet broadcast destination"
> +
> + # start tcpdump listening for icmp
> + # tcpdump will exit after receiving a single packet
> + # timeout will kill tcpdump if it is still running after 2s
> + timeout 2s ip netns exec "${CLIENT_NS}" \
> + tcpdump -i link0 -c 1 -w "${CAPFILE}" icmp &> "${OUTPUT}" &
> + pid=$!
> + slowwait 1 grep -qs "listening" "${OUTPUT}"
> +
> + # send broadcast ping
> + ip netns exec "${CLIENT_NS}" \
> + ping -W0.01 -c1 -b 255.255.255.255 &> /dev/null
> +
> + # wait for tcpdump for exit after receiving packet
> + wait "${pid}"
Hi Oscar and Brett,
I am concerned that if something goes wrong this may block forever.
Also, I'm wondering if this test could make use of the tcpdump helpers
provided in tools/testing/selftests/net/forwarding/lib.sh
> +
> + # compare ethernet destination field to ff:ff:ff:ff:ff:ff
> + ether_dst=$(tcpdump -r "${CAPFILE}" -tnne 2>/dev/null | \
> + awk '{sub(/,/,"",$3); print $3}')
> + if [[ "${ether_dst}" == "ff:ff:ff:ff:ff:ff" ]]; then
> + echo "[ OK ]"
> + rc="${ksft_pass}"
> + else
> + echo "[FAIL] expected dst ether addr to be ff:ff:ff:ff:ff:ff," \
> + "got ${ether_dst}"
> + rc="${ksft_fail}"
> + fi
> +
> + return "${rc}"
> +}
...
next prev parent reply other threads:[~2025-08-29 11:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 11:42 [PATCH net v4] selftests: net: add test for destination in broadcast packets Oscar Maes
2025-08-28 11:44 ` kernel test robot
2025-08-28 12:16 ` Brett A C Sheffield
2025-08-29 11:19 ` Simon Horman [this message]
2025-08-29 11:44 ` Brett Sheffield
2025-08-29 13:11 ` Brett Sheffield
2025-09-01 12:25 ` Oscar Maes
2025-09-02 8:49 ` Paolo Abeni
2025-09-02 9:33 ` Brett Sheffield
2025-09-02 9:57 ` Paolo Abeni
2025-09-02 10:25 ` Brett Sheffield
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=20250829111921.GI31759@horms.kernel.org \
--to=horms@kernel.org \
--cc=bacs@librecast.net \
--cc=brett@librecast.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oscmaes92@gmail.com \
--cc=pabeni@redhat.com \
--cc=stable@vger.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 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.