On Tue, 15 Jan 2019 at 14:08, Andrej Shadura <andrew@xxxxxxxxxx> wrote: > Hi, > > Forwarding yet another issue; this time, with BCM4360 :( One of the users (cc'ed) adds to the bug report: =========================== Dear Maintainer, I am also seeing (probably) the same problem with wl. My machine works with wpasupplicant <= 2:2.7~git20181004+1dd66fc-1, but not with >= 2:2.7-1. After bisecting changes to upstream and Debian packaging, I have found that disabling at least following build-time options, all of which have been enabled in 2:2.7-1 or 2:2-7-2, restores it to work well again: CONFIG_FILS CONFIG_MBO CONFIG_MESH CONFIG_FILS_SK_PFS looks related to CONFIG_FILS, so I suppose this should also be disabled, while it looks working whether or not this option is set in my experiment. Moreover, upstream says FILS should be disabled; quoting from wpa_supplicant/defconfig: # Fast Initial Link Setup (FILS) (IEEE 802.11ai) # Note: This is an experimental and not yet complete implementation. This # should not be enabled for production use. #CONFIG_FILS=y # FILS shared key authentication with PFS #CONFIG_FILS_SK_PFS=y Note that we need to cherry-pick an upstream commit after 2.7, f2973fa39d6109f0f34969e91551a98dc340d537, to avoid FTBFS with CONFIG_FILS disabled. =========================== -- Cheers, Andrej _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
