I had/have sort of the same problem, when running the network startup it somehow wants to set up my vlans twice; i think when i do the 'master' interface, and once when it sets up the normal interface.
The first time it just sets up the vlan and assigns an address. The second time it tries to add that address again, but that obviously fails with an 'RTNETLINK answers: File exists' And because the default (since 2014?) is to treat any error as fatal it just stops configuring the interface even tho it would be perfectly ok to at least try to set, for example, the default route or the 'up' statements. But no, a small step failed so it's better to leave the interface half configured. On Ubuntu 16.04 this can be worked around by adding "EXCLUDE_INTERFACES=' --ignore-errors' " to /etc/default/networking so ifupdown does the sensible thing and tries to continue after an error instead of leaving a half configured interface. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565804 Title: ifup of vlan interfaces failing during networking start - RTNETLINK answers: File exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1565804/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
