I have a ALMA9 Linux server with a quad BCM57414 NetXtreme-E 10Gb/25Gb RDMA Ethernet Controller NIC. I have two interfaces teamed using LACP and connected to a Cisco 9336C-FX2 switch running (NX-OS) Software 7.0(3)I7(6). The two interfaces are connected at 25Gbps speed each. Can I aggregate them so that the total throughput is 50Gbps? Here is what my network guys sent me regarding the interfaces and port channel: SWITCH-ACCESS02-9336C# show int status | i ppg Eth1/14/1 ... Sto connected trunk full 25G QSFP100G-4SFP25G-CU3M Eth1/14/2 ... Sto connected trunk full 25G QSFP100G-4SFP25G-CU3M Po160 ... Sto connected trunk full 25G -- He says, "It turns out that the server is sending LACP packets to the switch telling it that it can only load balance using MAC address and Layer 4 destination port. Those two modes do NOT support bundling the throughput." How then do I bundle the throughput? Is that possible on the Linux side? My bond state looks like this: [root@linux-host ~]# teamdctl bond1 state setup: runner: lacp ports: bcom1 link watches: link summary: up instance[link_watch_0]: name: ethtool link: up down count: 1 runner: aggregator ID: 5, Selected selected: yes state: current bcom2 link watches: link summary: up instance[link_watch_0]: name: ethtool link: up down count: 1 runner: aggregator ID: 5, Selected selected: yes state: current runner: active: yes fast rate: yes Thanks.

I'm using Open vSwitch (OVS) with a bonded interface configured for LACP and balance-tcp mode. After running ovs-appctl bond/show, I see output like this:

bond-m-2274c5f6 --- 
bond mode: balance-tcp
bond may use recirculation: yes, Recirc-ID :3
bond-hash-basis:0
updelay:0 ms
downdelay:0 ms
next rebalance:9367 ms
lacp_status: negotiated
lacp fallback ab: true
active slave mac: 34:73:79:f7:77:12(ens1f1np1)

slave ens1f1np1: enabled
  active slave
  may_enable: true

slave ens4f1np1: enabled
  may_enable: true

My questions are: 1. What exactly does the active slave field mean in the context of balance-tcp mode? 2. In LACP, is there a concept of an "active" slave interface, or are all aggregated links treated equally? 3. Are there any actual differences between the two slave interfaces (e.g., ens1f1np1 vs ens4f1np1) in this setup? From my understanding, balance-tcp should distribute traffic based on a hash (TCP/IP/MAC), and both interfaces should be actively used. I just want to make sure I'm interpreting the ovs-appctl bond/show output correctly. Any insights or clarifications would be appreciated!

OS: CentOS 6.6 / 64bit / Kernel 2.6.32-504.30.3.el6.x86_64 I have bond0 interface with following configuration. Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer2 (0) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 802.3ad info LACP rate: slow Aggregator selection policy (ad_select): stable Active Aggregator Info: Aggregator ID: 7 Number of ports: 2 Actor Key: 17 Partner Key: 3 Partner Mac Address: a4:56:30:c6:0d:00 Slave Interface: eth0 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 2 Permanent HW addr: 9c:8e:99:0d:1a:f2 Aggregator ID: 7 Slave queue ID: 0 Slave Interface: eth1 MII Status: up Speed: 1000 Mbps Duplex: full Link Failure Count: 2 Permanent HW addr: 9c:8e:99:0d:1a:f4 Aggregator ID: 7 Slave queue ID: 0 modprobe.conf alias bond0 bonding options bond0 mode=4 miimon=100 Cisco switch config: interface Port-channel1 description Linux-bond0 switchport access vlan 10 interface GigabitEthernet0/7 switchport access vlan 10 spanning-tree portfast spanning-tree guard root channel-protocol lacp channel-group 1 mode active ! interface GigabitEthernet0/8 switchport access vlan 10 spanning-tree portfast spanning-tree guard root channel-protocol lacp channel-group 1 mode active ! # Issue I am getting RX packet drop on bond0 and eth0 interface on Linux ( but not on eth1) bond0 : RX packets:575214161 errors:0 dropped:6407 overruns:0 frame:0 eth0 : RX packets:573623915 errors:0 dropped:6410 overruns:0 frame:0 eth1 : RX packets:1590356 errors:0 dropped:0 overruns:0 frame:0 I have check MRTG to see traffic flow and its around ~30mbps But interesting thing. I am seeing all 30mbps traffic on eth0, eth1 has few kbps traffic. That means my link is not doing load balancing right? cacti reporting following data. LACP should share traffic on both link right? eth0: 30mbps eth1: 600kbps

Is the mode 6 traffic will receive load balance relatively according to the slaves interfaces? OS: ubuntu 18.04.6 LTS; bonding driver: v3.7.1; kernel: 4.15.0-213-generic In mode 6, I had setted the parameter bond_arp_interval 100, arp_validate 3 and bond_arp_ip_target ip1,ip2 and restart interface, then only get *ip1* from file */sys/class/net/bond6/bonding/arp_ip_target*, but get *0* from both file */sys/class/net/bond6/bonding/arp_interval* and */sys/class/net/bond6/bonding/arp_validate*, and pushed the traffic to the dest host by iperf3, all traffic from different src hosts with different arp records(same dest ip with different mac addresses which belong to the dest host mode 6 bonding slaves) always received by the same slave interface in dest host. Maybe the ARP record does not update properly in the subnet, so it can't receive traffic load balancing. And I tested bond_arp_interval 100, arp_validate 3 and bond_arp_ip_target ip1 in mode 1, it works, reference to this redhat solution . Maybe arp probes not suitable for mode 6? Why mode 6 say it could achieve that receive traffic balancing? How the bonding driver initiates an ARP reply to the peer for updating the ARP record? I can't find any other parameter to work for it. Linux Ethernet Bonding Driver HOWTO : > Receive load balancing is handled by Address Resolution Protocol (ARP) negotiation and table mapping to the relevant group interface. > Hence, peers learn the hardware address of the bond and the balancing of receive traffic collapses to the current slave. This is handled by sending updates (ARP Replies) to all the peers with their individually assigned hardware address such that the traffic is redistributed. Questions: 1, how bonding achieve that the mode 6 **receive traffic load balancing** to the slaves? 2, why it doesn't work with **arp monitor** in mode 6? 3, could it work in **Distributed VXLAN Gateway ** with dynamically learns ARP entries and ARP broadcast suppression? 4, when two Distributed VXLAN Gateway(Q3) leaves learned the **same host IP ARP entry but with different mac addresses** from local network(switch port), what would they do?

I made an attempt bonding two interfaces into one, created bond0, and found it unsatisfactory. I then reverted all changes made to /etc/network/interfaces and ran systemctl restart networking.service, but the bond interface still existed (shows up in ifconfig and ip link commands) and I had to run ip link set bond0 down or ifconfig bond0 down to force kick it out. How do I completely remove this interface without rebooting the server? I'm on Debian Buster. The file was originally like this:

auto eno1
iface eno1 inet static
    # regular network settings like address, netmask, gateway etc.
auto eno2
iface eno2 inet static
    # regular network settings like address, netmask, gateway etc.

I turned both interfaces into one bond by changing it into this:

auto eno1
iface eno1 inet manual
    bond-master bond0
auto eno2
iface eno2 inet manual
    bond-master bond0

auto bond0
iface bond0 inet static
    # regular network settings like address, netmask, gateway etc.

**Pre-amble**: I am wanting to turn n + 1 connections into a single connection where the failover latency is 0 by *duplicating* traffic over multiple connections and dropping out packets on reception. **Investigation**: I have investigated mlvpn which I've discovered simply doesn't do this, besides, I don't want to use non-stock linux components if I can avoid it. bonding seems to fit the bill, specifically with mode = broadcast which flat out duplicates traffic on all the links. I have combined this with openvpn tap tunnels which are bonded on either end like so: ----- tap 0 ----- / \ (home-router) bond0 bond0 (vps server) \----- tap 1 ------/ There's a bunch of hoops to jump through here, and it's not perfect, but I am able to get this setup working: 1. I can tcpdump on tap0, tap1 and bond0 and see exactly what I expect to: traffic is duplicated over tap0 and tap1. 2. I can stop the openvpn process on the server and observe no activity on one of the two taps while seeing a 0 latency failover of ping on bond0 What I cannot do is deduplicate the traffic. I have looked at nftables, ebtables, and iptables (in descending order of preference). I have also investigated eBPF. Surely what I'm trying to achieve has been done before, I can't be the first to invent this wheel. Any ideas?

I want to bond the network interfaces of two USB-tethered android phones connected to a Raspberry Pi 4. So when one person leaves and takes his phone, it "fail-overs" to the second phone without a short interruption you would normally have without bonding. The problem is that the bonding network interface disappears when I remove and replug the last phone (and activate USB tethering again). This is how I set up the bonding interface. I use systemd-networkd: /etc/systemd/network/bond1.netdev

[NetDev]
Name=bond1
Description=Bonds usb network interfaces
Kind=bond

[Bond]
Mode=active-backup
MIIMonitorSec=100

/etc/systemd/network/bond1.network

[Match]
Name=usb*

[Network]
Bond=bond1

/etc/systemd/network/bond1-net.network

[Match]
Name=bond1

[Network]
DHCP=yes

This configuration seems to work as long as at least one usb network interface is there and is not removed/replugged. As soon as I un- and replug (i.e. not upon removal) the last phone and activate USB-tethering the usb0 network interface appears again and bond1 immediatly disappears and I have to restart systemd-networkd to let it reappear again. After removing all bonded usb network interface ip link still lists bond1:

5: bond1:  mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
    link/ether 4e:db:45:d2:25:c0 brd ff:ff:ff:ff:ff:ff

After replugging and enabling usb tethering bond1 is gone and dmesg says:

[ 1345.285781] bond1: (slave usb0): making interface the new active one
[ 1345.286004] bond1: (slave usb0): Enslaving as an active interface with an up link
[ 1346.647947] bond1: (slave usb0): Releasing backup interface
[ 1346.682264] bond1 (unregistering): Released all slaves

So at first it re-adds the usb interface again but then releases all interfaces and unregisters bond1. Then I tried to find a solution and found the following hints: Add these lines to /etc/systemd/network/bond1.netdev

[NetDev]
Name=bond1
Kind=bond
Removable=no # Added

[Bond]
Mode=active-backup
MiimonSec=100
PrimaryReselectPolicy=better # Added
IgnoreCarrierLoss=1 # Added

And add udev rules to manually re-add the usb interfaces:

SUBSYSTEM=="net", ACTION=="add", KERNEL=="usb0", RUN+="/usr/bin/ip link set usb0 master bond1"
SUBSYSTEM=="net", ACTION=="add", KERNEL=="usb1", RUN+="/usr/bin/ip link set usb1 master bond1"

But that does not help or change the behavior in any way. Does anyone know what might help to fix this problem?

After adding a new "interface" to the /etc/sysconfig/ifcfg-foobar: BOOTPROTO='static' BROADCAST='' ETHTOOL_OPTIONS='' IPADDR='1.2.3.4/24' MTU='9000' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='no' VLAN_ID='50' ETHERDEVICE='bond0' What is the proper method to bring this new interface up? /etc/init.d/networking restart just killed my SSH session and I had to reboot the server. Came in via another interface that was using bond0. Or was the problem that I wasn't running the /etc/init.d/networking restart command in a screen/tmux session on the server? Using SLES 11.4

I'm setting up an interface alias with my bond0 network. Why am I not able to ping/reach the second IP address, in this case 192.168.30.84? * However I can ping the address from another server:

-shellsession
    ~# ifconfig bond0
    bond0     Link encap:Ethernet  HWaddr 90:b1:1c:1e:eb:68  
              inet addr:192.168.30.82  Bcast:192.168.255.255  Mask:255.255.0.0
              inet6 addr: fe80::92b1:1cff:fe1e:eb68/64 Scope:Link
              UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
              RX packets:6924946 errors:0 dropped:2670931 overruns:0 frame:0
              TX packets:82824 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0 
              RX bytes:921251441 (878.5 MiB)  TX bytes:6424239 (6.1 MiB)

    bond0:0   Link encap:Ethernet  HWaddr 90:b1:1c:1e:eb:68  
              inet addr:192.168.30.84  Bcast:192.168.255.255  Mask:255.255.0.0
              UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1

    ~# ip a
    1: lo:  mtu 16436 qdisc noop state DOWN
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: eth0:  mtu 1500 qdisc mq master bond0 state UP qlen 1000
        link/ether 90:b1:1c:1e:eb:68 brd ff:ff:ff:ff:ff:ff
    3: eth1:  mtu 1500 qdisc mq master bond0 state UP qlen 1000
        link/ether 90:b1:1c:1e:eb:68 brd ff:ff:ff:ff:ff:ff
    4: bond0:  mtu 1500 qdisc noqueue state UP
        link/ether 90:b1:1c:1e:eb:68 brd ff:ff:ff:ff:ff:ff
        inet 192.168.30.82/16 brd 192.168.255.255 scope global bond0
        inet 192.168.30.84/16 brd 192.168.255.255 scope global secondary bond0:0
        inet6 fe80::92b1:1cff:fe1e:eb68/64 scope link
           valid_lft forever preferred_lft forever

* Content of /etc/network/interfaces:

auto bond0                                                                                                       
                                                                                    
    iface bond0 inet static                                                         
        address 192.168.30.82                                                       
        netmask 255.255.0.0                                                         
        gateway 192.168.0.1                                                         
        slaves eth0 eth1                                                            
        bond_mode active-backup                                                     
        bond_miimon 100                                                             
        bond_downdelay 200                                                          
        bond_updelay 200                                                            
                                                                                    
    auto bond0:0                                                                    
    iface bond0:0 inet static                                                       
        address 192.168.30.84                                                       
        netmask 255.255.0.0

I have some servers with multiple network interfaces, setup with bonding and some VLANs. Whenever I reboot the server, one of the bonded network interfaces is not reachable from other servers, nor can any traffic leave that interface. The status from ifconfig on that interface does indicate that the link is up, however. Simply restarting the network at this point will restore everything to normal. The fact that everything works as expected after I restart the network makes me think that my configuration is correct, but it is something in the startup order that isn't working right on reboot, but gets straightened out when restarting the network. I have 7 identical servers with the same setup (other than IP addresses differing), and it happens on all of them, every time they are rebooted. A bit more details on the setup: - Servers: HP ProLiant DL380 - 6 network interfaces, setup as 3 bonded interfaces named: bondm, bondr, bondt. - 4 interfaces are built-in, the remaining 2 are in an add-on PCI card - bondm is configured with 2 VLANs - bondm is used as the default route - bondm is setup to use eth0 and eth2 - bondm is the interface that is failed on reboot **Update:** I've restested this with the exact same configuration and kickstart files, but with SL 6.2 vs 6.3. Everything is fine with 6.2, but I get this behavior with 6.3. Is it due to the different kernels? Here are some of the relevant config files from /etc/sysconfig/network-scripts: $ cat ifcfg-eth0 ifcfg-eth2 ifcfg-bondm ifcfg-bondm.132 ifcfg-bondm.832 DEVICE=eth0 BOOTPROTO=none NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet HWADDR=44:1E:A1:03:71:C4 SLAVE=yes MASTER=bondm ETHTOOL_OPTS="-s eth0 speed 1000 duplex full" DEVICE=eth2 HWADDR=44:1E:A1:03:71:C8 NM_CONTROLLED=no ONBOOT=yes SLAVE=yes MASTER=bondm ETHTOOL_OPTS="-s eth2 speed 1000 duplex full" DEVICE=bondm BOOTPROTO=none NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet IPV4_FAILURE_FATAL=yes IPV6INIT=no BONDING_OPTS="mode=active-backup miimon=100" DEVICE=bondm.132 BOOTPROTO=none NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet IPADDR=192.168.13.19 PREFIX=28 GATEWAY=192.168.13.17 DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no BONDING_OPTS="mode=active-backup miimon=100" VLAN=yes DEVICE=bondm.832 BOOTPROTO=none NM_CONTROLLED=no ONBOOT=yes TYPE=Ethernet IPADDR=10.123.94.69 PREFIX=28 DEFROUTE=no IPV4_FAILURE_FATAL=yes IPV6INIT=no BONDING_OPTS="mode=active-backup miimon=100" VLAN=yes

I have multiple devices (A, B, C). Device A is a sensor that captures data and shares it with device C (Android) over a local Wi-Fi network. The problem is that the application to receive data only works on Android, and Android does not support being connected to two networks simultaneously, so when C connects to the Wi-Fi that A emits, it can correctly receive the data captured by A, but loses internet connection. I would like to know if a third device B (Ubuntu 23.10) with internet thanks to a 4G modem, can connect to the Wi-Fi network that A broadcasts and share internet through that Wi-Fi network so that C has internet when it connects to A's Wi-Fi. A is not configurable, it is a purchased device and I cannot modify anything. A emits a Wi-Fi signal and to receive data it is necessary to connect an Android device (C) to A's Wi-Fi network in order to receive data from its application. If A could connect to a hotspot issued by C there would be no problem since A and C would be connected and C would maintain an internet connection. However, A's app does not support that functionality and the only way to receive the data captured by A is to connect C to the Wi-Fi created by A. I would like to know if I can add another device (B), with an OS that does support simultaneous connection of network interfaces (for example Ubuntu) and share the internet through the Wi-Fi created by A. I have searched many similar questions about it, but none that solve my problem. In most of the questions asked, the internet is shared through a network cable or by creating a hotspot, however, I need to share the internet through the Wi-Fi network that A creates and not create a new one. On the other hand, I have found a lot of information about bridges and bonding, but I have not achieved favorable results either.

I'm running Linux Mint 17.3 on my laptop. When docked, I'm connected via Ethernet, but when I undock, I'd like not to break my ssh sessions, ongoing downloads, etc., and to use the same IP address on the Wi-Fi adapter, so that still appears the same to other machines on my network. Bonding in mode 1, active backup, sounds exactly like what I want. I've found a number of resources online about how to set it up, but network configuration seems to vary quite a bit between distributions and even between different versions of each distribution, so that the steps for this vary quite a bit. What's more, most of the instructions I've found rely on static configuration, like hardcoding network addresses and even WPA passwords into /etc/network/interfaces. I take my laptop to other networks, so I rely on Network Manager to store network configuration. By googling "bond eth0 wlan0", I found a sample /etc/networking/interfaces file that more or less works, but I apparently have to disable Network Manager to keep it from doing weird things with my routing table. And while the bond is active, I can't seem to use the Network Manager applet to change Wi-Fi networks. Network Manager 0.9.8 supports bonded interfaces, but only for Ethernet and InfiniBand connections, not for Wi-Fi. Is there a way to bond Ethernet and Wi-Fi connections that's compatible with Network Manager?

If you create a bond using modprobe bonding then a file is stored in /proc/net/bonding/ giving the details of the bond. Is there any equivalent file, giving the runner type, for teamd?

Is there is any way to set up priority order for multiple interfaces (more than two) for a network bond in active-backup mode? I have 3 interfaces (I know for two interfaces I can address this problem by setting one interface as primary interface), I'm looking for any way to specify priority for each interfaces, such that when one with high priority go down, next priority will get choosed/or any way to address this issue for multiple interfaces.

This is my /etc/network/interfaces file: auto bond0 iface bond0 inet manual address 10.66.7.11/24 gateway 10.66.7.1 bond-mode 802.3ad bond-slaves eth2 eth3 bond-miimon 100 bond-downdelay 200 bond-updelay 400 bond-lacp-rate 1 up ifconfig bond0 10.66.7.11/24 up when I bring the bond0 interface up, it works, but the default gateway is not set # route -n Destination Gateway Genmask Flags Metric Ref Use Iface 10.66.7.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0 I have to set the default gateway manually, and then everything works fine: route add default gw 10.66.7.1 bond0 #route -n Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.66.7.1 0.0.0.0 UG 0 0 0 bond0 10.66.7.0 0.0.0.0 255.255.255.0 U 0 0 0 bond0 why is my default gateway not set automatically, when I have it defined in the /etc/network/interfaces file ?

If I create a connection using network bonding (using the mode active-backup), then although automatic switching to the backup network occurs if I pull out the network cable, it does not occur when the problem is no packets getting through. What can I do to enable automatic switching to the backup network when there is packet loss on the primary with switching back when the primary is working properly (much like how network bonding with mode active-backup seamlessly switches between primary and backup and back when pulling out and plugging back in the network cable)?

I am trying to do a network install of OEL 8 using a custom image. The image works perfectly when the vlan is untagged but I can't get a connection on a tagged vlan. My boot line is (with line feeds added for readability) linuxefi /images/pxeboot/vmlinuz \ inst.repo=https://repo.example.com/kickstart-oel-8/boot \ inst.ks=https://repo.example.com/kickstart-oel-8/ks.cfg \ ip=198.162.100.2::198.162.100.1:24:oel.example.com:bond0:none \ nameserver=198.162.100.100 \ bond=bond0:eno5,eno6:mode=802.3ad,other_options \ vlan=vlan501:bond0 \ rd.plymouth=0 plymouth.enable=0 quiet For systems on an untagged vlan I just remove the vlan= option. The system I am installing on was previously running CentOS 7 with the network configured with a tagged vlan and bonded interface so I know the switch port settings are correct as are the physical interface names. I've looked at a few references both [official](https://docs.centos.org/en-US/centos/install-guide/adminoptions/) and [unofficial](https://leo.leung.xyz/wiki/Red_Hat_kickstart) and played with different formats for the vlan= parameter. The image is based on OEL8u6 minimal iso. The only change I made to the image was to put in custom isolinux and grub configs. Has anybody gotten a setup like this working? If so, what am I doing wrong? I have 250+ servers to rebuild and I really need the process to be as automated as possible. EDIT: After removing quiet from the boot line I see these messages 8021q: adding VLAN 0 to HW filter on device eno5 8021q: adding VLAN 0 to HW filter on device eno6 Ethernet Channel Bonding Driver: 3.7.1 (April 27, 2011) 8021q: adding VLAN 0 to HW filter on device bond0 8021q: adding VLAN 0 to HW filter on device bond0 nlx5_core 0000:5d:00.0 eno5: Link up nlx5_core 0000:5d:00.1 eno6: Link up bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond bond0: active interface up! I filtered out some other lines that did not add any information. I also had to type these in manually but I don't think any typos crept in.

I have two interfaces bonded together in LACP mode (mode=4 802.3ad) in bond0 : The mac address of bond0before reboot :

$ cat /sys/class/net/bond0/address
xx:xx:xx:xx:xx:bf

The mac address of bond0after reboot :

$ cat /sys/class/net/bond0/address
xx:xx:xx:xx:xx:bd

Here is some information about the network configuration :

$ ip -o l | grep state.UP
2: em1:  mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000\    link/ether xx:xx:xx:xx:xx:bd brd ff:ff:ff:ff:ff:ff
3: em2:  mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000\    link/ether xx:xx:xx:xx:xx:bd brd ff:ff:ff:ff:ff:ff
7: bond0:  mtu 9000 qdisc noqueue state UP mode DEFAULT group default qlen 1000\    link/ether xx:xx:xx:xx:xx:bd brd ff:ff:ff:ff:ff:ff
$ grep BONDING_OPTS= /etc/sysconfig/network-scripts/ifcfg-bond0
BONDING_OPTS="mode=4 miimon=100 lacp_rate=1"
$ egrep "(MASTER|SLAVE)=" /etc/sysconfig/network-scripts/ifcfg-em?
/etc/sysconfig/network-scripts/ifcfg-em1:MASTER=bond0
/etc/sysconfig/network-scripts/ifcfg-em1:SLAVE=yes
/etc/sysconfig/network-scripts/ifcfg-em2:MASTER=bond0
/etc/sysconfig/network-scripts/ifcfg-em2:SLAVE=yes
$ egrep -v "^$|^#" /etc/NetworkManager/NetworkManager.conf
[main]
[logging]

Why did the mac address of bond0 change ?

I have a Centos server having a bond interface containing two interfaces, I am trying to remove one of them from the bond. Using ifenslave -d bond0 eno1 it is removed\ however, **after restart** the interface **reverts back** to bond0. How can i make this change permanent?

I want to run some tests using linux network bonding. I am using qemu VMs and I am using a custom-built kernel to run them where I set it up to have bonding statically linked. I see in the documentation that it's possible to set up parameters for bonding (like miimon) when loading the module. But how can these values be set when it's statically linked?