netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: "Marc Suñé" <marcdevel@gmail.com>,
	kuba@kernel.org, willemdebruijn.kernel@gmail.com,
	pabeni@redhat.com
Cc: netdev@vger.kernel.org, dborkman@kernel.org
Subject: Re: [PATCH RFC net 5/5] selftests/net: use scapy for no_bcastnull_poison
Date: Mon, 22 Dec 2025 09:34:43 +0000	[thread overview]
Message-ID: <cfb231cd-17bc-41aa-9533-f1a048eeb1be@linux.dev> (raw)
In-Reply-To: <3cfd28edb2c2b055e74b975623a3d38ade0237f1.1766349632.git.marcdevel@gmail.com>

On 21/12/2025 21:19, Marc Suñé wrote:
> Use Scapy to generate ARP/ND packets for ARP/ND no bcast/NULL MAC
> poisoning.

What's wrong with current implementation in arp_send.c and ndisc_send.c?

  reply	other threads:[~2025-12-22  9:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-21 21:19 [PATCH RFC net 0/5] net: discard ARP/NDP bcast/null announce (poison) Marc Suñé
2025-12-21 21:19 ` [PATCH RFC net 1/5] arp: discard sha bcast/null (bcast ARP poison) Marc Suñé
2025-12-22  9:47   ` Vadim Fedorenko
2025-12-22 21:37     ` Marc Sune
2025-12-22 22:08       ` Vadim Fedorenko
2025-12-21 21:19 ` [PATCH RFC net 2/5] selftests/net: add no ARP bcast/null poison test Marc Suñé
2025-12-21 21:19 ` [PATCH RFC net 3/5] neigh: discard lladdr bcast/null (bcast poison) Marc Suñé
2025-12-21 21:19 ` [PATCH RFC net 4/5] selftests/net: add no NDP bcast/null poison test Marc Suñé
2025-12-21 21:19 ` [PATCH RFC net 5/5] selftests/net: use scapy for no_bcastnull_poison Marc Suñé
2025-12-22  9:34   ` Vadim Fedorenko [this message]
2025-12-22 21:46     ` Marc Sune

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=cfb231cd-17bc-41aa-9533-f1a048eeb1be@linux.dev \
    --to=vadim.fedorenko@linux.dev \
    --cc=dborkman@kernel.org \
    --cc=kuba@kernel.org \
    --cc=marcdevel@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=willemdebruijn.kernel@gmail.com \
    /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;
as well as URLs for NNTP newsgroup(s).