[ath9k-devel] ath9k not connecting to one particular network..

[Linus Torvalds <torvalds@linux-foundation.org>]

On Mon, Mar 25, 2013 at 9:42 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Mon, Mar 25, 2013 at 9:35 AM, Jouni Malinen <jouni@qca.qualcomm.com> wrote:
>>
>> I'm not really familiar with debugging with NM enabled, but it could be
>> possible that the instructions for the older wpa_supplicant on
>> https://live.gnome.org/NetworkManager/Debugging could be adopted for
>> this. The key here would be to get -K added wpa_supplicant command line
>> since exposing of the keys cannot be enabled dynamically at runtime.
>
> I tried that already, but couldn't get it to work. I suspect there's
> some tighter integration between NM and wpa_supplicant, so that it
> doesn't actually use that Exec= line any more, or edits it, or
> something.

Nothing sane worked, so I did a brute-force "let's just make
wpa_supplicant a shell-script that adds the debug fields and then runs
the real wpa_supplicant binary with the extra flags".

And that worked.

The bugzilla at

  https://bugzilla.redhat.com/show_bug.cgi?id=927191

now has a wpa_supplicant trace with keys and timestamps for the
non-working NetworkManager case too.

I see no sane difference. There are several dbus-related setup
differences, but then in the actual handshake, afaik they do the same
thing, except the non-working one never gets the reply after sending
EAPOL-Key 2/4. I dunno. I have no idea what that thing is actually
doing.

Hopefully somebody else can see what the difference is.

               Linus