This bug was fixed in the package netplan.io - 0.104-0ubuntu1
---
netplan.io (0.104-0ubuntu1) jammy; urgency=medium
* New upstream release: 0.104
- Enable 'embedded-switch-mode' setting on SmartNICs
- Permit multiple patterns for the driver globs in match (LP: #1918421)
** Changed in: netplan
Status: Triaged => Fix Committed
--
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
A related change to automatically fallback inside wpa_supplicant itself
just landed: https://launchpad.net/ubuntu/+source/wpa/2:2.9.0-23
--
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:
See https://github.com/canonical/netplan/pull/240
--
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
For example, fallback (-Dnl80211,wext) is used for the wpa_supplicant systemd
service:
https://salsa.debian.org/debian/wpa/-/blob/debian/unstable/debian/patches/networkd-
driver-fallback.patch
But it isn't present in the netplan networkd renderer.
--
You received this bug notification because
> What is the range of possible values for this -D option, and why would
you ever want to specify it in the netplan yaml instead of inferring it?
It would be best if wpa_supplicant selected the correct driver, but it
seems it doesn't do a good job with this. It does support fallbacks,
though,
I have this trouble too!!! Please fix it!
--
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:
This bug affects me
tested on two different adaptors
/sbin/wpa_supplicant -c /run/netplan/wpa-wlxd037453da72a.conf -iwlxd037453da72a
-Dwext
will work for me
lsusb reports 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 802.11n Wireless
Network Adapter
however running
/sbin/wpa_supplicant -c
Same here. Also using rtl8188 chipset which only works with wext.
--
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
I have this problem too, I think netplan is garbage, because it has no
config for some networkd config(such as mdns and ipv6 prefix
delegation), it only have is a basic network config, I don't know why
bother use netplan but it's integrated in ubuntu as essential(ubuntu-
minimal and cloud-init all
This also affects me: the wireless dongle I am using needs wext driver
but by default netplan is trying to use the nl80211 driver. If I
specify -Dwext as seen in this paste I can get a connection:
https://paste.ubuntu.com/p/gxDb7PcFnP/
--
You received this bug notification because you are a
This bug affects me too: to be able to use my RTL-8188EUS on Ubuntu
Server 18.04.4 I have to pass -Dwext as parameter to wpa_supplicant. My
workaround up to now has been to create a wrapper script named
wpa_supplicant renaming the original executable.
--
You received this bug notification
Here's one (e.g. my) case:
Asus AC1200 USB-AC53 Nano wifi adapter. No linux driver available from
the manufacturer. But there are open-source drivers available that work
well, but that require the -D parameter in order to be able to use
wpa_supplicant.
Quoting
I'm afraid I still don't understand from this why one would specify a -D
option by hand
--
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
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
What is the range of possible values for this -D option, and why would
you ever want to specify it in the netplan yaml instead of inferring it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814012
That's not quite the device, but a driver value though. I wonder if it
wouldn't be best to either always set -Dnl80211 on wireless (and -Dwired
for 802.1x on ethernet...), or to make it possible to use an alternative
value if matching by driver.
For example:
wifis:
wlan1:
match:
Triaged; we will need some input from Steve though to figure out how to
addess this in the netplan schema.
It's Triaged High as it actually does potentially impact many devices.
There are sadly still lots of devices that either don't do wext, or
don't do nl80211, and maybe it wouldn't hurt to be
18 matches
Mail list logo
