[11:53] <pmjdebruijn> interface aliases still aren't supported?
[11:54] <pmjdebruijn> also https://netplan.io/examples/ the 'lo' example seems to replace the 127.0.0.1/8 IP, as opposed to merely adding an ew ip
[11:57] <slyon> pmjdebruijn: netplan supports ip addr labels, does that work for your interface alias use case? https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1743200
[12:02] <pmjdebruijn> slyon: is there any proper documentation?
[12:03] <slyon> pmjdebruijn: it's described in netplan's reference, which also contains a small example: https://netplan.io/reference/#common-properties-for-all-device-types
[12:04] <pmjdebruijn> yeah found that in the meanwhile
[12:05] <pmjdebruijn> it seems this breaks ifconfig entirely
[12:06] <pmjdebruijn> and doesn't result in a seperate interface
[12:11] <pmjdebruijn> so it's marginally worse than before
[12:13] <pmjdebruijn> slyon: essentially we'd like to add additional IPs to 'lo' but OTOH not mess with 'lo' itself, so we can be sure to never break it
[12:17] <slyon> pmjdebruijn: hmm.. what OS are you running that you need to use legacy ifconfig instead of iproute2?
[12:19] <slyon> netplan set network.ethernets.lo.addresses='["127.0.0.1/8", "::1/128", "1.1.1.1/24", "2.2.2.2/24"]' doesn't work for you?
[12:19] <pmjdebruijn> I don't "need" anything, it's a matter of convenience
[12:21] <pmjdebruijn> slyon: it seems to work now, it's more than netplan has had more than it's fair share of bugs, so having it mess with the main lo, isn't something i'm looking forward to
[12:21] <pmjdebruijn> aside from the documentation about 'lo' being a bit misleading
[12:22] <slyon> I'm glad it's working now, and I agree that the 'lo' documentation needs to be updated
[12:23] <pmjdebruijn> it's misleading in way, that would badly break a pre-existing install, so removing that would better than leaving it in place like this
[12:35] <slyon> pmjdebruijn: I guess this should help, right? https://github.com/canonical-web-and-design/netplan.io/pull/225
[12:41] <pmjdebruijn> yeah I think so