# Bond0 as primary interface (Bonding, LACP)

**URL:** <https://forums.suse.com/t/bond0-as-primary-interface-bonding-lacp/6594>\
**Category:** RancherOS\
**Created:** [June 9, 2017, 4:54pm UTC](https://forums.suse.com/t/bond0-as-primary-interface-bonding-lacp/6594 "2017-06-09T16:54:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![bryman55](https://avatars.discourse-cdn.com/v4/letter/b/8e8cbc/32.png) [@bryman55](https://forums.suse.com/u/bryman55)\
**Post date:** [June 9, 2017, 4:54pm UTC](https://forums.suse.com/t/bond0-as-primary-interface-bonding-lacp/6594/1 "2017-06-09T16:54:52Z")

</div>

I have an interesting problem, I can create a bond just fine. However if I just configure a bond0 and no other interface, the system tries to configure one of my bonding interfaces as a primary interface. I would like bond0 to be the primary interface. So in my example below eth3 is reconfigured as a regular interface. If I plug an additional network port at eth0 my bond0 works fine. Again if I only want bond0, eth3 gets reconfigure from bond slave to eth3 dhcp. Any thoughts?

```
rancher:
  network:
    interfaces:
      eth*:
        dhcp: false
      eth2:
        bond: bond0
      eth3:
        bond: bond0
      bond0:
        dhcp: true
        bond_opts:
          mode: 6
          miimon: 100
          lacp_rate: 1
          xmit_hash_policy: 1
        mtu: 9000
```