I’m forwarding a follow-up to a thread named "Scan trigger failed: ret=-22 (Invalid argument)". There’s nothing actually private in this email, so I suppose it is fine. As the result of this I have temporarily disabled WNM support in Debian’s wpa-supplicant, but I keep getting requests to re-enable in again, but I’m hesitant to re-enable it. I’m unsure what can be done about this. ---------- Forwarded message --------- From: YOSHINO Yoshihito <yy.y.ja.jp@xxxxxxxxx> Date: Wed, 27 Dec 2017 at 18:05 Subject: Re: Scan trigger failed: ret=-22 (Invalid argument) To: Andrew Shadura <andrew@xxxxxxxxxx> Hi Andrew, On Wed, Dec 27, 2017 at 8:39 PM, Andrew Shadura <andrew@xxxxxxxxxx> wrote: > Until this is fixed (hopefully) upstream, how do you think, what would > be an impact of setting CONFIG_WNM=n? That should work around the > issue for you, but how much of a degraded experience will it be for > everyone else? Hmm ... many other distributions seem to disable CONFIG_WNM: Fedora (1:2.6-12) https://src.fedoraproject.org/rpms/wpa_supplicant/blob/master/f/build-config openSUSE Tumbleweed (2.6-4.2) http://download.opensuse.org/tumbleweed/repo/src-oss/suse/src/wpa_supplicant-2.6-4.2.src.rpm openSUSE Leap 42.3 (2.2-13.1) https://download.opensuse.org/repositories/openSUSE:/Leap:/42.3:/Update/standard/src/wpa_supplicant-2.2-13.1.src.rpm Arch Linux (1:2.6-11) https://git.archlinux.org/svntogit/packages.git/tree/trunk/config?h=packages/wpa_supplicant Gentoo (2.6-r4) https://gitweb.gentoo.org/repo/gentoo.git/tree/net-wireless/wpa_supplicant/wpa_supplicant-2.6-r4.ebuild FreeBSD port (2.6_2) https://svnweb.freebsd.org/ports/head/security/wpa_supplicant/Makefile?view=log FreeBSD base (2.4) https://svnweb.freebsd.org/base/head/usr.sbin/wpa/wpa_supplicant/Makefile?view=log https://svnweb.freebsd.org/base/head/usr.sbin/wpa/Makefile.inc?view=log https://svnweb.freebsd.org/base/head/usr.sbin/wpa/Makefile.crypto?view=log NetBSD (2.6nb1) https://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/net/wpa_supplicant/files/ OpenBSD (2.6p1) http://cvsweb.openbsd.org/cgi-bin/cvsweb/ports/security/wpa_supplicant/files/config Upstream considers this experimental and incomplete, and the example config disables this: https://w1.fi/cgit/hostap/tree/wpa_supplicant/defconfig > # Wireless Network Management (IEEE Std 802.11v-2011) > # Note: This is experimental and not complete implementation. > #CONFIG_WNM=y (BTW, "CONFIG_WNM=n" does not disable this: > # This file lists the configuration options that are used when building the > # wpa_supplicant binary. All lines starting with # are ignored. Configuration > # option lines must be commented out complete, if they are not to be included, > # i.e., just setting VARIABLE=n is not disabling that variable. ) I have also disabled this and it seems to work fine. I suppose it is reasonable to disable this. Note also that NM works fine on my machine without no-mac-addr-change.conf if this is disabled or my temporary patch is applied. Debian has enabled this since 2.2-1 because of the suggestion by Gerald Turner https://bugs.debian.org/718651#42 but I do not see the exact reason why he has activated this. Regards, -- YOSHINO Yoshihito <yy.y.ja.jp@xxxxxxxxx> -- Cheers, Andrej _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
