reversion in recent wpasupplicant vs. intel 2011b ap (which advertises but does not support WPA)

[Brad Langhorst]

A year ago in this thread we found a way to work around a problem with
intel 2011b access points that advertise support for WPA but do not
actually support it at all.

http://readlist.com/lists/shmoo.com/hostap/0/1176.html

since then it look like jouni's fix has disappeared...

I can get an association to work if I do this:

--- wpasupplicant-0.6.0+0.5.8/events.c  2007-05-28 20:39:51.000000000
-0400
+++ /tmp/events.new     2007-10-23 17:08:05.607365129 -0400
@@ -464,8 +464,9 @@
                        }
 
                        if ((ssid->key_mgmt & 
-                            (WPA_KEY_MGMT_IEEE8021X |
WPA_KEY_MGMT_PSK)) ||
-                           bss->wpa_ie_len != 0 || bss->rsn_ie_len !=
0) {
+                            (WPA_KEY_MGMT_IEEE8021X |
WPA_KEY_MGMT_PSK)) 
+                             /*||
+                           bss->wpa_ie_len != 0 || bss->rsn_ie_len != 0
*/) {
                                wpa_printf(MSG_DEBUG, "   skip - "
                                           "WPA network");
                                continue;

Jouni applied a fix that checked to see if the user allowed non WPA in
her config, but i don't have a config file - instead I'm using
NetworkManager (which visually shows me that it's not a WPA network).

What's the correct fix now?

I have captured a beacon with 
sudo tcpdump -i eth1 -x -n

16:47:15.818388 Beacon (ppwn) [1.0* 2.0* 5.5 11.0 Mbit] ESS CH: 6
        0x0000:  f933 2db5 0100 0000 6400 0100 0004 7070
        0x0010:  776e 0104 8284 0b16 0301 0605 0404 0a00
        0x0020:  0007 0655 5320 010b 1ead 0f00 a0f8 0100
        0x0030:  0000 0a00 0000 0000 0000 dd12 0050 f201
        0x0040:  0100 0050 f200 0000

I don't know what those fields mean... but Stefan Rompf asked for a
beacon frame last time around.

I hope that's helpful.

brad