Okay, really scary systemd-networkd moment: I replaced a lot of the #networkd config files on my server with new ones, that create bonds, bridges, etc and even move the IP address I am connected to from one of the interfaces to a bridge and move the interface onto the bridge.
I prepared the OOB connection and entered `networkctl reload` with the expectation that I will break my config.
And 2 seconds later my prompt appeared again on my SSH session. I love it when stuff magically just works.đ
De nou online! Després de superar un tall de llum de 5 hores per intentar arreglar ves a a saber que els de la companyia de la llum... i substituir #NetworkManager per #systemd #networkd
@alexhaydock my intent is to educate myself about CLAT and solicit more input on how reasonable is it to do the translation with a bpf program within NM? What are your (anybody reading this) thoughts on it?
What about those using #systemd-#networkd or #connman? How does this compare to doing CLAT within userspace (via tunnel interface) or the kernel? Does CLAT really matter in GNU/Linux where the userspace is generally in better shape than Mac/Windows and we can just rebuild it?
[2/2]
Seems this is a bug in systemd-networkd unfortunately. So for now I just have to run dhclient after every suspend. https://bbs.archlinux.org/viewtopic.php?pid=2221138
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.
systemd-networkd-wait-online.service always takes about a minute to finish.
I hope that adding the renderer line to my netplan config fixes this - i'll see, next time i reboot the box.
#NixOS abstractions are nice, but it sucks when the networkd config option you need isn't yet supported, and you can't just edit the netdev config file either because it's a read-only FS... https://github.com/NixOS/nixpkgs/pull/261726 #networkd #vlan
Apparently
1) There's a race condition between #tibyvmm and #networkd that prevents VMs from getting a DHCP reply fast enough (I'm so moving off networkd now)
and
2) cilium clustermesh is just fragile as fuck and requires manual rubbing in proper order for the clusters to regain peering.
The technology is scary.
Et routeur #Debian configurĂ© pour utiliser la #Freebox en mode bridge avec DHCPv4 + dĂ©lĂ©gation de prĂ©fixes #IPv6, cela fonctionne parfaitement â€ïž
(avec #systemd-#networkd et #iptables)
Fini la tannée du setup custom pour pouvoir se passer de la #Livebox #Orange, avec en plus des IP fixes.
Je gagne aussi en débit, mais ça n'était pas l'objectif.
Bref, content ! đ
#networkd is so much fun. The default ubuntu setup (networkd based) wonât play nice with networkdâs own dhcp server.
Wrote some more details on my #networkd issues with #tinyvmm today: https://farcaller.net/the-woes-of-networkd/
Weird issues with #dns lately, not sure its only affecting my #opensuse #tumbleweed, but after digging the forums for a while, I really lost some trust in Opensuse after reading all the issues related to #wicked. Seems I need check how #networkd works and switch to it.
As part of my blog resurrection, just posted a new short note on how to setup a #wireguard #vpn server using #systemd #networkd.
https://kalnytskyi.com/posts/setup-wireguard-systemd-networkd/
