On Wed, 2012-06-13 at 14:39 -0400, Pavel Simerda wrote: > 2) the ifcfg way with connection name > > UUID=2e1906b1-92a4-4206-b2d3-eecfd07241e9 > TYPE=Ethernet > HWADDR=52:54:00:8e:93:da > BRIDGE=Bridge
TYPE=Bridge DEVICE=br0 > > 3) the ifcfg way with device name > > UUID=2e1906b1-92a4-4206-b2d3-eecfd07241e9 > TYPE=Ethernet > HWADDR=52:54:00:8e:93:da > BRIDGE=wan2 Type=Ethernet MASTER=br0 It's the very same syntax as when using initscripts. > The only interesting message in the debug is: > > NetworkManager[31436]: <warn> error monitoring device for netlink events: > error processing netlink message: Object busy > > Otherwise all configurations lead to just normal DHCP setup. The bridge is > setup properly and up but the slave device is > *not* added. > > A single working configuration example to start with would be fine. It > doesn't matter so much if > it's based on ifcfg or keyfile but it should not require any other action > then (1) creating and > editing configuration files and (2) starting NetworkManager. There is, see: src/settings/plugins/ifcfg-rh/tests/network-scripts/ifcfg-test-bridge-main src/settings/plugins/ifcfg-rh/tests/network-scripts/ifcfg-test-bridge-component _______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
