On Mon, Jan 21, 2019 at 07:13:44PM +0100, Andrej Shadura wrote: > On Tue, 15 Jan 2019 at 14:08, Andrej Shadura <andrew@xxxxxxxxxx> wrote: > > Forwarding yet another issue; this time, with BCM4360 :( > 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 This sounds like an issue with the particular driver not liking the Extended Capabilities element values that gets added when new protocol functionality is enabled. Those listed items (or well, CONFIG_FILS and CONFIG_MBO) end up setting new bits in the element. A verbose wpa_supplicant debug log would be helpful in confirming that, though. If this is the reason for the regression, there is unfortunately no clean way of working around the driver issue. This would require some configuration parameter to disable addition of new Ext Capab flags (and obviously disabling the relevant functionality). And potentially automatically enabling that workaround based on the used driver, but that is somewhat inconvenient if there are different versions of the driver and some of them work and some that don't. -- Jouni Malinen PGP id EFC895FA _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
