Search
384 results for “NetworkManager”
-
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/ -
@lkundrak
soooo then... why isn't there a #TurboVision frontend to #NetworkManager yet? 😈
@pascaldragon @whitequark -
@lkundrak
soooo then... why isn't there a #TurboVision frontend to #NetworkManager yet? 😈
@pascaldragon @whitequark -
@lkundrak
soooo then... why isn't there a #TurboVision frontend to #NetworkManager yet? 😈
@pascaldragon @whitequark -
@lkundrak
soooo then... why isn't there a #TurboVision frontend to #NetworkManager yet? 😈
@pascaldragon @whitequark -
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 -
Hmpf. Ich hätte gedacht, dass es leichter ist, einen #RaspberryPi ins #WLAN zu bekommen.
raspi-config macht gefühlt gar nix.
Der #NetworkManager fragt immer wieder nach dem Passwort, das er schon kennt und auch vorschlägt.
#wpa_supplicant scheint einerseits mit dem NetworkManager zusammenzuarbeiten, hat aber auch eigene Konfig.
Und der Kernel schmeisst teilweise Fehler, dass er schon auf unterster Ebene den RF-Channel nicht konfigurieren könne... zumindest lese ich das da raus. Google findet zu der Meldung auch nix hilfreiches. Dann hilft auch nur noch ein Reboot, ansonsten spammt er mir die Logs zu.
Die Doku im Netz geht wild durcheinander und ist meistens undatiert, so dass nicht immer sofort ersichtlich ist, auf welche Generation der Reinen Lehre™️ sie sich gerade bezieht.
Sieht so aus, als wenn ich mich erst einmal tiefer einlesen muss, wie all die Komponenten ineinandergreifen und welche zusammen und welche gegeneinander arbeiten. 😬
-
#Netplan 1.1.2 has been released (#Canonical / #Ubuntu / #YAML / #NetworkManager / #SystemdNetworkD / #NetworkConfiguration) https://netplan.io/
-
Ensimmäistä kertaa kaukojunassa varmaan noin viiteen vuoteen. VR:n wifi blokkaa aika tehokkaasti VPN-yhteydet. En ole nyt liikkeellä työasioissa, mutta vähän hankalaa olisi tehdä töitä täältä. Linux-käyttäjänä en suht nopeasti löytänyt tapaa kiertää asiaa NetworkManagerilla. Private Internet Accessin oma sovellus sallii liikenteen ohjaamisen kohdeportin 80 kautta, jolloin se pääsee blokista läpi.
#VR #juna #VPN #wifi #privateinternetaccess #linux #networkmanager
-
#Netplan 1.1 has been released (#Canonical / #Ubuntu / #YAML / #NetworkManager / #SystemdNetworkD / #NetworkConfiguration) https://netplan.io/
-
How To Configure Static IP Address In Linux And Unix #IP #ipaddress #Linux #Unix #CentOS7 #Freebsd12 #nmtui #NetworkManagerTUI #CLI
https://www.ostechnix.com/configure-static-ip-address-linux-unix/ -
Linux (systemd, NetworkManager): how to run a script on suspend before networking is shut down
How to reliably run a script that requires networking immediately before your computer suspends.
https://blog.kamens.us/2023/02/24/linux-systemd-networkmanager-how-to-run-a-script-on-suspend-before-networking-is-shut-down/
#Computers #FreeSoftware #Linux #NetworkManager #systemd #JikBlogFlashback -
CW: PSA: Disabling connectivity surveillance on GNU/Linux
We almost forgot the most important part!
After doing the above reset the NetworkManager with:
sudo systemctl restart NetworkManager
If you run your packet sniffer now (Wireshark/tcpdump) you shouldn't see anymore phoning home (from Connectivity Checks at least. Doesn't include DNS leaks, NTP, pings etc).
-
@dcz @malte I get so upset when I see issues closed automatically after inactivity, it makes my heart sink. At least it looks like they stopped doing this 10 months ago in this project, but without reopening the auto-closed issues… https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/?sort=created_date&state=closed&label_name%5B%5D=auto-closed&first_page_size=20
#stalebot #NetworkManager #FreeDesktop -
Oh man, what a hassle it is to predefine wifi connections on a new Linux install with NetworkManager. Used to be you could simply add 2 or 3 lines per connection to wpa_supplicant.conf but now every connection is a whole separate file with a UUID and nmtui doesn't even encode the passphrase so they need manual editing anyway.
-
Okay, can anyone tell me how to automatically enable and auto connect to wifi using #connman? From what I can find in google, everyone is really into doing it manually every time and likes randomized macs.
I do not think I belong here. Sure, I sometimes want to set #NetworkManager on fire, but it does understand I really do want to use wifi.
-
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
-
#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
-
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/ -
CW: old cat yells about packaging and cross-compiling
Feels like I got into shaving a whole herd of yaks when I just wanted to access NetworkManager over D-Bus from Python on a certain embedded system. :neocat_laugh_sweat:
* The only non-deprecated, non-systemd way to do that (short of handwriting a client library) seems to be python-gobject and introspection.
* The #Buildroot packages for python-gobject and gobject introspection are marked as glibc-only, but I'm using musl. And I know they work on Alpine just fine.
* The GLib, gobject-introspection, and python-object versions in Buildroot are very old. And Alpine actually dropped a musl-compatibility patch with the most recent gobject-introspection version. So… update time.
* The #GLib build process changed and now requires a bootstrap step to support introspection.
* Turns out… Bootstrap or not, introspection isn't supported when cross-compiling. :neocat_scream_stare:
We'll see where it goes from here, the gobject-introspection package in Buildroot does some wild things with Qemu to work around a similar limitation. And there are some somewhat recent changes related to cross-compiling upstream. :neocat_think: -
So, after I met problems with iwlwifi driver and my attempts to aggregate both em0 and wlan0 interfaces to the one lagg0 interface (https://mastodon.bsd.cafe/@evgandr/115985853500057386) — looks like I found a much (MUCH!) simpler solution :drgn_happy:
I wanted to automatically switch between wired and wireless networks when I plug-in (or disconnect) my Ethernet cable. First, because I was a newbie in the FreeBSD world, I tried to search for some kind of NetworkManager. Thankfully, I didn't find any NetworkManager clone ported to the FreeBSD. I found some tries to port NetworkManager from Linux to FreeBSD but all of them are failed (not surprised, lol).
Then, I finally started to read documentation :drgn_think_science: . In the section about advanced networking I read about aggregation interfaces. And somehow I managed to aggregate both of em0 and wlan0 to the one lagg0 interface and it works well.
But, looks like (see https://mstdn.social/@erikarn/115986265106931691) it is not the way how the lagg interfaces should work. It is not intended to use wireless interfaces in the aggregate interfaces — so my tricky setup stopped working in the FreeBSD 15.0.
BUT, since we have a beautiful devd daemon, which listens for various system events and able to execute actions when event is happened — I just wrote 23 lines of shell script to learn my laptop how to switch between interfaces when the Ethernet cable (dis)connects, lol. Solution is very simple:
First, we already have /etc/devd/dhclient.conf, which starts dhclient when some interface appeared in the system. I modified it, so it calls the sPeCiAL script, each time when em0, or wlan0, or ue0 interface appeared in the system, or when em0 is disappeared:
notify 0 {
match "system" "IFNET";
match "type" "LINK_UP";
media-type "ethernet";
action "/root/bin/unfuck_network.tcsh $subsystem ifup";
};notify 0 {
match "system" "IFNET";
match "type" "LINK_DOWN";
media-type "ethernet";
action "/root/bin/unfuck_network.tcsh $subsystem ifdown";
};notify 0 {
match "system" "IFNET";
match "type" "LINK_UP";
media-type "802.11";
action "/root/bin/unfuck_network.tcsh $subsystem";
};notify 0 {
match "system" "ETHERNET";
match "type" "IFATTACH";
match "subsystem" "ue0";
action "/root/bin/unfuck_network.tcsh ue0";
};Then, the main magic happens in the /root/bin/unfuck_network.tcsh:
— When Ethernet cable is connected — it destroys the wlan0 interface and starts dhclient for em0 to talk with DHCP server.
— When Ethernet cable is disconnected — it makes all to remove route using em0 from routing table (removes em0 interface completely, flush routing table, etc — somehow em0 still stays in the routing table if interface is not destroyed; btw system will create it anyway later, in some point) and recreates the wlan0 interface.
— When wlan0 device is created — it starts dhclient for it.Script contents (for tcsh):
#!/bin/tcshswitch ( $1 )
case "em0":
if ( $2 == "ifup" ) then
service netif quietstop wlan0
service dhclient quietstart em0
else if ( $2 == "ifdown" ) then
service dhclient quietstop em0
ifconfig em0 delete
route flush
service routing restart
service netif quietstart wlan0
endif
breaksw;
case "wlan0":
service dhclient quietstart wlan0
breaksw;
case "ue0":
service dhclient quietstart ue0
breaksw;
endsw -
I digged an old Thinkpad T410 out of my pile of Thinkpads and decided to take it to the arcade as a general use laptop for the days I don't have anything more modern on me and something needs tweaking.
This specific machine had only 6 gigs of RAM, so I tried something new here. Normally I do these light but up-to-date setups with Debian and XFCE or IceWM, but since I've put Alpine into quite a few Docker containers, I wanted to see how it fares as a full installation.
For someone who has used Linux in the days when X configuration was done by hand, setting it up wasn't that hard, but there was also plenty of manual tweaking to get this thing behave somewhat like a modern era laptop would. I put XFCE on it, changed the networking to run under NetworkManager and so forth. Been quite a while when I've set something up from as scratch as this, but it was also a nice walk down the memory lane.
Anyway, the Thinkpad works great, Wifi and all. The whole installation with all the junk I need takes 1.4 gigabytes of disk space and 480 megabytes of RAM with full DE running. Pretty!
Isn't this thing glorious? ThinkLight and all!
-
Hướng dẫn dùng Raspberry Pi làm Router gia đình.
SSH vào Pi, dùng NetworkManager để tạo Access Point qua Ethernet:
sudo nmcli connection add type wifi ifname wlan0 con-name ap0 ssid "<TÊN_WIFI>" autoconnect yes
sudo nmcli connection modify ap0 802-11-wireless.mode ap 802-11-wireless.band bg
sudo nmcli connection modify ap0 wifi-sec.key-mgmt wpa-psk wifi-sec.psk "<MẬT_KHẨU>"
sudo nmcli connection modify ap0 ipv4.method shared ipv4.addresses 172.18.0.1/24
sudo nmcli connection up ap0 -
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 😑
-
#TFW you reboot your #Linode, and apparently something has changed on the host because the network interface name reported by the kernel is now different, so NetworkManager fails to configure the network and you have to waste a half hour logging into the console over lish and relearning how the fuck manually configured network interfaces are configured in NetworkManager so you can figure out what's wrong and fix it. *sigh*
-
Either I am going crazy, or akonadi_imap_resource on Debian 13 requires NetworkManager to be running, and if it is not running it crashes with "invalid nullptr parameter".
Because you know, that kind of hard dependency would make perfect sense, right?
:blobcatfacepalm: