On Sat, Jul 15, 2023 at 02:04:57PM -0400, nick black wrote: > Sam Hartman left as an exercise for the reader: > > I consider anything that requires me to write wpa_supplicant config to > > be a bad idea (unless I'm running an AP) and NetworkManager driving > > wpa_supplicant is a better idea. > > i think everyone's agreed on this part.
For my part I tend to prefer writing wpa_supplicant configs, as they're
dead simple and allow for easy setting of priorities. Including them from
/etc/network/interfaces is also trivial.
Example /etc/network/interfaces and /etc/wpa_supplicant/wpa_supplicant.conf
from my laptop, with just the names changed:
---------------------------------------------------------------------------
source /etc/network/interfaces.d/*
auto eth0
iface eth0 inet dhcp
pre-up /sbin/mii-tool eth0 | /bin/grep -qv "no link"
auto wlan0
iface wlan0 inet dhcp
pre-up /sbin/mii-tool eth0 | /bin/grep -q "no link"
wpa-conf /etc/wpa_supplicant/wpa_supplicant.conf
---------------------------------------------------------------------------
---------------------------------------------------------------------------
network={
ssid="Home"
psk="home password"
# Can also be this, via wpa_passphrase:
# psk=15bd59d568643e6781dd12f7e160b0589242472d3cc299bb5b0c4289d40c01af
priority=20
}
network={
ssid="CoffeeShop"
#psk="coffee password"
psk=ccd48495b2a1b7502f0bb0c5ca3689f6847b4f8532ce195ec17080308acb6bcd
priority=10
}
network={
key_mgmt=NONE
}
---------------------------------------------------------------------------
So, not quite everyone agrees. An advantage to using wpa_supplicant.conf
directly is that it works everywhere, and can generally be distributed as-
is across different operating systems.
--
Mason Loring Bliss ma...@blisses.org http://blisses.org/
For more enjoyment and greater efficiency, consumption is being standardized.
signature.asc
Description: PGP signature
