Comment 7 for bug 1846992

On Tue, 8 Oct 2019 at 11:30, Dimitri John Ledkov <email address hidden>
wrote:

> I'm not sure cloud-init's default behavior for networking will help here
> at all.
>

All I know is that cloud-init does have code for inspecting the
/run/net-*.conf files and has some kind of default behaviour for doing
dhcp. I don't know if all the pieces interact together nicely (e.g. if
there is a net-*.conf file that indicates networking, does it not do the
dhcp by default?).

To be clear, when I say "use cloud-init's default behavior" I mean removing
the netplan we currently have in the filesystem.squashfs (and having
cloud-init run in the live environment).

> At the moment I need networking up in the initrd, and for it to persist.
> Or do you mean I should look into cloud-utils-initramfs to make a baby
> again with casper?!
>

No, that's not what I meant.

> To me, it seemed like if there are two interfaces, and both manage to
> dhcp, there is no way in subiquity to pick which one should own the
> default route. Cause obviously one interface is DMZ and doesn't give
> internets, and the other one is the one that gives you internets.
>

 It seems to me that if the tiny DMZ does not give access to anything
useful, it's DHCP server should not be handing out a default route. In any
case, there is no "the default route", there can be a bunch of entries in
the routing table that take any address and the one that gets picked comes
down to route metrics. I have no idea which thing makes the call of which
of these two routes has the higher metric -- but I'm sure it's not
subiquity :)