On 16.07.24 11:24, Stephan Seitz wrote:
Am Di, Jul 16, 2024 at 10:54:47 +0200 schrieb Lukas Märdian:
* Netplan PLUS NetworkManager(desktop/laptop)
All my desktops have only LAN and are working very well with ifupdown since the
beginning.
My Laptops are mostly in a LAN either. So NM is onlay needed for the rare cases
I’m in a WLAN.
Today, if you install a desktop environment that comes with NetworkManager,
debian-installer will
already opt to configure N-M for you (instead of /etc/network/interfaces).
ifupdown is still
installed and can be used, as you apparently do.
With Netplan+sd-networkd (+wpa_supplicant) you would even gain another minimal
option that supports
the rare WLAN cases. But it sounds like you prefer using ifupdown, which is
totally fine, see below.
* Netplan PLUS wpa_supplicant (server/embedded, using sd-networkd on WiFi)
None of my servers are using WLAN. They all work very well with ifupdown
including bonding/vlans.
This might not be your usecase, but I regularly see setups of "embedded
boards", like Raspberry Pi,
that use a server image but have the WiFi adapter as their primary network
interface.
The only times I didn’t get a working network with ifupdown are a) missing
firmware and b) the installer doesn’t support VLAN/Bonding.
And I don’t think Netplan will help here.
Netplan supports VLAN & Bonding, but debian-installer deliberately writes a
very basic configuration
only (DHCP or static IP), leaving more advanced setups to the sysadmin, AFAIK.
Maybe this is something
to be discussed with the d-i team?
Using Debian should NOT feel like using different distros. We want
Sorry, I call this bullshit. I’m using Debian exactly because it feels
different like other distros. There wouldn’t be a need for Debian if not.
As Colin stated, what I said is that Debian should have a congruent networking
story in itself,
independent of the context you're using it in (desktop, server, cloud, etc.).
I'm sorry if that wasn't clear.
ifupdown *is* one of the reasons I’m using Debian. I’m not interested in
editing yaml files to configure the network.
Using ifupdown is totally fine! I'm not suggesting for it to go away. I even
think it should continue
to be part of the default installation (in Trixie at least), for backwards
compatibility and to give
sysadmins a choice of when and if they want to transition to new tooling. Given
the maintenance burden
discussed in other parts of this thread, it remains to be decided if this
should be handled by
ifupdown-ng or ifupdown itself. But the current maintainers (Santiago, Daniel,
...) are probably in the
best position to decide about such combined "ifupdown*" efforts.
People that prefer using ifupdown could then just not touch /etc/netplan, or even
"rm /etc/netplan/*.yaml"
and continue using /etc/network/interfaces as usual.
-- Lukas
