Es momento para lanzar un testlab 🤠 con la rc1 #debiantrixie #netplan #podman #wireguard
#netplan
Dual Interface "Jumpbox" Can't Reach Internet Using netplan #networking #netplan #ip #routing
Why is bond0 not being created? #netplan #networkbonding
Wi-Fi issues on Ubuntu 22 using netplan #networking #wireless #netplan #systemdnetworkd
systemd-networkd-wait-online waiting for ethernet that is not there #networking #2404 #netplan #systemdnetworkd
Just replaced my 18-year old gateway/router/firewall computer (homebuilt Athlon-based). It has been reliably up 24/7 all this time. Sorry to tear it down, but the new machine is better in every way.
The switch included a change in the boot configuration from using network/interfaces and ifupdown to using #netplan and #systemd.
Next: installing #PiHole and #Nextcloud on the new machine.
@ubuntuasahi #netplan was the answer. It doesn't do anything by default. Added config to request DHCPv4 on #ens0 (network interface). And then it immediately got an IP address after running `netplan apply`. Case solved
Yes, that was the obvious solution. Glad I don't have to type all that in myself, but rather that #Hashicorp #Packer does that for me.
(I have to configure the network to set "dhcp-identifier: mac" in Netplan, *before* the autoinstall file is downloaded; to mimic what happens when I install NetworkManager in the generated VM, otherwise it switched IP addresses after reboot, and Packer fails to log in over SSH).
Definitely did not waste most of today figuring this out...
Oof, that sounded much scarier than it turned out - could've been a 30 bucks brick!
It's fine, i've already rebooted the box. I'm not exactly sure about the improvements, though.
My MCX311A-XCAT always had all Fs in the GUIDs - shouldn't those be "Globally Uniquely IDentifying"?
While i'm figuring out how to utilise the #SRIOV capability, it'll be a member of br0.
…it couldn't be a simple "virtual-function-count" in my #Netplan yaml, could it? (anyone?)
Finalement, réussis à monter un routeur Linux maison en suivant 342748234 guides sous #ubuntu avec #netplan #hostapd #nftables (2 cartes wifi pour avoir les deux fréquences), 2 ports Ethernet. J'aimerais écrire une documentation, mais je devrais tout flusher et recommencer pour voir si je suis capable de le refaire. Bien souvent, j'ai eu à deviner des choses, car je ne trouvais pas de solution sur les internets. Pourquoi je suis si masochiste ? 🤣
#Netplan 1.1.2 has been released (#Canonical / #Ubuntu / #YAML / #NetworkManager / #SystemdNetworkD / #NetworkConfiguration) https://netplan.io/
I just hope the rest of the road is smoother. Fighting for a while with configuration is pretty darn discouraging and exhausting.
I think I was spoiled with #networkd and #netplan (with networkd backend) for the most part working just the way I like, even though netplan is missing some things I need.
My new Debian install has had weird hangs during routine package installs. All I/O will hang for a minute, then recover - can't open a new SSH connection, can't do any file I/O on existing ones. Nothing in the logs. Very hard to debug.
Turns out even a "systemd daemon-reload" triggers it, or more to the point, "netplan try". It's a bug in netplan, now fixed upstream (after 8 months), but not in Debian stable. https://bugs.launchpad.net/netplan/+bug/1999178
I'm afraid I've never seen the point of #netplan. It's not difficult to configure systemd-networkd, so why do I need a wrapper for that? #systemd
I'm configuring #KVM on my #Linux laptop this morning and I came across #netplan. It's a tool to easily configure, networks on Linux. Very useful if you need to configure bridge devices on #Ubuntu. #networking https://netplan.io
802.1x on #Debian or #Ubuntu anybody? Manually running wpa_supplicant with password=hash:something and dhclient works for me, but it did not work adding this to /etc/network/interfaces. I always end up in default VLAN using this method.
Will one of the other methods (#systemd-networkd, #NetworkManager or #netplan support hashed passwords?)
I am just looking for a method that works.
#8021x
today i learned that when #systemd gets restarted on my headless ubuntu 24.04 server, as it did with a recent update, this apparently also restarts systemd-networkd, and that kills ethernet connectivity until a reboot. since it's headless and doesn't currently have any other management options, that's never fun.
i saw that systemd-networkd was integrated with #netplan. i tried bypassing netplan and using a systemd-networkd configuration alone - which was an interesting challenge - but still, every time systemd-networkd restarts, networking is donezo. so i also tried switching to #networkmanager and ditching systemd-networkd, but then, somehow boot is delayed significantly and udisks2 fails to start (...why?!).
i have had to resort to setting up the watchdog package to reboot when network activity stops or pings fail. i don't like it, but i don't know what else to do in this distro.
also, kudos to anyone who can manage to use the term "systemd-networkd" in a post more than i did here.
#Netplan 1.1 has been released (#Canonical / #Ubuntu / #YAML / #NetworkManager / #SystemdNetworkD / #NetworkConfiguration) https://netplan.io/
How to Switch Back to /etc/network/interfaces From #Netplan
https://www.tecmint.com/switch-from-netplan-to-interfaces-ubuntu/
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst