Technical data

4. Packages

Further informations about ethtool can be found here: http://linux.die.net/man/8/ethtool

4.2.9. Example

For understanding a simple example is certainly helpful. In our example we assume 2 parts

of a building which are connected by 2 x 100 Mbit/s lines. Four separate networks should be

routed from one building to the other.

To achieve this a combination of bonding (joining the two physical lines) VLAN (to trans-

port several separate networks on the bond) and bridging (to link the diﬀerent nets to the

bond/VLAN) is used. This has been tested successful on 2 Intel e100 cards and 1 Adaptec

4-port card ANA6944 in each building’s router. The two e100 have the device names ’eth0’

and ’eth1’. They are used for connecting the building. Intel e100’s are the only cards known

to work ﬂawlessly with VLAN by now. Gigabit-cards should work too. The 4 ports of the

multiport-card are used for the networks and have device names ’eth2’ to ’eth5’.

At ﬁrst the two 100 Mbit/s lines will be bonded:

OPT_BONDING_DEV='yes'

BONDING_DEV_N='1'

BONDING_DEV_1_DEVNAME='bond0'

BONDING_DEV_1_MODE='balance-rr'

BONDING_DEV_1_DEV_N='2'

BONDING_DEV_1_DEV_1='eth0'

BONDING_DEV_1_DEV_2='eth1'

This creates the device ’bond0’. Now the two VLANs will be built on this bond. We use

VLAN-IDs 11, 22, 33 und 44:

OPT_VLAN_DEV='yes'

VLAN_DEV_N='4'

VLAN_DEV_1_DEV='bond0'

VLAN_DEV_1_VID='11'

VLAN_DEV_2_DEV='bond0'

VLAN_DEV_2_VID='22'

VLAN_DEV_3_DEV='bond0'

VLAN_DEV_3_VID='33'

VLAN_DEV_4_DEV='bond0'

VLAN_DEV_4_VID='44'

Over this two VLAN connections the bridge into the networks segments will be built. Rout-

ing is not necessary this way.

OPT_BRIDGE_DEV='yes'

BRIDGE_DEV_N='4'

BRIDGE_DEV_1_NAME='_VLAN11_'

BRIDGE_DEV_1_DEVNAME='br11'

BRIDGE_DEV_1_DEV_N='2'

BRIDGE_DEV_1_DEV_1='bond0.11'

BRIDGE_DEV_1_DEV_2='eth2'

BRIDGE_DEV_2_NAME='_VLAN22_'

BRIDGE_DEV_2_DEVNAME='br22'

BRIDGE_DEV_2_DEV_N='2'