Debian VM script and static networking setup

[Mvanmierlo]

I am having issues setting up my network interface in this VM as there is no /etc/network/interfaces file after the installation.
Leaving everything default and have the interface connected on a network with a DHCP server the ens18 interface shows up with a vallid DHCP IPV4 address.

But trying to set this up manualy by creating /etc/network/interfaces has no result what soever.
I tried several guides on setting up an interface manualy in Debian 12 but no luck.
IFUP / IFDOWN commands are not known / sysctl restart networking does not work etc etc. Feels like I am missing some essentials for setting up the debian networking properly in this VM, but I am clueless at this moment.

I did check the mentioned url #836 but this is far from up to date most commands do not work (try the setting up SSHD as an example the sshd-config file is also not pressent in the default script installation.

any help would be much appriciated.

[in the meantime I did a manual install of debian via the standard and latest net inst ISO and networking did show up as expected and works with the /etc/network/ interfaces file.
So I have no clue why the script building the VM version of debian 12 is deviating from the default net inst iso installation but I hope someone can clearify this as I am still a big fan of the proxmox scripts from this project.]

[michelroegl-brunner]

It is literaly right there under Added 2025-02-25 - Debian Cloud Networking

[Mvanmierlo]

What has Cloud networking to do with the basic network setup of a virtual Debian server in my home lab ?
I am puzzled
Has Debian / Linux AGAIN changed the default network tools / way of setup (I am an old ifconfig nerd so please be gentle with me :-)

[Mvanmierlo]

@michelroegl-brunner you closed the question so you see this as answered, but I did not get a proper answer as clearly mentioned.

As mentioned I do appreciate the scripts, but I expect them to do a default (non custom) install of an OS, as edited in my initial question I also did a manual VM installation of Debian, this resulted in a different OS / Network config than the script so I can only conclude that the script is deviating from the default install behaviour.
I am curious / willing to learn why, so hope you can give me a pointer in the right direction.

Much appreciated.

[tremor021]

Hi, i'll expand on @michelroegl-brunner answer. The image thats used for debian VM is a cloud image. Debian cloud images use netplan to manage the network configuration, hence why additional configuration guide is added to the discussion here:

#836

You are pointed at that discussion on the script webpage:

[Mvanmierlo]

. The image thats used for debian VM is a cloud image.

Not trying to be a smart ass here nor to be blunt but this is not mentioned anywhere on the webpage one visits to find the script, and the pointer to the 836 discussion is also not realy vocal / clear about this if one is not hard core debian fan.
Which I am obviously not.
If this was more prevalent on the script page / description it would have pointed me in the right direction right the way (saving you guys some time :-) )

Thanks for pointing this out, makes the script (too bad as I am a fan) useless for my environment as I do not care for this cloud way of working (yet) in my home lab, and I prefer the default networking setup which is documented the most in my google finds / I am used to on my physical machines.

Thanks for your time !

[tremor021]

I mean, there are literaly 2 informations on the webpage.

First is description of the VM you're about to install
Second is telling you to go check out the discussion after the installation finishes...

I'm not really sure what else we can do... Seems we really can't force people to read two sentences on a page, obviously

Also, netplan is documented the same way as every other network manager out there. Nothing is forcing you to use it. Install your own network manager and use it:
apt-get install network-manager for example