Currently, the speaker pods keep announcing the same Mac address of the interface it initially gets. However, if the mac address changes for the specific interface, linux bridge, etc the requests to IP address announced by MetalLB start failing since speaker pods are still pointing to older mac address.

Example:

Many of the customers are creating a bond on top of 2 NICs and then a Linux Bridge on top of that bond with the help of NNCP. Now that Linux Bridge is used inside VMs created by OCP Virtualization. Every time a VM is created by specifying the Linux Bridge as an additional network, the "veth" for that VM gets associated to the Linux Bridge as one of its ports, and the mac address of the bridge changes to the latest VM veth mac address.

MetalLB speaker pod keeps on announcing the initial Mac address for the Linux bridge that it got initially while in reality the Linux Bridge mac address has been changed and hence requests to IP address announced by speaker pod over bridge starts failing.