LAGG interfaces lose MAC address
LAGG interfaces lose their MAC address, normally inherited from the first member, if all links are disconnected and then reconnected. The switch they are connected to is powercycled for example.
Create a lagg interface with two memebers. Set it to LACP. Check the MAC of lagg0 it will be 00:00:00:00:00:00.
Reboot the firewall it will come back up with the correctly inherited MAC.
Pull the links to the two members NICs. The MAC will remain correct. Reconnect one or both members and the MAC will revert to 00:00:00:00:00:00
Additonally editing an existing lagg anf changing its type, for example, will result in a void MAC.
This does not happen in 2.3.4
#6 Updated by Denis Grilli over 1 year ago
You can also have the problem if you have vlans attached to the lagg interface:
1) create a new vlan
2) assign the new vlan to an interface.
After step 2) you lose the mac address.
I would consider to change priority to this case. It feels to me a quite of a big problem.
#12 Updated by Gianluca Toso over 1 year ago
I had similar issue with this mb APU1D/T40E, pfsense 2.4.0 fresh install:
all 3 reX interfaces were members in a LAG (LACP) which also contained several VLANs.
All interfaces showed mac address 00:00:00:00:00:00, this caused troubles with DHCP, PPPoE and so on...
Same config with 2.3.4 nanobsd works like a charme.
I didn't perform upgrade to 2.4.1 because I needed PPPoE over VLAN.
Therefore on a different 8 ports motherboard with emX nics the mac address problem doesn't occur (similar config with 6 over 8 port in a LACP LAG with server VLANs).
Will the 2.4.2 fix resolve mac address issue in this scenario as well?
Thanks in advance,