diff options
author | 2025-02-25 03:39:14 +0000 | |
---|---|---|
committer | 2025-02-26 19:27:17 -0800 | |
commit | 28d68d396a1cd21591e8c6d74afbde33a7ea107e (patch) | |
tree | 5975a27e71830936ea858152550d70d4b79deb4d /include/linux/cpu_rmap.h | |
parent | net: skb: free up one bit in tx_flags (diff) | |
download | wireguard-linux-28d68d396a1cd21591e8c6d74afbde33a7ea107e.tar.xz wireguard-linux-28d68d396a1cd21591e8c6d74afbde33a7ea107e.zip |
bonding: report duplicate MAC address in all situations
Normally, a bond uses the MAC address of the first added slave as the bond’s
MAC address. And the bond will set active slave’s MAC address to bond’s
address if fail_over_mac is set to none (0) or follow (2).
When the first slave is removed, the bond will still use the removed slave’s
MAC address, which can lead to a duplicate MAC address and potentially cause
issues with the switch. To avoid confusion, let's warn the user in all
situations, including when fail_over_mac is set to 2 or not in active-backup
mode.
Signed-off-by: Hangbin Liu <liuhangbin@gmail.com>
Reviewed-by: Nikolay Aleksandrov <razor@blackwall.org>
Link: https://patch.msgid.link/20250225033914.18617-1-liuhangbin@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/linux/cpu_rmap.h')
0 files changed, 0 insertions, 0 deletions