You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With ifcfg or NetworkManager it is possible to have generic config files for every system to configure a bridge on the one and only physical network interface. See the examples below how such configuration looks like.
With systemd-networkd it is apparently required to specify the MAC in the configuration. As a result, such configuration is per host and not generic anymore:
Here the physical link b8:ac:6f:a3:7d:0a should be part of bridge br0. Without [Link] MACAddress=b8:ac:6f:a3:7d:0a in br0.network the assigned MAC will be random. If there is just one single interface for the bridge, the MAC should be inherited. With more physical interfaces, like in the examples provided by systemd.network(5), the decision what MAC should be assigned to br0 is not straight forward.
With ifcfg or NetworkManager it is possible to have generic config files for every system to configure a bridge on the one and only physical network interface. See the examples below how such configuration looks like.
With systemd-networkd it is apparently required to specify the MAC in the configuration. As a result, such configuration is per host and not generic anymore:
Here the physical link
b8:ac:6f:a3:7d:0a
should be part of bridgebr0
. Without[Link] MACAddress=b8:ac:6f:a3:7d:0a
inbr0.network
the assigned MAC will be random. If there is just one single interface for the bridge, the MAC should be inherited. With more physical interfaces, like in the examples provided bysystemd.network(5)
, the decision what MAC should be assigned tobr0
is not straight forward.The text was updated successfully, but these errors were encountered: