netdev - Re: [PATCH net-next] net: bridge: when suppression is enabled exclude RARP packets

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <161644621029.7104.8989663274952971379.git-patchwork-notify@kernel.org>
Date:   Mon, 22 Mar 2021 20:50:10 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Nikolay Aleksandrov <razor@...ckwall.org>
Cc:     netdev@...r.kernel.org, roopa@...dia.com,
        bridge@...ts.linux-foundation.org, nikolay@...dia.com,
        amer@...dia.com
Subject: Re: [PATCH net-next] net: bridge: when suppression is enabled exclude
 RARP packets

Hello:

This patch was applied to netdev/net-next.git (refs/heads/master):

On Mon, 22 Mar 2021 17:45:27 +0200 you wrote:
> From: Nikolay Aleksandrov <nikolay@...dia.com>
> 
> Recently we had an interop issue where RARP packets got suppressed with
> bridge neigh suppression enabled, but the check in the code was meant to
> suppress GARP. Exclude RARP packets from it which would allow some VMWare
> setups to work, to quote the report:
> "Those RARP packets usually get generated by vMware to notify physical
> switches when vMotion occurs. vMware may use random sip/tip or just use
> sip=tip=0. So the RARP packet sometimes get properly flooded by the vtep
> and other times get dropped by the logic"
> 
> [...]

Here is the summary with links:
  - [net-next] net: bridge: when suppression is enabled exclude RARP packets
    https://git.kernel.org/netdev/net-next/c/0353b4a96b7a

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html