Hwaddress ether xx:xx:xx:xx:xx:xx #fixed mac addressĪddress x.x.x. MACADDR=a0:36:9f:0f:b1:70 #Assigning fixed mac addressīONDING_OPTS="mode=active-backup primary=eno1 miimon=100" # cat /etc/sysconfig/network-scripts/ifcfg-bond0 # cat /etc/sysconfig/network-scripts/ifcfg-eno2 #Redhat/Centos # cat /etc/sysconfig/network-scripts/ifcfg-eno1 Bonding, also called port trunking or link aggregation means combining several network interfaces (NICs) to a.
Here is sample interface and bond file config, MACADDR may solve your issue. Descriptions of balancing algorithm modes. How do I prevent this MAC address generation and tell networkd to just use one from the slaves? Files The bonding driver intercepts the ARP Replies sent by the local system on their way out and overwrites the source hardware address with the unique hardware.
For other kind of netdevs, if this option is not set, then MAC address is generated based on the interface name and the machine-id(5). If this option is not set, "vlan" devices inherit the MAC address of the physical interface.
Please specify it in "" section of the corresponding work(5) file. For "tun" or "tap" devices, setting MACAddress= in the "" section is not supported. This breaks DHCP, and doesn't follow the expectation set by the Linux kernel bonding documentation that states that the bond interface will take the MAC address of one of its slaves.Īccording to the networkd documentation, the issue appears to be this: When I add the config files below into /etc/systemd/network and restart systemd-networkd, I find that the MAC addresses of bond0, eth0 and eth2 have all been changed to a single, locally administered address.
0 kommentar(er)
