Networking/Bridging: Difference between revisions

Latest revision as of 08:01, 26 April 2013

Using iproute2 (runtime only)

Example configuration:

master=bridge0
slave=eth0

Create a bridge:

ip link add $master type bridge

Enslave an ethernet device:

ip link set $slave master $master

Release an ethernet device:

ip link set $slave nomaster

Remove a bridge:

ip link delete $master

Using NetworkManager (permanent)

NetworkManager in Fedora 18+ already has some support for bridging. As of 2012-04-02, it is far from perfect but at least there's something to experiment with. Please file bug reports to the upstream bugzilla and link them here.

Using configuration files (keyfile)

Bridge:

[connection]
id=Bridge
uuid=fc61f6e5-8900-4c6f-915c-eb55714eb874
interface-name=bridge0
type=bridge
autoconnect=false

[bridge]
interface-name=bridge0

Slave:

[connection]
id=Slave
uuid=2e1906b1-92a4-4206-b2d3-eecfd07241e9
type=802-3-ethernet
master=fc61f6e5-8900-4c6f-915c-eb55714eb874
slave-type=bridge

[802-3-ethernet]
mac-address=52:54:00:8e:93:da

Bug reports:

bridge/bond: duplicate interface name in keyfile configuration

Using configuration files (ifcfg)

ifcfg-Bridge:

UUID=fc61f6e5-8900-4c6f-915c-eb55714eb874
TYPE=bridge
DEVICE=bridge0

ifcfg-Slave:

UUID=2e1906b1-92a4-4206-b2d3-eecfd07241e9
TYPE=Ethernet
HWADDR=52:54:00:8e:93:da
BRIDGE=fc61f6e5-8900-4c6f-915c-eb55714eb874

Note: I haven't tested this particular configuration. Feel free to test and adjust.

Using command-line interface (nmcli)

Warning: This is new development and it be available with NM 0.9.10 or an earlier snapshot.

SLAVE_MAC=00:aa:bb:cc:dd:ee

nmcli connection add name Bridge type bridge iface testbridge
nmcli connection add name Slave type ethernet mac $SLAVE_MAC

@@ Line 1: / Line 1: @@
-=== Using iproute2 (runtime) ===
+== Using iproute2 (runtime only) ==
 Example configuration:
@@ Line 32: / Line 32: @@
 </pre>
-=== Using NetworkManager (permanent) ===
+== Using NetworkManager (permanent) ==
-'''NOTE: This is not yet supported in Fedora.  This page merely documents configurations which could be tested when NetworkManager stops explicitly ignoring Bridge configurations.'''
+NetworkManager in Fedora 18+ already has some support for bridging. As of 2012-04-02, it is far from perfect but at least there's something to experiment with. Please file bug reports to the upstream bugzilla and link them here.
-NetworkManager is getting support for bridging. It is not yet in the master branch (as of 2012-06-14) and it doesn't yet work for
+=== Using configuration files (keyfile) ===
-me (pavlix) but I believe it's time to have some testing configuration to work with. It may not work for you, so feel free
-to modify this page when bridging support is generally available.
-Tracker: https://bugzilla.gnome.org/show_bug.cgi?id=546197
-==== The 'keyfile' way ====
 Bridge:
@@ Line 50: / Line 44: @@
 id=Bridge
 uuid=fc61f6e5-8900-4c6f-915c-eb55714eb874
-interface-name=br0
+interface-name=bridge0
 type=bridge
 autoconnect=false
 [bridge]
-interface-name=br0
+interface-name=bridge0
 </pre>
@@ Line 72: / Line 66: @@
 </pre>
-==== The 'ifcfg' way ====
+Bug reports:
+* [https://bugzilla.gnome.org/show_bug.cgi?id=696936  bridge/bond: duplicate interface name in keyfile configuration]
+=== Using configuration files (ifcfg) ===
 ifcfg-Bridge:
@@ Line 79: / Line 77: @@
 UUID=fc61f6e5-8900-4c6f-915c-eb55714eb874
 TYPE=bridge
-DEVICE=br0
+DEVICE=bridge0
 </pre>
@@ Line 88: / Line 86: @@
 TYPE=Ethernet
 HWADDR=52:54:00:8e:93:da
-BRIDGE=br0
+BRIDGE=fc61f6e5-8900-4c6f-915c-eb55714eb874
+</pre>
+Note: I haven't tested this particular configuration. Feel free to test and adjust.
+=== Using command-line interface (nmcli) ===
+Warning: This is new development and it be available with NM 0.9.10 or an earlier snapshot.
+<pre>
+SLAVE_MAC=00:aa:bb:cc:dd:ee
+nmcli connection add name Bridge type bridge iface testbridge
+nmcli connection add name Slave type ethernet mac $SLAVE_MAC
 </pre>

Search