Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

We currently are setup with bonded nics. I layered vlans ontop of bond0 and used the vlans as the interfaces for the bridges. Following the examples in the article, a config that looks something like this should work:

auto eth0
iface eth0 inet manual
  bond-master bond0

auto eth1
iface eth1 inet manual
  bond-master bond0

auto bond0
iface bond0 inet manual
  bond-mode 802.3ad
  bond-miimon 100
  bond-lacp-rate 1
  bond-slaves eth0 eth1

# This is vlan 100. This requires additional
# configuration on the switch itself.
auto bond0.100
iface bond0.100 inet manual
  up ip l s $IFACE up
  down ip l s $IFACE down
  vlan-raw-device bond0

# I have kept the name as br-eth0 because that is what the

interface is named in the article. # I suggest creating it as something less confusing like br-data auto br-eth0 iface br-eth0 inet static address 10.240.0.10 netmask 255.255.255.0 gateway 10.240.0.1 nameserver 8.8.8.8

We currently are setup with bonded nics. I layered vlans ontop of bond0 and used the vlans as the interfaces for the bridges. Following the examples in the article, a config that looks something like this should work:

auto eth0
iface eth0 inet manual
  bond-master bond0

auto eth1
iface eth1 inet manual
  bond-master bond0

# Remember this isn't the only way to bond these nics.
# Make sure to use the appropriate bond-mode
auto bond0
iface bond0 inet manual
  bond-mode 802.3ad
  bond-miimon 100
  bond-lacp-rate 1
  bond-slaves eth0 eth1

# This is vlan 100. This requires additional
# configuration additional configuration
# on the switch itself.
itself. Also install the `vlan` package if you
# haven't done so already.
auto bond0.100
iface bond0.100 inet manual
  up ip l s $IFACE up
  down ip l s $IFACE down
  vlan-raw-device bond0

# I have kept the name as br-eth0 because that is what the

# interface is named in the article. # I suggest creating it as something less confusing like br-data auto br-eth0 iface br-eth0 inet static address 10.240.0.10 netmask 255.255.255.0 gateway 10.240.0.1 nameserver 8.8.8.8

8.8.8.8

We currently are setup with bonded nics. I layered vlans ontop of bond0 and used the vlans as the interfaces for the bridges. Following the examples in the article, a config that looks something like this should work:

auto eth0
iface eth0 inet manual
  bond-master bond0

auto eth1
iface eth1 inet manual
  bond-master bond0

# Remember this isn't the only way to bond these nics.
# Make sure to use the appropriate bond-mode
auto bond0
iface bond0 inet manual
  bond-mode 802.3ad
  bond-miimon 100
  bond-lacp-rate 1
  bond-slaves eth0 eth1

# This is vlan 100. This requires additional configuration
# on the switch itself. Also install the `vlan` package if you
# haven't done so already.
auto bond0.100
iface bond0.100 inet manual
  up ip l s $IFACE up
  down ip l s $IFACE down
  vlan-raw-device bond0

# I have kept the name as br-eth0 because that is what the
# interface is named in the article.
# article. I suggest creating it as as
# something less confusing like br-data
br-data.
auto br-eth0
iface br-eth0 inet static
  address 10.240.0.10
  netmask 255.255.255.0
  gateway 10.240.0.1
  nameserver 8.8.8.8

We currently are setup with bonded nics. I layered vlans ontop of bond0 and used the vlans as the interfaces for the bridges. Following the examples in the article, a config that looks something like this should work:

auto eth0
iface eth0 inet manual
  bond-master bond0

auto eth1
iface eth1 inet manual
  bond-master bond0

# Remember this isn't the only way to bond these nics.
# Make sure to use the appropriate bond-mode
auto bond0
iface bond0 inet manual
  bond-mode 802.3ad
  bond-miimon 100
  bond-lacp-rate 1
  bond-slaves eth0 eth1
  up ip link set bond0 promisc on

# This is vlan 100. This requires additional configuration
# on the switch itself. Also install the `vlan` package if you
# haven't done so already.
auto bond0.100
iface bond0.100 inet manual
  up ip l s $IFACE addr add 0.0.0.0 dev bond0.100
  up ip link set br-eth0 up
  down ip l s $IFACE down
  vlan-raw-device bond0

# I have kept the name as br-eth0 because that is what the
# interface is named in the article. I suggest creating it as
# something less confusing like br-data.
auto br-eth0
iface br-eth0 inet static
  address 10.240.0.10
  netmask 255.255.255.0
  gateway 10.240.0.1
  nameserver 8.8.8.8
  bridge_ports bond0.100

We currently are setup with bonded nics. I layered vlans ontop of bond0 and used the vlans as the interfaces for the bridges. Following the examples in the article, a config that looks something like this should work:

RedHat and derivites should work with something like this:

DEVICE=eth0
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
#######################
DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
#######################
DEVICE=bond0
BOOTPROTO=none
ONBOOT=yes
USERCTL=no
#######################
DEVICE=bond0.100
BOOTPROTO=none
ONBOOT=yes
USERCTL=no
VLAN=yes
NM_CONTROLLED=no
BRIDGE=br-eth0
#######################
# Please change bridge name to somethine else
#######################
DEVICE=br-eth0
TYPE=Bridge
IPADDR=10.240.0.10
NETMASK=255.255.255.0
ONBOOT=yes
BOOTPROTO=none
NM_CONTROLLED=no
DELAY=0

I just named the bridge br-eth0 because that is what the guide says, change it to something more meaningful.

This would be for Debian (should work for Ubuntu)

auto eth0
iface eth0 inet manual
  bond-master bond0

auto eth1
iface eth1 inet manual
  bond-master bond0

# Remember this isn't the only way to bond these nics.
# Make sure to use the appropriate bond-mode
auto bond0
iface bond0 inet manual
  bond-mode 802.3ad
  bond-miimon 100
  bond-lacp-rate 1
  bond-slaves eth0 eth1
  up ip link set bond0 promisc on

# This is vlan 100. This requires additional configuration
# on the switch itself. Also install the `vlan` package if you
# haven't done so already.
auto bond0.100
iface bond0.100 inet manual
  up ip addr add 0.0.0.0 dev bond0.100
  up ip link set br-eth0 up
  vlan-raw-device bond0

# I have kept the name as br-eth0 because that is what the
# interface is named in the article. I suggest creating it as
# something less confusing like br-data.
auto br-eth0
iface br-eth0 inet static
  address 10.240.0.10
  netmask 255.255.255.0
  gateway 10.240.0.1
  nameserver 8.8.8.8
  bridge_ports bond0.100