4 ms·
Echo this; I was using an X201s with a bunch of OS's Linux has the mess of NetworkManager FreeBSD idled hard and also has wifi-supplicant and crap. Solaris i
by dijit 9y ago
Echo this; I was using an X201s with a bunch of OS's
Linux has the mess of NetworkManager
FreeBSD idled hard and also has wifi-supplicant and crap.
Solaris is a dead end and you can forget wifi.
OpenBSD was perfect, it felt so cleanly engineered with wifi/wpa handled by ifconfig.
the only concern was the bluetooth- they do not support, in any form, bluetooth. Because: "We have never seen a clean implementation of bluetooth". And yes, they trail with wifi support, but on a 7 year old laptop, that's fine.
Did wonders for my battery life too.
- agumonkey 9y agoI avoid NM for reasons, archlinux netctl and/or systemd networkd is good enough.
- floatboth 9y ago> wifi-supplicant and crap What's wrong with wpa_supplicant? It works really well, you just write one config file with all the networks and you can set the networks' priorities…
- dijit 9y agoMuch easier to just: ifconfig wlan0 scan ifconfig wlan0 ssid "thingIfound" wpakey "password" up dhclient wlan0
- floatboth 9y agoThat's easy for joining random hotspots, yeah. But for a more stable setup, wpa_supplicant is excellent. I have a config that prefers my home network (which is EAP-TLS secured, how does ifconfig on OpenBSD handle that?), then mobile hotspot, then a couple other known networks. It automatically decides the best network to use.
- dijit 9y agoThat is indeed cool, I used to rely on my bash history to find my old ifconfigs for common networks I liked. It's lower power though. Due to lack of polling. I guess there are advantages to the wpa_supplicant way of doing things too. But you have the option on openbsd too at least.