Activity log for bug #1814012

Date Who What changed Old value New value Message
2019-01-31 00:46:26 Gordon Harris bug added bug
2019-03-20 21:22:38 Mathieu Trudel-Lapierre netplan: status New Triaged
2019-03-20 21:22:44 Mathieu Trudel-Lapierre netplan: importance Undecided High
2019-03-20 21:22:49 Mathieu Trudel-Lapierre bug task added netplan.io (Ubuntu)
2019-03-20 21:22:54 Mathieu Trudel-Lapierre netplan.io (Ubuntu): status New Triaged
2019-03-20 21:22:58 Mathieu Trudel-Lapierre netplan.io (Ubuntu): importance Undecided High
2019-03-20 21:24:37 Mathieu Trudel-Lapierre netplan: assignee Steve Langasek (vorlon)
2019-04-20 17:49:19 Gordon Harris description Some wifi adaptors need to use the -Ddevicename argument for wpa_supplicant to successfully associate with an AP. The netplan yaml spec doesn't currently support an optional device 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" 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-wpa@wlx4cedfb37602e.service ..to include the proper device 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" ..option for the yaml file that would add the -Ddevicename to the unit file. 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 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" 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-wpa@wlx4cedfb37602e.service ..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..   driver: "drivername" ..option for the yaml file that would add the -Ddrivername to the unit file.
2021-10-21 07:52:45 Lukas Märdian netplan: status Triaged Fix Committed
2022-02-18 15:10:54 Launchpad Janitor netplan.io (Ubuntu): status Triaged Fix Released
2024-01-29 13:43:17 Lukas Märdian netplan: status Fix Committed Fix Released