Search
388 results for “NetworkManager”
-
Did you miss ADMIN Update last week? Read it now and subscribe free to get it every Wednesday https://mailchi.mp/admin-magazine/admin-update-free-help-desk #HelpDesk #FreeScout #TUXEDOComputers #Jupiter #exascale #NSA #Kubernetes #NetworkManager #containers #Linux #jobs #events #BeowulfBash #SC23
-
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 -
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 -
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 -
A new "Your own extras" is available:
Check the new "Donation list" to support your favourite free and open source software.
It includes all the #donation links with all the listed #tutorials and #services we provide.https://wiki.techsaviours.org/en/extras/donation_list
Still missing links:
- #lvm
- #luks
- #networkmanager
- #zram
- #sddm
- #firewalld
- #cronie ( #crontab )
- #rsync
- #AdGuardHome
- #redis
- #docker
- #LibreWolf
- #arkenfox
- #CustomNewTabPage
- #ProxySwitchOmega
- #Icecraven -
Huch? #raspberrypi mit #raspian von #debian #bullseye auf #bookworm per `apt dist-upgrade` hochgezogen.
#NetworkManager verliert dann **sämtliche** WLAN-Informationen und damit taucht das Ding nicht mehr im WLAN auf.
Kennt das jemand? Bug?! Feature?!
-
🚀 Raspberry Pi travelers & tinkerers: Turn your Pi into a powerful Wi-Fi hotspot! Share internet from USB tethering (Android/iPhone) or Ethernet – perfect for on-the-go, old routers, or secure home networks.
Easy NetworkManager setup (no hostapd hassle), auto-connect, WPA security + integrate Pi-Hole/TOR!
Go mobile with my beginner-friendly guide: 👉 https://peppe8o.com/raspberry-pi-wi-fi-hotspot/
#RaspberryPi #WiFiHotspot #SelfHosting #PiProjects #TechTips
Tag a friend who'd love portable internet! 🔥 -
💡To display the DHCP IPv4 options assigned to a Linux client, use the following command line @opensuse @fedora @NetworkManager #ZikTIPs #CLI #Networking #Linux #OpenSource
nmcli -f DHCP4 device show "$INTERFACE"
e.g. nmcli -f DHCP4 device show eth0
-
::: Unohditko WiFi-salasanasi? - KATSO SE yhteydessä olevaan verkkoosi Linuxissa 📶
Avaa pääte & käytä näitä komentoja.
Ubuntu:
ls /etc/NetworkManager/system-connections/
-----
Nmcli:tä käyttävät (esim. Solus):
nmcli device wifi show-password
(Tällä tavalla saat ohessa myös QR-koodin) 💥
#WiFi #Linux #verkko #salasana #Ubuntu #Solus #yhteys #yhteydet #qr #verkkoavain #vinkit
-
I am struggling to get my #archlinux IKE2 VPN working. I used to be able to just add the certificate and private key with the NetworkManager plug- in but now it complains about not being able to find the private key.
-
CW: PSA: Disabling connectivity surveillance on GNU/Linux
Yes you can disable #connectivityChecks without adverse issues. Connectivity checks are done every 3-5 minutes and only important if you often use random WiFi systems that might require a password to use.
Overwrite settings at '20-connectivity.conf':
sudo bash << EOF
echo "[connectivity]
enabled=0" >> /etc/NetworkManager/conf.d/$(whoami)-connectivity.conf
EOF -
Giving up for today trying to get #8021x (via ethernet, only using credentials, no certificates) working on #NixOS using #wpa_suplicant and #NetworkManager authing against a #UniFi infrastructure...
The debug output from both, NetworkManager, and (especially) wpa_supplicant is quite useless in this regard, as it focuses on technical mumble-jumble that might be useful to someone knees-deep into #RADIUS, but helps zero when it comes to a regular admin trying to get this working.
-
Di cosa dovrei #incazzarmi di più: del fatto che ormai da mesi — e in questi ultimissimi giorni la #storia è peggiorata #tragicamente, guardare per credere — la linea #Internet di casa salta di continuo, mettendo da sé continui bastoni tra le ruote al mio workflow… o del fatto che quando collego il telefono via tethering USB il mio sistema desktop sembra non essere sempre in grado di routare correttamente i pacchetti — in certi casi capisce che deve farli passare attraverso il telefono sennò non vanno da nessuna parte, ma altre volte si ostina a mandarli al mio bridge ethernet? #MANNAGGIA!!! 🗡️🗡️
È una domanda retorica, ovviamente; mi #incazzo più con #Vodafone, che mio padre paga per farci avere in cambio un servizio che dire #scadente è fargli un complimento, di quanto mi possa mai arrabbiare contro un software no-profit per un #problema che posso aggirare praticamente scollegando dei cavi. Però davvero non ne posso più, non solo questo comportamento mi ruba tempo quando lavoro al PC, ma mi manda pure giù le cose che ospito sul serverino in casa, e che palle. 😭️
Ogni tanto ricordo di questo bordello a mio padre, ma fino ad ora ancora non l’ho convinto a provare a comprare un #router nuovo, uno vero con cui rimpiazzare quel rottame della #VodafoneStation… lui dice che probabilmente i problemi sono sulla linea, e in parte anche io credo sia così (ma chissà quale segmento della linea!); però se anche così fosse il caso, resta comunque indecente il fatto che, mentre il #collegamento alla WAN si scollega e il #modem tenta di ricollegarsi, la Station non è nemmeno in grado di roteare pacchetti in LAN… cioè, fai
Ah, non centra con questi #problemi (mi è sempre capitato, e non impatta su questa situazione), ma guardate qui sto #bug: certe volte (credo a furia di disconnessioni e riconnessioni?) #NetworkManager sfancula e cambia i nomi delle mie schede di #rete nel pannello rapido (in questo caso di GNOME, ma lo faceva anche su Cinnamon)… ma poi nelle impostazioni i nomi sono corretti. Mamma mia che #disagio il software. 😩️pinge avoja ad aspettare, non risponde. È evidente che pure il #software che sta lì sopra fa schifo, mica solo la linea. E-waste puro. 💀️https://octospacc.altervista.org/2024/02/07/mannaggia-a-vodafone-di-continuo/
#bug #collegamento #disagio #incazzarmi #incazzo #Internet #Mannaggia #modem #NetworkManager #problema #problemi #rete #router #scadente #software #storia #tragicamente #Vodafone #VodafoneStation
-
TIL that running #rke2 on #rhel9 means that I should tell rke2 to NOT use /etc/resolv.conf, as this only contains 127.0.0.1 which means that Google DNS (8.8.8.8) will be used inside the containers...
Luckily NetworkManager has a file with my configured name servers in /run/NetworkManager/ and rke2 has a config option that my #Ansible role supports...
-
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 which 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
-
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
-
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
-
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
-
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 -
::: Forgot your WiFi password? - Find that password of your connected network in Linux 📶
Open the terminal & use these commands.
Ubuntu:
ls /etc/NetworkManager/system-connections/
------
The ones using Nmcli (for example Solus):
nmcli device wifi show-password
(This way you even get a QR code) 💥
#quickies #tips #find #WiFi #Linux #Ubuntu #network #password #Solus #Nmcli #NetworkManager #hints #help #connection #terminal #QR
-
::: Forgot your WiFi password? - Find that password of your connected network in Linux 📶
Open the terminal & use these commands.
Ubuntu:
ls /etc/NetworkManager/system-connections/
------
The ones using Nmcli (for example Solus):
nmcli device wifi show-password
(This way you even get a QR code) 💥
#quickies #tips #find #WiFi #Linux #Ubuntu #network #password #Solus #Nmcli #NetworkManager #hints #help #connection #terminal #QR
-
RE: https://mastodon.social/@mabcode/115569504712692034
Package_2025_Nov_19
git-2.52.0-1-x86_64.pkg.tar.zst
libnm-1.54.2-1-x86_64.pkg.tar.zst
libxm12-2.15.1-4-x86_64.pkg.tar.zst
networkmanager-1.54.2-1-x86_64.pkg.tar.zstTotal Download Size: 12.380 Mib
Total Instilled Size: 52.5 Mibhttps://github.com/MasoudAmiriBatmanghlnj/Linuxbase/releases/tag/Package_2025_Nov_19
-
Did you miss ADMIN Update last week? Read it now and subscribe free to get it every Wednesday https://mailchi.mp/admin-magazine/admin-update-free-help-desk #HelpDesk #FreeScout #TUXEDOComputers #Jupiter #exascale #NSA #Kubernetes #NetworkManager #containers #Linux #jobs #events #BeowulfBash #SC23
-
Did you miss ADMIN Update last week? Read it now and subscribe free to get it every Wednesday https://mailchi.mp/admin-magazine/admin-update-free-help-desk #HelpDesk #FreeScout #TUXEDOComputers #Jupiter #exascale #NSA #Kubernetes #NetworkManager #containers #Linux #jobs #events #BeowulfBash #SC23
-
Did you miss ADMIN Update last week? Read it now and subscribe free to get it every Wednesday https://mailchi.mp/admin-magazine/admin-update-free-help-desk #HelpDesk #FreeScout #TUXEDOComputers #Jupiter #exascale #NSA #Kubernetes #NetworkManager #containers #Linux #jobs #events #BeowulfBash #SC23
-
Did you miss ADMIN Update last week? Read it now and subscribe free to get it every Wednesday https://mailchi.mp/admin-magazine/admin-update-free-help-desk #HelpDesk #FreeScout #TUXEDOComputers #Jupiter #exascale #NSA #Kubernetes #NetworkManager #containers #Linux #jobs #events #BeowulfBash #SC23
-
Как работает DNS в Linux. Часть 3: Разбираемся с resolv.conf, systemd-resolved, NetworkManager и другими
Теоретическую основу кэширования DNS в Linux мы разбирали в первой части , где говорили про работу процесса разрешения имен — от вызова getaddrinfo() до получения IP-адреса. Вторая часть была посвящена различным уровням кэшей самой системы, приложений и языков программирования, контейнеров, прокси - а также их мониторингу и сбросу. Теперь самое время перейти к практике. Если вы когда-либо запускали подряд команды ping, curl, dig и получали разные IP-адреса, вы не одиноки. Поведение DNS в Linux — не просто вызов getaddrinfo() . Это взаимодействие множества слоёв: от glibc и NSS до NetworkManager , systemd-resolved, dnsmasq и облачных конфигураций. В этой части разберем практические аспекты DNS: почему одинаковые запросы дают разные IP как реально контролируется разрешение имен: что вызывает кого и зачем как проводить диагностику: strace, resolvectl, tcpdump
https://habr.com/ru/companies/k2tech/articles/941284/
#linux #dns #resolvconf #resolv #network #сетевые_технологии #сетевая_инфраструктура #devops #облачные_сервисы #облачные_технологии
-
The new #RaspberryPi OS (Bookworm) is a much more exciting upgrade than I would expect from them. The switch to #Wayland and #PipeWire from #X11 and #PulseAudio, a #Firefox browser optimised for Raspberry Pis as an option in addition to the dreadful #Chromium, and #NetworkManager as the default now instead of #dhcpcd. Honestly the best thing about this upgrade is their documentation all about it, it's very well written and even I was able to learn all about why they did what they did, and what these changes mean for Raspberry Pis in the long run.
Bookworm Raspberry Pi OS is available for a clean install on all the Raspberry Pis now, but with some certain features missing or coming for Raspberry Pi 3 or older. 4 and 5 should already support all that Bookworm has to offer.
🔗 https://www.raspberrypi.com/news/bookworm-the-new-version-of-raspberry-pi-os -
#BeagleBoard I'm now playing mix and match between guides to see what works with #connman. My ethernet and wifi will both a.) connect on restart/boot and b.) retain their mac addresses or I will get NetworkManager on here somehow.
Note to #connman: my network is MAC filtered and IP reserved. No, you can't get in unless the MAC is recognized. For God's sake who hurt you?
-
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