After some further investigation, I have found that the workaround is unnecessary if I add the secondary IP address with either global or host scope. I still think it's a bug in NetworkManager as I don't think it's the correct or intended behaviour. The first IP address given to an interface is the one that's supposed to be bound to by default, and it shouldn't matter whether additional addresses have host, link or global scope.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1503881 Title: Latest Vivid update causes problems in interfaces with multiple IP addresses To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1503881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
