Hi Sven On Thu, Jun 27, 2019 at 02:38:53PM +0200, Sven Bartscher wrote: > The specified network-config doesn't seem to have any actual effect on > what actually happens when the system boots. From what I see, > cloud-init generates a configuration file from my specified > configuration in /etc/network/interfaces.d/50-cloud-init.cfg with the > following contents:
Thanks for bringing this up. However I have bad news: this can not work with ifupdown. Reasons: - cloud-init write the config file using a name that is ignored by ifupdown. The filename is "50-cloud-init.cfg" and everything with "-" or "_" in it is ignored. (wtf?) - ifupdown can't handle duplicated network definitions. It will try to setup both static ips and use dhcp, and fail. The first could be fixed pretty easily. However the second can not really without reinventing everything. Regards, Bastian -- Youth doesn't excuse everything. -- Dr. Janice Lester (in Kirk's body), "Turnabout Intruder", stardate 5928.5.