After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 543232 - Add support for "shared physical interface" bridging
Add support for "shared physical interface" bridging
Status: RESOLVED DUPLICATE of bug 546197
Product: NetworkManager
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: Dan Williams
Dan Williams
Depends on:
Reported: 2008-07-16 07:10 UTC by Mark McLoughlin
Modified: 2009-02-24 00:11 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Mark McLoughlin 2008-07-16 07:10:30 UTC
With virtualization, e.g. with KVM or Xen or lguest, one often wants one's guest machines to appear on the same physical network as the host machine. This is especially true on server machines which have a fixed network connection.

You can achieve this by creating a bridge interface, running dhcp on that and then adding the physical ethernet device to the bridge. From then on, backend network interfaces from guest machines (e.g. tap devices) can be added to the bridge allowing them to appear on the lan.

See this page on the libvirt wiki for how we recommend people configure such a bridge:

You'll note that the first step is to disable NetworkManager - that's what we want to fix :-)

We use the name "shared physical interface" to more accurately easily describe this bridge - the fact that we're configuring a bridge to the user is not important, but rather the fact that the physical interface is being configured so that it can be shared with virtual machines. See the "User Visible Concepts" part in this now obsolete write-up:
Comment 1 Dan Williams 2009-02-24 00:11:57 UTC
I do have a plan for bridging (and it'll handle bonding in much the same way).  Hopefully F11 material.  Duping to another tracking bug.

*** This bug has been marked as a duplicate of 546197 ***