Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Layer 2: MetalLB shouldn't listen on interfaces which have master #349
Is this a bug report or a feature request?:
My nodes have a lot of interfaces, eg. 4 hardware interfaces, 2 bonding, bridge, vlans, and veth interfaces.
When I use arping, I have 8 replies from the metallb speaker. From each interface which passing the traffic.
Eg if you have the next scheme:
I will get answer from all of them. That's totally wrong because connectivity will not work if ip address will be associated with interface which have master (
What you expected to happen:
I expected answer only from
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Thanks for the report! This is definitely a bug, in exactly the way you describe.
Unfortunately, getting information about which interfaces are sub-interfaces of others is hard from Go right now, so it's not a 100% trivial fix. There's also a related bug #316 which would allow selecting specific interfaces to listen on, although I still want the default to be automagic.