From Fedora Project Wiki
No edit summary
Line 3: Line 3:
this page will include a working and tested configuration.
this page will include a working and tested configuration.


== The 'keyfile' way ==
=== Using iproute2 ===
 
Bridge devices can be easily adding using the <code>ip</code> command. This way is suitable for testing.
 
<pre>
name=my-bridge
 
ip link add $name type bridge
</pre>
 
=== Using NetworkManager (native configuration) ===


TODO: Test the configuration.
TODO: Test the configuration.
Line 29: Line 39:
</pre>
</pre>


== The 'ifcfg-rh' way ==
== Using NetworkManager (ifcfg-rh configuration plugin) ==


TODO: Fix and simplify the following configuration.
TODO: Fix and simplify the following configuration.

Revision as of 20:47, 10 December 2012

I haven't yet tested this and the following configuration is reported to be broken through the mailing list. But, eventually, this page will include a working and tested configuration.

Using iproute2

Bridge devices can be easily adding using the ip command. This way is suitable for testing.

name=my-bridge

ip link add $name type bridge

Using NetworkManager (native configuration)

TODO: Test the configuration.

bonding interface:

[connection]
id=...
uuid=...
type=bond

[bond]
interface-name=bond0

slave interface:

[connection]
id=...
uuid=...
master=bond0
slave-type=bond

Using NetworkManager (ifcfg-rh configuration plugin)

TODO: Fix and simplify the following configuration.

# cat ifcfg-bond0
DEVICE=bond0
BOOTPROTO=dhcp
ONBOOT=yes
NM_CONTROLLED="yes"
BONDING_MASTER="yes"
BONDING_OPTS="miimon=50 mode=balance-tlb"

# cat ifcfg-em3
BOOTPROTO="none"
DEVICE="em3"
ONBOOT="yes"
MASTER="bond0"
SLAVE="yes"
TYPE=Ethernet
NM_CONTROLLED="yes"

This won't work!