[Bug 1643063] Re: unable to ifup vlan based interface with systemd persistent naming

2017-05-05 Thread Andrei Coada
*** This bug is a duplicate of bug 1628591 *** https://bugs.launchpad.net/bugs/1628591 Check out my alternative workaround from duplicate bug #1628591. In my opinion, it's cleaner. I haven't heard of vconfig to be deprecated. Anyway... it's funny how we must do workarounds for basic

[Bug 1643063] Re: unable to ifup vlan based interface with systemd persistent naming

2017-05-05 Thread Andrei Coada
*** This bug is a duplicate of bug 1628591 *** https://bugs.launchpad.net/bugs/1628591 ** This bug has been marked a duplicate of bug 1628591 ifup & ifdown don't work for vlan devices when raw device name is the new "enp" convention -- You received this bug notification because you are

[Bug 1643063] Re: unable to ifup vlan based interface with systemd persistent naming

2017-05-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ifupdown (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1643063 Title:

[Bug 1643063] Re: unable to ifup vlan based interface with systemd persistent naming

2016-11-18 Thread Kevin Otte
This may need to be filed against the vlan package as /etc/network/if-pre-up.d/vlan is owned by same. It was my understanding, however, that vconfig was deprecated in favor of 'ip link' as used in my workaround. -- You received this bug notification because you are a member of Ubuntu Bugs,