On Thursday, 7 April 2016, James Hogarth james.hogarth@gmail.com wrote:
On 6 April 2016 at 19:21, Subscriber <ml-lists@agoris.net.ua javascript:;> wrote:
Hello James,
Wednesday, April 6, 2016, 5:34:26 PM, you wrote:
Note that this is pretty much the last use case you cannot use NetworkManager for but need the legacy network service ... to save you
some
pain in trying to configure it ;)
I disagree... NetworkManager works perfectly.
Ah I recall slightly incorrectly form my testing last May ... to be fair it's been nearly a year since I last looked at this ;)
https://www.hogarthuk.com/?q=node/8
it's nmcli specifically that wouldn't work as the bridge slave had an ethernet type requirement so wouldn't work if the type was bond or vlan
NM was able to create the connection from the file configuration however .... my apologies
Here's the bug with the limitation due to be fixed in the upcoming 7.3
https://bugzilla.redhat.com/show_bug.cgi?id=1183420
That's one less reason to use the legacy network service then! _____________________
I tried last night and it seems like the vlans that I created is failing to bring-up. So this is what Im doing
in my DATA trunk port at my HomeLab Im doing this
2 port configured for teaming1 (set as link only port) -> Create Bridge (br0 port) on top of the teaming1 -> create slave vlan10,20,30,40 and the parent is br0. Am I doing this correctly? Thanks