Hi, according to http://fedoraproject.org/wiki/Features/NMEnterpriseNetworking NetworkManager should support bridging now in Fedora 17. The question is how can I set this up? The GUI bits don't seem to be there yet but that page also doesn't explain how this could be set up manually.
How can this be a feature of the release when it can't be used by anyone?
Regards, Dennis
On Wed, 2012-06-13 at 15:12 +0200, Dennis Jacobfeuerborn wrote:
Hi, according to http://fedoraproject.org/wiki/Features/NMEnterpriseNetworking NetworkManager should support bridging now in Fedora 17. The question is how can I set this up? The GUI bits don't seem to be there yet but that page also doesn't explain how this could be set up manually.
How can this be a feature of the release when it can't be used by anyone?
I note:
"NetworkManager now supports configuration of bridges, bonds, and VLANs. Existing configurations should be managed seamlessly by NM as long as it is allowed to do so (ie, by removing NM_CONTROLLED=no from ifcfg files)."
So it sounds like, right now, what you can do is take an existing bridged config, drop NM_CONTROLLED=no from the ifcfg files, enable the NM service if necessary, and then see if NM takes over properly. It doesn't seem to be explicitly stated, but reading between the lines, the UI stuff isn't done yet.
On 06/13/2012 12:03 PM, Adam Williamson wrote:
So it sounds like, right now, what you can do is take an existing bridged config, drop NM_CONTROLLED=no from the ifcfg files, enable the NM service if necessary, and then see if NM takes over properly. It doesn't seem to be explicitly stated, but reading between the lines, the UI stuff isn't done yet.
I just tried this, and NetworkManager didn't bring up either the physical interface or the bridge. Here are ifcfg-eth0 and ifcfg-br0:
DEVICE=eth0 ONBOOT=yes TYPE=Ethernet IPV6INIT=no HWADDR=00:22:4d:4f:c7:ed BRIDGE=br0 #NM_CONTROLLED=no
IPADDR=172.31.250.1 GATEWAY=172.31.250.254 NETMASK=255.255.255.0 DEVICE=br0 ONBOOT=yes TYPE=Bridge IPV6INIT=no DELAY=0 #NM_CONTROLLED=no
Anyone have any ideas?
On Wed, 2012-06-13 at 16:52 -0500, Ian Pilcher wrote:
On 06/13/2012 12:03 PM, Adam Williamson wrote:
So it sounds like, right now, what you can do is take an existing bridged config, drop NM_CONTROLLED=no from the ifcfg files, enable the NM service if necessary, and then see if NM takes over properly. It doesn't seem to be explicitly stated, but reading between the lines, the UI stuff isn't done yet.
I just tried this, and NetworkManager didn't bring up either the physical interface or the bridge. Here are ifcfg-eth0 and ifcfg-br0:
DEVICE=eth0 ONBOOT=yes TYPE=Ethernet IPV6INIT=no HWADDR=00:22:4d:4f:c7:ed BRIDGE=br0 #NM_CONTROLLED=no
IPADDR=172.31.250.1 GATEWAY=172.31.250.254 NETMASK=255.255.255.0 DEVICE=br0 ONBOOT=yes TYPE=Bridge IPV6INIT=no DELAY=0 #NM_CONTROLLED=no
Anyone have any ideas?
Not here. Might be worth poking Dan directly by email or on IRC (dcbw). He may be able to clarify.
Hey,
On Wed, 13 Jun 2012 14:57:21 -0700 Adam Williamson awilliam@redhat.com wrote:
On Wed, 2012-06-13 at 16:52 -0500, Ian Pilcher wrote:
On 06/13/2012 12:03 PM, Adam Williamson wrote:
So it sounds like, right now, what you can do is take an existing bridged config, drop NM_CONTROLLED=no from the ifcfg files, enable the NM service if necessary, and then see if NM takes over properly. It doesn't seem to be explicitly stated, but reading between the lines, the UI stuff isn't done yet.
I just tried this, and NetworkManager didn't bring up either the physical interface or the bridge. Here are ifcfg-eth0 and ifcfg-br0:
DEVICE=eth0 ONBOOT=yes TYPE=Ethernet IPV6INIT=no HWADDR=00:22:4d:4f:c7:ed BRIDGE=br0 #NM_CONTROLLED=no
IPADDR=172.31.250.1 GATEWAY=172.31.250.254 NETMASK=255.255.255.0 DEVICE=br0 ONBOOT=yes TYPE=Bridge IPV6INIT=no DELAY=0 #NM_CONTROLLED=no
Anyone have any ideas?
Not here. Might be worth poking Dan directly by email or on IRC (dcbw). He may be able to clarify.
Did anyone do this yet? If not, what is Dan's email adress? I'm trying this on F-17 and have the same experience -- it's simply not doing anything.
--Stijn
On 06/25/2012 02:56 AM, Stijn Hoop wrote:
Not here. Might be worth poking Dan directly by email or on IRC (dcbw). He may be able to clarify.
Did anyone do this yet? If not, what is Dan's email adress? I'm trying this on F-17 and have the same experience -- it's simply not doing anything.
rpm --changelog packagename | tail should tell you
Rahul
On 06/25/2012 06:55 AM, Rahul Sundaram wrote:
On 06/25/2012 02:56 AM, Stijn Hoop wrote:
Not here. Might be worth poking Dan directly by email or on IRC (dcbw). He may be able to clarify.
Did anyone do this yet? If not, what is Dan's email adress? I'm trying this on F-17 and have the same experience -- it's simply not doing anything.
rpm --changelog packagename | tail should tell you
Rahul
You mean:
rpm -q --changelog ...
Hello Dan,
as suggested on the fedora test list I am forwarding this to you: I and some others have been trying to activate the Fedora 17 NetworkManager bridge configuration, but it appears not to do anything at all with bridges.
Is there a bug somewhere or is the feature description not right?
http://fedoraproject.org/wiki/Features/NMEnterpriseNetworking
mentions bridges, but the docs for 0.9.4 do not mention bridges at all.
Regards,
--Stijn
On Mon, 25 Jun 2012 10:25:45 +0530 Rahul Sundaram metherid@gmail.com wrote:
On 06/25/2012 02:56 AM, Stijn Hoop wrote:
Not here. Might be worth poking Dan directly by email or on IRC (dcbw). He may be able to clarify.
Did anyone do this yet? If not, what is Dan's email adress? I'm trying this on F-17 and have the same experience -- it's simply not doing anything.
rpm --changelog packagename | tail should tell you
Rahul
-
Adam Williamson -
Dennis Jacobfeuerborn -
Ian Pilcher -
Joachim Backes -
Rahul Sundaram -
Stijn Hoop