pve-common/test/etc_network_interfaces/base-auto-allow-hotplug

# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

auto ens18
allow-hotplug ens18
iface ens18 inet dhcp
inotify: network: improve "allow-hotplug" & "auto" interaction commit c86cfb8bbd9b505d06b580582297fa670561437b dropped allow-hotplug from the primary interfaces file completely on write, but that breaks setups that come from plain Debian. Instead, as stop-gap measurement, transform "allow-hotplug" to auto in the PVE controlled config. That avoids conflict and improves installing PVE on top of plain Debian, as the interface still comes up after the first reboot. But it is not ideal auto is not the same as hotplug, so we need to also track that difference in the future, but that needs some adaptions in the API too (change autostart from boolean to string+enum or so= Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> 2021-09-24 13:29:46 +03:00			`# network interface settings; autogenerated`
			`# Please do NOT modify this file directly, unless you know what`
			`# you're doing.`
			`#`
			`# If you want to manage parts of the network configuration manually,`
			`# please utilize the 'source' or 'source-directory' directives to do`
			`# so.`
			`# PVE will preserve these directives, but will NOT read its network`
			`# configuration from sourced files, so do not attempt to move any of`
			`# the PVE managed interfaces into external files!`

			`auto lo`
			`iface lo inet loopback`

			`auto ens18`
			`allow-hotplug ens18`
			`iface ens18 inet dhcp`