Hide Forgot
Description of problem: system-config-network lacks way to do bridging, a very common thing that should be supported
Just to note that Fedora supports bridging. Just system-config-network that doesn't. To make a bridge: 1. service network stop 2. Create a /etc/sysconfig/networking/devices/ifcfg-br0 like any other device, but with TYPE=Bridge; 3. ln /etc/sysconfig/networking/devices/ifcfg-br0 /etc/sysconfig/networking/profiles/default/ifcfg-br0 4. ln /etc/sysconfig/networking/devices/ifcfg-br0 /etc/sysconfig/network-scripts/ifcfg-br0 5. Edit ifcfg-* files for other interfaces that will participate on the bridge, take out all address information (IPADDR, NETMASK, etc) and add BRIDGE=br0. 6. service network start The bridge is shown in system-config-network, but you cant edit it.
Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
Still an issue in current rawhide.
thanks for your update
Changing version to '9' as part of upcoming Fedora 9 GA. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
(In reply to comment #1) > Just to note that Fedora supports bridging. Just system-config-network that > doesn't. To make a bridge: > > 1. service network stop > 2. Create a /etc/sysconfig/networking/devices/ifcfg-br0 like any other device, > but with TYPE=Bridge; > 3. ln /etc/sysconfig/networking/devices/ifcfg-br0 > /etc/sysconfig/networking/profiles/default/ifcfg-br0 > 4. ln /etc/sysconfig/networking/devices/ifcfg-br0 > /etc/sysconfig/network-scripts/ifcfg-br0 > 5. Edit ifcfg-* files for other interfaces that will participate on the bridge, > take out all address information (IPADDR, NETMASK, etc) and add BRIDGE=br0. > 6. service network start > > The bridge is shown in system-config-network, but you cant edit it. And if you try to edit it, a traceback occurs. (Fedora 10, system-config-network-1.5.94-2.fc10.noarch) Component: system-config-network Version: 1.5.94 Summary: TBf8f4a16f NCDevice.py:177:getDialog:TypeError: exceptions must be classes, instances, or strings (deprecated), not NotImplementedType Traceback (most recent call last): File "/usr/share/system-config-network/netconfpkg/gui/maindialog.py", line 814, in on_editButton_clicked self.editButtonFunc[self.active_page](button) File "/usr/share/system-config-network/netconfpkg/gui/maindialog.py", line 922, in on_deviceEditButton_clicked button = self.editDevice(device) File "/usr/share/system-config-network/netconfpkg/gui/maindialog.py", line 950, in editDevice dialog = device.getDialog() File "/usr/share/system-config-network/netconfpkg/NCDevice.py", line 177, in getDialog raise NotImplemented TypeError: exceptions must be classes, instances, or strings (deprecated), not NotImplementedType Local variables in innermost frame: self: Device.AllowUser=False Device.BootProto=dhcp Device.Device=br0 Device.DeviceId=br0 Device.HardwareAddress=00:1e:4f:c1:e6:b2 Device.Hostname=jerry-opti755 Device.IPv6Init=False Device.NMControlled=False Device.OnBoot=False Device.Type=Bridge
should be raise NotImplementedError
(In reply to comment #7) > should be > > raise NotImplementedError Which then just changes the names in the traceback: Component: system-config-network Version: 1.5.94 Summary: TBf8f4a16f NCDevice.py:177:getDialog:NotImplementedError Traceback (most recent call last): File "/usr/share/system-config-network/netconfpkg/gui/maindialog.py", line 814, in on_editButton_clicked self.editButtonFunc[self.active_page](button) File "/usr/share/system-config-network/netconfpkg/gui/maindialog.py", line 922, in on_deviceEditButton_clicked button = self.editDevice(device) File "/usr/share/system-config-network/netconfpkg/gui/maindialog.py", line 950, in editDevice dialog = device.getDialog() File "/usr/share/system-config-network/netconfpkg/NCDevice.py", line 177, in getDialog raise NotImplementedError NotImplementedError Local variables in innermost frame: self: Device.AllowUser=False Device.BootProto=dhcp Device.Device=br0 Device.DeviceId=br0 Device.HardwareAddress=00:1e:4f:c1:e6:b2 Device.Hostname=jerry-opti755 Device.IPv6Init=False Device.NMControlled=False Device.OnBoot=False Device.Type=Bridge
This message is a reminder that Fedora 9 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 9. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '9'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 9's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 9 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
*** Bug 562608 has been marked as a duplicate of this bug. ***
Adding bridge support to system-config-network should be pretty trivial how come no one has bothered to do it in the four years since the initial request was made? Bridging is more important now that KVM is mainstream. KVM requires a bridge device if you want a VM to be visable on your network. When this request was originally posted the main virtualization option was VMware which handled the bridging problem itself so it wasn't as important that the network GUI do the job, but now that KVM is becoming the virtualizer of choice it would be nice if bridges were handled like any other network device.
A suggestion for handling the UI. Just add an Enable Bridging button to the General Device Dialog. Enabling the option would put the line, BRIDGE=br# Into the ifcfg-eth# script and create the ifcfg-br# script which would get it's parameters from the same device dialog, for example, DEVICE=br0 TYPE=Bridge BOOTPROTO=none DNS1=192.168.1.1 GATEWAY=192.168.1.1 IPADDR=192.168.1.6 NETMASK=255.255.255.0 ONBOOT=yes NM_CONTROLLED=no IPV6INIT=no USERCTL=no
Moving to NetworkManager, the one tool to rule it all
*** Bug 558982 has been marked as a duplicate of this bug. ***
*** Bug 639522 has been marked as a duplicate of this bug. ***
This is still a problem in Fedora 14 beta. I need it to quickly transfer all of my data to my NAS device (it's normally connected by wireless), without messing with the configuration. Windows has allowed bridging to be easy since at least Windows XP.
Is there some way to sponsor this work? I am not a coder myself but i would be happy to donate $$ for this feature. I myself use a laptop and having bridge support in NetworkManager would be awsome.
I'd be happy to sponsor it a bit too.. There are only a few major annoyances left in Fedora, and this is one of them. It couldn't be too hard considering even mobiles these days act as Mobile AP's.
Still a problem in F15 and becoming more annoying as more programs use NetworkManager to determine if network connectivity is available or not (empathy and the yum update applet on a default F15 installation for example) and therefore refuse to make use of a manually created bridge without further configuration changes.
I agree. It would be very nice if i could have bridging without the need for disabling "NetworkManager" and enabling "network". I use bridging for my KVM virtual machines on my laptop, but i also need be able to connect to wireless as well when im not using bridging. here's a script i use to automate the transition from NetworkManager to "bridging mode" #!/usr/bin/sh virsh net-destroy default service NetworkManager stop chkconfig NetworkManager off service network restart virsh net-start default NOTES: as of this moment i havent yet tested if chkconfig is "session only" or "until you change it back" Honestly, this has been a problem for several years. Why has noone built this into network manager yet? As a previous poster stated, more and more programs are starting to depend on NetworkManager to get the link state. if NM cant cope with bridging, this problem is going to become increasingly severe. I too might be willing to sponsor this (Especially if network manager and make bridging possible for wireless networks as well(by whatever means necessary))
I have changed the release to Fedora 15 since it still appears to be a "problem". This report seems to have been originally opened against system-config-network but is now against NetworkManager since that is the currenet direction for network configuration, etc. Obviously, there must be some significant problem supporting bridging with NetworkManager or (with all of the griping) it would have been done. Is there any hope or is this one of those "you can't get there from here" sort of problems? Is this better taken up on the mailing list or here in bugzilla?
Created attachment 513492 [details] ifmodeswitcher Here is a quick script i wrote to switch between bridge mode and normal mode for those of us who need to be able to use the features of wifi and bridging in the same machine, on the same session even. be advised that you cant do both at the same time with this script...
Moving it up to 16 because what do you know, Network Manager still doesn't support bridging.
I saw in the F17 features list that the plumbing for this is now in place. The GUI is due in F18 at the moment.
(In reply to comment #25) > I saw in the F17 features list that the plumbing for this is now in place. > The GUI is due in F18 at the moment. AWESOME! I love virt-manager way more than VirtualBox or VMWare, but it's pretty useless to me until bridging is implemented. I really, really hope it gets put into F18. Too bad it's going to be another 6 months until we have that....
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Changed release. Although there is development progress, this functionality is still not available.
(In reply to comment #28) > Changed release. Although there is development progress, this functionality > is still not available. About to land in Fedora soon.
Yes indeed. I run with updated versions because I need the functionality and when I installed the with with git20121211, the bridge update bit me on virtual network devices for IPv4 but (strangely) not IPv6.
(In reply to comment #29) > > About to land in Fedora soon. Hi Dan, Any chance this can be backported to F18, or just F19 as per your feature: https://fedoraproject.org/wiki/Features/NetworkManagerBridging -c
Oh NO! I was so looking forward to this. I see from https://fedoraproject.org/wiki/Features/NetworkManagerBridging Current status Targeted release: Fedora 20 Last updated: 2013-03-19 Percentage of completion: 50% For those of us that would REALLY like to use bridging with libvirt/QEMU/KVM, is there a recommended work-around for use with Fedora 18?
The code is going to land, it's just not going to make the F19 feature freeze deadline. And because of this, we want to make sure it's rock-solid before that happens, since people don't have the heads-up that the feature process would normally give.
That is good and I am willing to do whatever I can to help test it. But what we really need to know NOW is the recommended work-around. I am willing to accept that the network management applet of the Gnome Control Center can not be used or displays erroneous or misleading information. But does the NetworkManager service work correctly? if so, what should the ifcfg-br1 and ifcfg-em1 files look like? Are there steps to be taken before configuring NetworkManager? What about routing? These are some of the details we hope will become transparent and I am certain you know them better than we do. There is a lot of information available that seems dated in one regard or another and virsh iface-bridge, which seemed like a big step forward, returns an error (https://bugzilla.redhat.com/show_bug.cgi?id=919625). It is my understanding that a bridge could be configured to make the virtual machine guests appear on the network as if they were network peers of the physical machine host; they would used the same DHCP as the physical machines, the same address range, the same DNS, etc. I have tried piecing together the configuration, but nothing I have done quite works. Please, is there a document you could reference or instructions you could provide for of us that are not expert enough in the networking utilities to dig it out on our own?
If you need a simple work-around for simple bridging there is support for it in virt-manager by using a macvtap device. To bridge a guest to your configured em1/eth0 just edit your virtual-machine in virt-manager on the nic in virt-manager of the virtual machine there should be a drop drown list for: "Source device". Just pick "Host device eth0 : macvtap"
I have tried macvtap. While it works with NetworkManager I have two problems with this approach: 1) It requires a second network for connectivity from the VM guest to the host. 2) It requires manual use of a GUI to set it up. I need something that I can script, start, and come back when it is ready to use. So far, http://docs.fedoraproject.org/en-US/Fedora/17/html/System_Administrators_Guide/s2-networkscripts-interfaces_network-bridge.html is the most recent reference I have found. It only works if NetworkManager is replace is replaced by network on the host, but this can be scripted. I am using this on a server class machine so wireless networking is not important. What do I lose with this approach?
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.