Re range of possible values for -D option:
>From man wpa_supplicant:
AVAILABLE DRIVERS
A summary of available driver backends is below. Support for each of
the driver backends is
chosen at wpa_supplicant compile time. For a list of supported driver
backends that may be used
with the -D option on your system, refer to the help output of
wpa_supplicant (wpa_supplicant -h).
wext Linux wireless extensions (generic).
wired wpa_supplicant wired Ethernet driver
roboswitch
wpa_supplicant Broadcom switch driver
bsd BSD 802.11 support (Atheros, etc.).
ndis Windows NDIS driver.
from wpa_supplicant --help on my system:
drivers:
nl80211 = Linux nl80211/cfg80211
wext = Linux wireless extensions (generic)
wired = Wired Ethernet driver
none = no driver (RADIUS server/WPS ER)
** Description changed:
- Some wifi adaptors need to use the -Ddevicename argument for
+ Some wifi adaptors need to use the -Ddrivername argument for
wpa_supplicant to successfully associate with an AP.
- The netplan yaml spec doesn't currently support an optional device
+ The netplan yaml spec doesn't currently support an optional driver
property for the wifis type.
For instance, here's my 01-netcfg.yaml:
network:
- version: 2
- renderer: networkd
- ethernets:
- ens32:
- dhcp4: no
- dhcp6: no
- addresses: [192.168.0.222/24]
- gateway4: 192.168.0.1
- nameservers:
- addresses: [8.8.8.8,8.8.4.4]
- wifis:
- wlx4cedfb37602e:
- optional: true
- dhcp4: no
- dhcp6: no
- addresses: [192.168.1.222/24]
- access-points:
- "myssid":
- password: "mywpapsk"
+ version: 2
+ renderer: networkd
+ ethernets:
+ ens32:
+ dhcp4: no
+ dhcp6: no
+ addresses: [192.168.0.222/24]
+ gateway4: 192.168.0.1
+ nameservers:
+ addresses: [8.8.8.8,8.8.4.4]
+ wifis:
+ wlx4cedfb37602e:
+ optional: true
+ dhcp4: no
+ dhcp6: no
+ addresses: [192.168.1.222/24]
+ access-points:
+ "myssid":
+ password: "mywpapsk"
This isn't currently enough to get the wifi interface to associate. I
have to hand-edit:
/run/systemd/system/multi-user.target.wants/netplan-
[email protected]
- ..to include the proper device name. E.g.:
+ ..to include the proper driver name. E.g.:
[Service]
Type=simple
ExecStart=/sbin/wpa_supplicant -c /run/netplan/wpa-%I.conf -i%I -Dnl80211
Once that edit has been made and systemctl daemon-reload run, the wifi
interface associates.
It would be nice if netplan included a..
- device: "devicename"
+ driver: "drivername"
- ..option for the yaml file that would add the -Ddevicename to the unit
+ ..option for the yaml file that would add the -Ddrivername to the unit
file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814012
Title:
netplan type wifis needs a device option
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1814012/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
