Re: [PATCH 0/6] Bridging support v2
- From: Pavel Simerda <psimerda redhat com>
- To: Thomas Graf <tgraf redhat com>
- Cc: networkmanager-list gnome org
- Subject: Re: [PATCH 0/6] Bridging support v2
- Date: Thu, 14 Jun 2012 08:27:58 -0400 (EDT)
> My setup is as follows:
>
> ---- ifcfg-br0
> NAME="Bridge"
> NM_CONTROLLED="yes"
> DEVICE="br0"
> TYPE="Bridge"
> ONBOOT="no"
> IPADDR0=10.1.0.1
> PREFIX0=24
> BOOTPROTO=none
> ----
>
> ---- ifcfg-eth1
> HWADDR="52:54:00:c8:5c:a0"
> NAME="Slave"
> UUID="5dfee073-aaa7-4fcb-a27c-c85687ff2b39"
> NM_CONTROLLED="yes"
> DEVICE="eth1"
> TYPE="Ethernet"
> BRIDGE="br0"
> ONBOOT="no"
> ----
>
> $ nmcli con up id Bridge
> $ nmcli con status
> NAME UUID
> DEVICES DEFAULT VPN
> MASTER-PATH
> Bridge d2d68553-f97e-7549-7a26-b34a26f29318 br0
> no no not set
> Slave 5dfee073-aaa7-4fcb-a27c-c85687ff2b39 eth1
> no no /org/freedesktop/NetworkManager/Devices/3
> System eth0 ce6029d3-4d48-4d20-b10c-baab44318fee eth0
> yes no not set
> $ brctl show
> bridge name bridge id STP enabled interfaces
> br0 8000.525400c85ca0 no eth1
Thanks. It might be worth fixing the bridge support to also work with default ONBOOT="yes".
I don't think we can require users to manually start these two connections.
> Not sure what that means, the files are right there in the git tree.
I'm sorry. I meant that the settings don't work well with NM startup. Setting
ONBOOT=no is a good second test but I believe that number one is the “just works”
scenario with onboot left enabled.
> > > src/settings/plugins/ifcfg-rh/tests/network-scripts/ifcfg-test-bridge-main
> > > src/settings/plugins/ifcfg-rh/tests/network-scripts/ifcfg-test-bridge-component
> >
> > That one says BRIDGE, not MASTER:
>
> Right, it's BRIDGE= not MASTER=. My mistake.
Thanks for confirmation.
Cheers,
Pavel
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]