diff options
| author |   Jakub Kicinski <kuba@kernel.org> | 2025-04-09 19:13:46 -0700 |
|---|---|---|
| committer | Jakub Kicinski <kuba@kernel.org> | 2025-04-09 19:13:46 -0700 |
| commit | 330689f757a7b31794b9887788da679be2d03248 (patch) | |
| tree | a0f4c231521833a366aeb012c1553fa7ea1991d6 /net/lapb/lapb_timer.c | |
| parent | net: remove cpu stall in txq_trans_update() (diff) | |
| parent | selftests: test_bridge_neigh_suppress: Test unicast ARP/NS with suppression (diff) | |
| download | wireguard-linux-330689f757a7b31794b9887788da679be2d03248.tar.xz wireguard-linux-330689f757a7b31794b9887788da679be2d03248.zip | |
Merge branch 'bridge-prevent-unicast-arp-ns-packets-from-being-suppressed-by-bridge'
Amit Cohen says:
====================
bridge: Prevent unicast ARP/NS packets from being suppressed by bridge
Currently, unicast ARP requests/NS packets are replied by bridge when
suppression is enabled, then they are also forwarded, which results two
replicas of ARP reply/NA - one from the bridge and second from the target.
The purpose of ARP/ND suppression is to reduce flooding in the broadcast
domain, which is not relevant for unicast packets. In addition, the use
case of unicast ARP/NS is to poll a specific host, so it does not make
sense to have the switch answer on behalf of the host.
Forward ARP requests/NS packets and prevent the bridge from replying to
them.
Patch set overview:
Patch #1 prevents unicast ARP/NS packets from being suppressed by bridge
Patch #2 adds test cases for unicast ARP/NS with suppression enabled
====================
Link: https://patch.msgid.link/cover.1744123493.git.petrm@nvidia.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'net/lapb/lapb_timer.c')
0 files changed, 0 insertions, 0 deletions