Linux

48328 readers

636 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

Wi-Fi connectivity issues resolved by dropping wpa_supplicant in favour of iwd (lemmy.ml)

submitted 7 months ago by jokeyrhyme@lemmy.ml to c/linux@lemmy.ml

11 comments fedilink hide all child comments

My desktop PC is the only machine in the house having Wi-Fi connectivity issues (connects fine, but drops out randomly after a few minutes or sometimes a few hours)

I think wpa_supplicant is getting confused and thinks signal strength is poor (I have a Netgear mesh, but this seems increasingly common, so it's weird for that to be the issue)

I did pick up a TP-Link USB Wi-Fi adapter, but can reproduce the same connectivity issues

The fix was switching away from wpa_supplicant in favour of iwd, which seems rock solid in comparison

I'm sure there's a way to fix wpa_supplicant, but it's man pages only seem to list the options without actually describing what they do, which seems sort of poor considering how old the project is 🤷

you are viewing a single comment's thread
view the rest of the comments

[–] d3Xt3r@lemmy.nz 7 points 7 months ago (3 children)

iwd is great. In fact I'd say take it a step further and get rid of the beast that is NetworkManager as well.

https://austindw.com/networkmanager-is-bloat/

[–] LemmyHead@lemmy.ml 5 points 7 months ago (1 children)

Tbf you only need iwd, as systemd can take care of the rest. But it's not an option for me on desktop anyway because signal and vpn connection visibility are important for me and that's not possible without a GUI running

[–] d3Xt3r@lemmy.nz 3 points 7 months ago

There are lightweight GUI options for that too. For iwd, you can use iwgtk. For VPN, that would depend on your VPN protocol/service. Some providers like Proton have their own client, others can use something like Wireguard Client (as an example) or something similar depending on your VPN setup.

[–] jokeyrhyme@lemmy.ml 1 points 7 months ago

I did actually do this already, separate from working on this issue, but can confirm the intermittent problems with the combination of wpa_supplicant and systemd-networkd

[–] MonkderDritte@feddit.de 1 points 7 months ago

Though connman supports iwd only partially, no?