#networkmanager — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #networkmanager, aggregated by home.social.
-
After the last NetworkManager update, the use of aliases for the server no longer works #apache2 #networkmanager #postfix
-
After the last NetworkManager update, the use of aliases for the server no longer works #apache2 #networkmanager #postfix
-
After the last NetworkManager update, the use of aliases for the server no longer works #apache2 #networkmanager #postfix
-
After the last NetworkManager update, the use of aliases for the server no longer works #apache2 #networkmanager #postfix
-
After the last NetworkManager update, the use of aliases for the server no longer works #apache2 #networkmanager #postfix
-
Has anyone managed to get #Wireguard up and running with #NetworkManager on #Linux?
I had to switch backnto the Wireguard tools again, because although the connection is established, devices are not reachable.
In addition, the configuratiin is very cumbersome, as the wg0.conf file cannot simply be imported.
-
Why will no form of internet work? #networking #networkmanager #internet #cinnamon
-
How prevent a network from connecting to my laptop #networking #lubuntu #networkmanager
-
#Linux Weekly Roundup for February 15th, 2026: #Mesa 26.0, #Ubuntu 24.04.4 LTS, #KDE Frameworks 6.23, #GNOME 49.4, #pearOS 26.2, #IPFire DBL, #KaOS 2026.02, #NetworkManager 1.56, #GNU Linux-libre 6.19, #OpenVPN 2.7, #Parrot 7.1, #Tails 7.4.2, GNOME 50 beta, #REMnux 8, #MythTV 36.0, GNU Binutils 2.46, #Vim 9.2, #GitHub Tray, and more https://9to5linux.com/9to5linux-weekly-roundup-february-15th-2026
-
#Linux Weekly Roundup for February 15th, 2026: #Mesa 26.0, #Ubuntu 24.04.4 LTS, #KDE Frameworks 6.23, #GNOME 49.4, #pearOS 26.2, #IPFire DBL, #KaOS 2026.02, #NetworkManager 1.56, #GNU Linux-libre 6.19, #OpenVPN 2.7, #Parrot 7.1, #Tails 7.4.2, GNOME 50 beta, #REMnux 8, #MythTV 36.0, GNU Binutils 2.46, #Vim 9.2, #GitHub Tray, and more https://9to5linux.com/9to5linux-weekly-roundup-february-15th-2026
-
#Linux Weekly Roundup for February 15th, 2026: #Mesa 26.0, #Ubuntu 24.04.4 LTS, #KDE Frameworks 6.23, #GNOME 49.4, #pearOS 26.2, #IPFire DBL, #KaOS 2026.02, #NetworkManager 1.56, #GNU Linux-libre 6.19, #OpenVPN 2.7, #Parrot 7.1, #Tails 7.4.2, GNOME 50 beta, #REMnux 8, #MythTV 36.0, GNU Binutils 2.46, #Vim 9.2, #GitHub Tray, and more https://9to5linux.com/9to5linux-weekly-roundup-february-15th-2026
-
#Linux Weekly Roundup for February 15th, 2026: #Mesa 26.0, #Ubuntu 24.04.4 LTS, #KDE Frameworks 6.23, #GNOME 49.4, #pearOS 26.2, #IPFire DBL, #KaOS 2026.02, #NetworkManager 1.56, #GNU Linux-libre 6.19, #OpenVPN 2.7, #Parrot 7.1, #Tails 7.4.2, GNOME 50 beta, #REMnux 8, #MythTV 36.0, GNU Binutils 2.46, #Vim 9.2, #GitHub Tray, and more https://9to5linux.com/9to5linux-weekly-roundup-february-15th-2026
-
#Linux Weekly Roundup for February 15th, 2026: #Mesa 26.0, #Ubuntu 24.04.4 LTS, #KDE Frameworks 6.23, #GNOME 49.4, #pearOS 26.2, #IPFire DBL, #KaOS 2026.02, #NetworkManager 1.56, #GNU Linux-libre 6.19, #OpenVPN 2.7, #Parrot 7.1, #Tails 7.4.2, GNOME 50 beta, #REMnux 8, #MythTV 36.0, GNU Binutils 2.46, #Vim 9.2, #GitHub Tray, and more https://9to5linux.com/9to5linux-weekly-roundup-february-15th-2026
-
can anyone tell me how to teach my system that a user other than that one controlling the #wayland environment is allowed to control network connections via #networkmanager (nmcli console command, for VPN purposes)? This was possible under #debian12, but now it requires password confirmation from both(!) users 😕 #linux #debian
-
Essential nmcli Command Examples To Manage Network Connections On Linux #nmcli #NetworkManager #LinuxNetworking #Linuxadmin #linuxhowto #linuxbasics #linuxcommands #commandline
https://ostechnix.com/linux-nmcli-command-examples/ -
This guide walks you through every method for changing the IP address on Debian 12, providing clear, step-by-step instructions.
Keep reading:👇
https://greenwebpage.com/community/how-to-change-an-ip-address-on-debian-12/#ipaddress #nmcli #nmtui #networkmanager #dhcp #manaulipaddress #debian #linuxadministration #greenwebpage
-
After years of using #NetworkManager because I had no clue what a #wpa_supplicant or #iwd was, I finally switched to systemd-networkd. I don't dislike NetworkManager and I will miss the integration in GNOME Settings, but I just prefer systemd-resolved, which depends a bit on systemd-networkd for some #DNS functionality I want.
I also discovered #impala for configuring iwd. What a neat utility. And it's written in Rust, which automatically makes it even better.
-
CW: CW Blogpost
Too Good To #014
In today’s installment:
- #dmesg from before the machine crashed
- #Kill process ID from #pidfile
- Let #systemd retry a task
- Set #MTU on #OpenVPN connections in #Networkmanager -
Setup -> I have a #RaspberryPi #RaspberryPiZero2W running #linux #pios #RaspberryPiOS #headless
Aim: I want the pi to always offer a #hotspot #wifihotspot on #boot
based on the commandnmcli device wifi hotspot ssid pizerohotspot password my_password
Is this below a bad solution ?? -> I came up with this solution in the link below using a .service but fear it shows I am clueless? Is there a better way? Thanks!
https://www.loramesh.org/subpages/pi_install.html#pi_hotspot -
Das #VPN der #UniBonn gibt mittlerweile eine äußerst unhilfreiche 404-not-found Fehlermeldung zurück, wenn man sich unter #Linux (#openconnect cli oder #NetworkManager GUI) verbinden möchte.
Die Lösung ist (natürlich!) wie hier¹ im #ArchWiki erwähnt:
> sudo openconnect --useragent=AnyConnect unibn-vpn.uni-bonn.de
Also dem Gateway vorgaukeln, dass man der Cisco AnyConnect client ist 😑
-
#Netplan 1.1.2 has been released (#Canonical / #Ubuntu / #YAML / #NetworkManager / #SystemdNetworkD / #NetworkConfiguration) 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 -
If for some fucking reason your OpenVPN connection VPN decided it was cool to fuck up your day and not connect, this may be the culprit:
https://bbs.archlinux.org/viewtopic.php?id=295561
Basically, check your system logs if you need to add "data-ciphers" to your config, and restart the #NetworkManager after all changes are done.
#Linux #Troubleshooting #Network #VPN #OpenVPN #OVPN #Networking #Connection #Security #Technology
-
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/
-
It's always DNS, right? If someone experiencing some strange issues with ubuntu, maybe this toot is for you.
tl;dr: switch from systemd-resolved to resolvconf.
I thought, the saying from the beginning was just something from the "old days". No DNS Problems in 2024 anymore, right? But Ubuntu taught me different.
Ubuntu is using systemd-resolved since 20.04 (if I'm correct). But I was shocked, when I was looking at my uptime kuma Container on a Ubuntu 22.04 LTS Host. It was constantly failing. Sometimes 3 services at the same time, sometimes just 1 service a day. One Check suddenly failed. 60 seconds later, the next check, switched back to green again. But all fails had the same error message: "getaddrinfo ENOTFOUND domain.com". Doesn't matter if they were internal domains or external. Sometimes some of them just failed.
I thought it could be an old Firewall Applience that were running at like 120% system utilization and were serving DHCP and (with this) internal DNS. But no. Not even high latencies from that Firewall. Then I thought it might be AdGuard (in a Docker Container). So I switched to PiHole. But the problems were still the same.
Then I turned on debug logs of systemd-resolved and found out that sometimes it was switching to the secondary DNS Server for whatever reason and just attaching the search domain to the following requests:
1. AAAA of demodomain.com
--> no answer (because only A were available)
2. A of demodomain.com
--> somehow failed, systemd-resolved switched to second DNS (debug log of systemd-resolved is hard to read, not sure why it somehow failed)
3. AAAA of demodomain.com.local
--> it just attached the searchdomain of the system to the domain which now resulting in errors from all following DNS ServerAfter another round of wrong requests it suddenly get back his head. But in the meantime, uptime kuma already failed.
The solution in my case: switch "back" to resolvconf package on Ubuntu. Which comes to at least one downside: it seems to not have an interface to netplan and/or networkmanager (which leads to manual creating and managing of resolv.conf, not via DHCP, bummer). But after I switched: Everything is working fine and without any problems since days.
"We" also have an open bug report since 3 years: https://github.com/systemd/systemd/issues/21123
It's not exactly the same issue, but I think the root cause is connected somehow: it seems to be a problem of IPv6.
But a) I need (or better: want) IPv6 in my case/that network and b) WTF? How can this be a good solution to turn off IPv6 (https://github.com/systemd/systemd/issues/21123#issuecomment-2028976737)? Not to mention that we still need a solution for Post-IPv4.By the way: If you still experiencing DNS issues inside Docker Container, maybe Alpine could be another issue: https://martinheinz.dev/blog/92
#systemdresolved #ubuntu #Ubuntu2404 #uptimekuma #dns #usg #unifi #ubiquiti #adguard #pihole #netplan #networkmanager #ipv4 #ipv6 #alpine #docker #glibc #musl
-
How To Find WiFi Password Of Connected Networks In Linux #wifi #wireless #Wifresti #PasswordRecovery #NetworkManager #Networking #Python #Linux #commandline #LinuxCommands
https://www.ostechnix.com/find-wifi-password-of-connected-networks-in-linux/ -
Anybody knows how to get #NetworkManager to work with an #L2TP Fortinet #VPN ?
I installed the required packages, but if I "enable IPsec tunnel to L2TP host" it fails, and if I disable that, well, auth succeeds, and it sets up routes, but doesn't route anything. 🤔