Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #165761

Re: Bond and Bridge problem [Off-list]

Show all headers | View raw

On 21.03.2016 00:30, Tom H wrote:
> [Off-list]
>
> Try rewriting "/etc/network/interfaces" as (I didn't check the actual
> bond and bridge options):
>
> <begin>
> iface eth0 inet manual
> bond-master bond0
>
> iface eth1 inet manual
> bond-master bond0
>
> iface bond0 inet manual
> bond-mode 802.3ad
> bond-miimon 100
> bond-downdelay 200
> bond-updelay 200
> bond-lacp-rate 4
>
> auto br0
> iface br0 inet static
> address 10.10.0.159
> netmask 255.255.0.0
> gateway 10.10.0.254
> mtu 9000
> vlan-raw-device bond0
> bridge_ports bond0
> bridge_stp off
> bridge_fd 0
> bridge_maxage 0
> bridge_ageing 0
> bridge_maxwait 0
> </end>

I made this config and interfaces was not brought up after restart. auto 
eth0 and auto eth1 must be present.
>
> Reasons:
>
> 1) You don't need "broadcast" or "network" because they're calculated
> by ifupdown.

Remove and seems it is ok. Less to calc.

>
> 2) You don't need "auto" except for the bridge because of this extract
> from "man bridge-utils-interfaces":
>
> <begin>
> The main extension is the bridge_ports option, with it you describe that
> the interface is a bridge and what ports does it have. These ports are
> the interfaces that are part of the bridge, and they shouldn't have any
> stanzas defining them on the interfaces file.
> </end>

Does this take into account that bridge-utils must bring up also eth0 
and eth1? How to define bond configuration if the interface must not 
have any stanzas defined? The order to bring up is eth0+eth1 -> bond0 -> 
br0.

>
> 3) You don't need "bond-slaves" because of this extract from
> "/usr/share/doc/ifenslave/README.Debian.gz":
>
> <begin>
> Previous versions of the package supported specifying the slaves all in
> the stanza for the bonding interface, using the "bond-slaves" option.
> However, in such a configuration there is a race condition between
> bringing up the hardware driver for the ethernet devices and attempting
> to bring up the bonded interface; the bonding interface needs to be
> initiated from the slave interfaces instead.
> </end>
>

Ok, this definition works for bonding.


Still, the bridge scripts may be having problem with bonds? After 
restart route -n does not have default entry to gateway defined, only 
one route for local lan.

Back to linux.debian.user | Previous | Next | Find similar | Unroll thread

Thread

Re: Bond and Bridge problem [Off-list] Mimiko <vbvbrj@gmail.com> - 2016-03-21 11:10 +0100

csiph-web