Bond Interface

English Network/Internet
#1

I am running several servers with bond interfaces. Upgrading to Opensuse 13.1 or higher I run inter problems having bond interfaces active.
Having eth0 and eth1 configured as bond slaves and running on DHCP it happens, that eth0 gets the same IP address as bond0 and the default route points to the our gateway ip. But it points to eth0 instead of bond0
Always when the system is restarted this occurs. Sometimes this also happens if the system is up for several days.
This never happens to eth1

ifcfg-eth0:

BOOTPROTO=‘none’
BROADCAST=’’
ETHTOOL_OPTIONS=’’
IPADDR=’’
MTU=’’
NAME=‘82541GI Gigabit Ethernet Controller’
NETMASK=’’
NETWORK=’’
REMOTE_IPADDR=’’
STARTMODE=‘hotplug’
USERCONTROL=‘no’

ifcfg-eth1

BOOTPROTO=‘none’
BROADCAST=’’
ETHTOOL_OPTIONS=’’
IPADDR=’’
MTU=’’
NAME=‘82541GI Gigabit Ethernet Controller’
NETMASK=’’
NETWORK=’’
REMOTE_IPADDR=’’
STARTMODE=‘hotplug’
USERCONTROL=‘no’

ifcfg-bond0
BONDING_MASTER=‘yes’
BONDING_MODULE_OPTS=‘mode=active-backup miimon=100’
BONDING_SLAVE0=‘eth0’
BONDING_SLAVE1=‘eth1’
BOOTPROTO=‘dhcp4’
BROADCAST=’’
ETHTOOL_OPTIONS=’’
IPADDR=’’
MTU=’’
NAME=’’
NETMASK=’’
NETWORK=’’
REMOTE_IPADDR=’’
STARTMODE=‘auto’
USERCONTROL=‘no’

#2

Although I’m not running a bonding configuration on my machines,

I assume you’re using YAST to configure bonding (using classical ifup/ifdown aka Wicked).

Recommend you inspect the** routing tab** of your Network Settings in YAST.
For your bonding interface, my guess your IPv4 interface routing value is empty (thereby picking up DHCP settings which is not what you want).
If you have a properly configured bonding interface set up by YAST, I assume you should see the interface listed as a device (Hmmm… I think that “device” is a misnomer, you’re setting to an interface and not a physical device) and you can set it. If it’s not listed, then we probably need to more closely inspect how you set up your bonding (physically creating interface config files instead of using YAST?)

TSU