Wifi gone, Ubuntu 24.04, reinstalling network-manager does not work #networking #drivers #wireless #networkmanager

https://askubuntu.com/q/1549964/612

VPN grayed out when connecting via Horizon Client #networking #networkmanager #vpn

https://askubuntu.com/q/1549456/612

really weird, `wpa_supplicant` decided to shit itself and now only `iwd` works?

nm_log_dbg, _LOGD() and similar NetworkManager logs not appearing in terminal (non-systemd setup) #networkmanager

https://askubuntu.com/q/1547828/612

Can't connect to wireless internet while connected to a device over ethernet #networking #wireless #networkmanager #internet #ethernet

https://askubuntu.com/q/1547594/612

As #NetworkManager's #SSH VPN/tunnel plugin has now been ported to GTK4 and works directly from the #GNOME Control Center panel, I thought I'd finally try it out.

Once you figure out that you must only fill the gateway field, leave all IPs fields alone, tweak stuff in the Advanced dialog to have a working SOCKS proxy with "no tunnel", then it "works"… as long as you use the standard SSH port.

With SSH server ports other than 22, it fails on #Fedora… due to #SELinux

https://bugzilla.redhat.com/show_bug.cgi?id=1808435#c10

eSIM hotspot not working on Ubuntu #networking #networkmanager

https://askubuntu.com/q/1547434/612

Выпущен NetworkManager 1.52 с поддержкой интерфейса IPvlan и режима ethtool FEC, поддержкой автоматического добавления маршрутов к DNS-серверам и многим другим

https://linuxmasterclub.ru/release-networkmanager-1-52/

#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

#NetworkManager 1.52 Released with IPvlan Interface Support, ethtool FEC Mode, and Much More https://9to5linux.com/networkmanager-1-52-released-with-ipvlan-interface-support-ethtool-fec-mode

#TIL you'll need to set
`nmcli con mod <SSID> wifi.powersave disable`
for your headless pi that it doesn't lose wifi connectivity on idle.

Why is this not in the docs?

If it was a true #opensource project, I'd put up a pull request...

I wrote a blog post: "Building a #Linux #Firewall with #AlmaLinux 9, #NetworkManager, #BGP, #DHCP and #NFTables with #Puppet"
https://jon.sprig.gs/blog/post/8093

Оновив недавно #RaspberryPi OS до Bookworm. Ну, точніше, встановив Bookworm на нову картку пам'яті.

Довелося вирішувати виниклі проблеми з WiFi. Якщо точніше, з точкою доступу, який роздаю з малинки.

По-перше, до мене після оновлення добралась проблема з некоректним менеджментом енергозбереження, який треба вимкнути, щоб точка доступу працювала стабільно.

Або як тут:

https://www.thedigitalpictureframe.com/stay-connected-enhancing-raspberry-pi-wi-fi-stability-by-turning-off-power-management/

Або:
nmcli con modify <pointname> 802-11-wireless.powersave 2

Крім того, виявив, що за замовчанням точка доступу, створена через #NetworkManager , має захист WPA, а не WPA2. Щоб це змінити, треба в явному вигляді налаштувати протоколи:

sudo nmcli con modify <pointname> 802-11-wireless-security.proto rsn

sudo nmcli con modify <pointname> 802-11-wireless-security.pairwise ccmp

https://askubuntu.com/questions/1345284/how-to-disable-wpa1-security-and-keep-only-wpa2-aes-wifi-hotspot-on-ubuntu-18-04

Сконтролювати через #WifiAnalyzer.

До купи викинув WPS (теж десь знаходив, сторінку уже мабуть закрив):

nmcli con modify <pointname> 802-11-wireless-security.wps-method 1

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.

So I recently used a #sledgehammer where a #scalpel was needed.

I've got an #HP DL80 Gen9 with the iLO license, but without the #FlexibleLOM card... so to access the iLO I have to have an ethernet cable plugged into the first ethernet port.

Problem is, no matter what I tried in #Webmin or #NetworkManager, every reboot would re-enable that port... which would then get a IP via DHCP (even when I'd disabled it in nm...), which would mean #Zabbix would pick it up as a client and add it.. meaning every time a disk got a little "backed up", I'd get two alerts, and this machine has 12 very old SATA drives in it.

Tired of messing with the damned thing, I finally got out the sledgehammer....
....and blacklisted HP's #OUI from the #DHCP server.

No IP, no extra client created in Zabbix, and only the normally-annoying amount of alerts.

I'll #fsck with it for real, later...

Looking for opportunities to harden your Fedora system? Here's one way to make your VPN use more secure with NetworkManager.

https://fedoramagazine.org/protect-your-vpn-from-tunnelvision-attacks-with-networkmanager/

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

¹https://bbs.archlinux.org/viewtopic.php?id=289283

Managing IPv4 Address Conflict Detection with NetworkManager

https://fedoramagazine.org/managing-ipv4-address-conflict-detection-with-networkmanager/