Search
384 results for “NetworkManager”
-
Ozen.fm appoints Bruno Pinheiro as Network Manager in Latin America
São Paulo, April 2026 — Ozen.fm, a global platform dedicated to the curation and distribution of podcasts and…
#Conflict #Conflicts #War #agency #Latinamerica #NetworkManager #Ozen.fm #people
https://www.europesays.com/2919224/ -
Did a fresh install of #AlpineLinux. Switched to Edge to have an updated #Plasma desktop, and everything was great. So I set up #NetworkManager because wpa_supplicant makes me want to punch kittens whenever I have to use something other than my home network. Which worked great.
Start my laptop this morning, though, and it won't get pas starting the display manager during boot.
*sigh*
So… now I get to manually fix some config files or something I guess. Shoulda gone with #XFCE…
(Before anyone jumps on me, I obviously fucked up something in the configuration, this isn't #KDE's fault, and I 100% own that this is my fault. As usual, the Owlbear should not be taken seriously.) #Linux
-
Did a fresh install of #AlpineLinux. Switched to Edge to have an updated #Plasma desktop, and everything was great. So I set up #NetworkManager because wpa_supplicant makes me want to punch kittens whenever I have to use something other than my home network. Which worked great.
Start my laptop this morning, though, and it won't get pas starting the display manager during boot.
*sigh*
So… now I get to manually fix some config files or something I guess. Shoulda gone with #XFCE…
(Before anyone jumps on me, I obviously fucked up something in the configuration, this isn't #KDE's fault, and I 100% own that this is my fault. As usual, the Owlbear should not be taken seriously.) #Linux
-
Did a fresh install of #AlpineLinux. Switched to Edge to have an updated #Plasma desktop, and everything was great. So I set up #NetworkManager because wpa_supplicant makes me want to punch kittens whenever I have to use something other than my home network. Which worked great.
Start my laptop this morning, though, and it won't get pas starting the display manager during boot.
*sigh*
So… now I get to manually fix some config files or something I guess. Shoulda gone with #XFCE…
(Before anyone jumps on me, I obviously fucked up something in the configuration, this isn't #KDE's fault, and I 100% own that this is my fault. As usual, the Owlbear should not be taken seriously.) #Linux
-
There is finally a merge request to use QtKeyChain in plasma-nm 🥳 🎉
https://invent.kde.org/plasma/plasma-nm/-/merge_requests/551
-
There is finally a merge request to use QtKeyChain in plasma-nm 🥳 🎉
https://invent.kde.org/plasma/plasma-nm/-/merge_requests/551
-
There is finally a merge request to use QtKeyChain in plasma-nm 🥳 🎉
https://invent.kde.org/plasma/plasma-nm/-/merge_requests/551
-
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:
-
After every reboot/suspent, I'm automatically connected to one of my wireguard connections. Is there something to prevent this?
-
I am so happy with my #Linux Mint. but others have #Fedora in my fam &they run into issues (like #NetworkManager crashing - yes it starts, but then it crashes) so I figured I'd start a fresh Instance but for whatever reason, I cannot get the system (*I* INSTALLED via USB a few months back) to boot into the USB 😭 . I feel so dumb.. I have adhd, I have done almost a dozen setups now & everything is different with every device😭 - I know it is a skill issue, but it is exhausting & steals my courage
-
Sysadmin journal: setting up wireguard on all of my Linux desktops
I had to hack together a few things to use wireguard transparently on my Android phone and all of my Linux laptops and desktop.
#ddclient #Linux #NetworkManager #VPN #wireguard #Ansible #SysAdmin
https://blog.kamens.us/2025/05/10/sysadmin-journal-setting-up-wireguard-on-all-of-my-linux-desktops/ -
Sysadmin journal: setting up wireguard on all of my Linux desktops
I have several mostly interchangeable Linux computers for personal use. All but one are laptops; the mini-tower which isn’t is used as both a desktop and my home network server, e.g., for DNS and for SSHing into the home network from the outside when I’m traveling with one of the laptops.
A pro-democracy activist group that I’m part of has asked everyone in the group to use a VPN whenever accessing group stuff online (including Signal, Matrix, Proton, etc.) and has recommended using a VPN all the time. I am not convinced this is worth the effort, but it probably can’t hurt, and I don’t want to be the Guy Who Wasn’t Following The Rules if something does end up going down, so today I set out to make this happen.
I signed up for a VPN service that uses wireguard (no, I’m not going to tell you which one, that would be giving away information unnecessarily) and set out to figure out how to set up this VPN to be active all the time on my phone and all of my Linux computers. Below are my notes about the bumps in the road I hit while figuring this out and how I got over them.
The VPN service I signed up with has a bespoke Android client so setting it up for Android was trivial.
The service allowed me to add other devices to my account and download a standard-format wireguard configuration file for each, to be imported into wireguard, which I was able to do easily in NetworkManager on Debian after installing the wireguard package (I’m actually not 100% certain that it was necessary to import the wireguard package, I think it may have worked even if I hadn’t done that):
- Open Settings app
- Click on Network
- Click the + symbol next to VPN
- Click Import from file…
- Select the wireguard configuration file I downloaded from the VPN service
I wanted to configure the VPN to connect automatically. You can’t do that from the Settings app but you can do it from
nm-connection-editorornmcli. In the connection editor:- Open
nm-connection-editor, a.k.a., the “Advanced Network Configuration” desktop app - Double-click on the imported VPN
- Click on the General tab
- Check the “Connect automatically with priority” checkbox
- Save and exit
In
nmcli, you can do “nmcli connection modify [connection-name] connection.autoconnect yes“.I configure all my Linux machines via Ansible, so I wanted to figure out how to do the wireguard VPN configuration automatically using the
nmcliAnsible module, i.e., I wanted to do the import as described above manually the first time and then figure out how to replicate in Ansible code what the manual import did so I wouldn’t have to do it manually in the future. Unfortunately, though the documentation claims this should be possible, for some reason I don’t have the ability to specifywireguard.peersto the module, so I can’t do the configuration automatically. Therefore, I set up an Ansible rule that checks if the VPN is configured and fails if it isn’t, so that I am reminded to configure it manually if/when I’m setting up a new computer:- name: make sure wireguard VPN is configured and autoconnect is on nmcli: conn_name: "{{wireguard['vpn_name']}}" autoconnect: yes state: present register: nmcli check_mode: true failed_when: nmcli.changed or 'Exists' not in nmcliNext, I had to deal with the fact that when I enabled the VPN on my desktop, my
ddclientconfiguration stopped getting my correct public IP address and instead started putting the egress IP of my VPN into my dynamic DNS entry. The reason for this is obvious. I toldddclienttouse=web, web=http://checkip.dyndns.com/, and that is obviously going to go through the VPN and get the VPN’s IP rather than mine. I don’t know if the fix I came up with is the best one, but it works:use=cmd, cmd='curl --silent --interface enp2s0 http://checkip.dyndns.com/ | perl -ne \'chomp; if (s/.\b([1-9][0-9]\.[1-9][0-9]\.[1-9][0-9]\.[1-9][0-9])\b./$1/){print;exit}\''Next problem: I need to be able to log into my home desktop from outside the house. Solution: add routing policy rules on my home desktop so that traffic to/from our family server in the cloud bypasses the VPN, so that I can SSH into the cloud server from anywhere and then SSH into the home desktop from the cloud server. I deployed a script to
/etc/NetworkManager/dispatcher.dto add the routing rules when the VPN comes up and remove them when it comes down. The commands the script runs look like this:ip -4 rule add from [server IP] table mainip -4 rule add to [server IP] table main
It specifies “del” instead of “add” to remove the rules. I figured this out with the help of this Reddit posting. Note that this needs to be a dispatcher script because NetworkManager ignores
PostUpandPreDownlines in wireguard configuration files when importing them, and as far as I can tell there is no way to configure directly in NetworkManager commands to be run when an interface goes up or down.Final challenge: when I am working on one of my laptops and I need to SSH into my desktop, I want to do so directly via the private IP address on the home network when I’m at home, or indirectly through my cloud server when I’m out of the house, and I want this to happen automatically. Fortunately, I already had a NetworkManager dispatcher script which automatically generates ah SSH configuration file that’s included by my main SSH configuration. The old purpose of this script was so that when I’m out of the house with laptop A and I want to SSH into laptop B, which is on my home network but not accessible from the outside, that SSH automatically gets proxied through my desktop, which is accessible from the outside. I was able to augment this script to add the new functionality. Now whenever one of my laptops connects to my home network, the script adds to my SSH config a
Hostsection for the desktop with aHostNameline in it specifying the internal domain host name which resolves to its internal IP address, whereas when the laptop connects to a network outside my home, instead of theHostNameline it adds aProxyJumpline specifying the host name of my cloud server.If you’re one of the two people in the world who read this blog posting all the way to the end, drop a comment and let me know. 😉
#Ansible #ddclient #Linux #NetworkManager #sysadmin #VPN #wireguard
-
#Linux Weekly Roundup for March 2nd, 2025: #NVIDIA 570 graphics driver hits stable, #NetworkManager 1.52 addsIPvlan interface support, #Armbian 25.2 ships Linux kernel 6.12 LTS, #FrameworkDesktop, #FrameworkLaptop 12, #LibreOffice 25.2.1 fixes 77 bugs, #KDE Plasma 6.3.2, #LinuxMint's revamped #Cinnamon app menu, and more https://9to5linux.com/9to5linux-weekly-roundup-march-2nd-2025
-
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. 😬
-
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. 😬
-
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. 😬
-
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. 😬
-
💡Display the active WiFi connection using the following command in Linux #ZikTIPs #CLI #WiFi #Linux #Opensource
@NetworkManager @opensuse @fedora @debiannmcli connection show --active
NOTE: Works on distributions that use #networkmanager
-
CW: CW WPA3
Kundenlaptop Lenovo P14s mit Debian 12 funzt mit #WPA3. Da kann ich OS/Networkmanager/Supplicant wohl schon ausschließen.
-
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.
-
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: -
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: -
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: -
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: -
How To Assign IP Address To Remote Linux Systems Via SSH #Linuxnetworking #Ipaddress #Linuxcommands #Linuxhowto #Linuxadministration #nmcli #NetworkManager #Networking #Commandline #Bashscript #Shellscript
https://ostechnix.com/assign-ip-address-to-remote-linux-system-via-ssh/ -
How To Assign IP Address To Remote Linux Systems Via SSH #Linuxnetworking #Ipaddress #Linuxcommands #Linuxhowto #Linuxadministration #nmcli #NetworkManager #Networking #Commandline #Bashscript #Shellscript
https://ostechnix.com/assign-ip-address-to-remote-linux-system-via-ssh/ -
How To Assign IP Address To Remote Linux Systems Via SSH #Linuxnetworking #Ipaddress #Linuxcommands #Linuxhowto #Linuxadministration #nmcli #NetworkManager #Networking #Commandline #Bashscript #Shellscript
https://ostechnix.com/assign-ip-address-to-remote-linux-system-via-ssh/ -
How To Assign IP Address To Remote Linux Systems Via SSH #Linuxnetworking #Ipaddress #Linuxcommands #Linuxhowto #Linuxadministration #nmcli #NetworkManager #Networking #Commandline #Bashscript #Shellscript
https://ostechnix.com/assign-ip-address-to-remote-linux-system-via-ssh/ -
How To Assign IP Address To Remote Linux Systems Via SSH #Linuxnetworking #Ipaddress #Linuxcommands #Linuxhowto #Linuxadministration #nmcli #NetworkManager #Networking #Commandline #Bashscript #Shellscript
https://ostechnix.com/assign-ip-address-to-remote-linux-system-via-ssh/
