I did digging in the driver, and found that line 868 of ieee80211_input.c was the part giving the message, traced the node_is_authorized and found that exceptions are made for 8021X (LEAP notably). I didn't dig deep as to how a node was to be authorized in 8021X as opposed to WPA2, so I just noted the exceptions like:
if (ni->ni_authmode != IEEE80211_AUTH_8021X) ieee80211_node_authorize(ni);
In ieee80211_input.c: 1314
and ieee80211_proto.c:1535
And changed them to:
/* if (ni->ni_authmode != IEEE80211_AUTH_8021X) */ ieee80211_node_authorize(ni);
And now LEAP works (but still only if mode 11b is issued). This is now definitely two separate issues. This workaround is probably not the correct way with respect to security, so someone who knows the madwifi driver must comment as to what is probably going wrong.
I did digging in the driver, and found that line 868 of ieee80211_input.c was the part giving the message, traced the node_is_authorized and found that exceptions are made for 8021X (LEAP notably). I didn't dig deep as to how a node was to be authorized in 8021X as opposed to WPA2, so I just noted the exceptions like:
if (ni->ni_authmode != IEEE80211_ AUTH_8021X)
ieee80211_ node_authorize( ni);
In ieee80211_input.c: 1314 proto.c: 1535
and ieee80211_
And changed them to: AUTH_8021X) */
ieee80211_ node_authorize( ni);
/* if (ni->ni_authmode != IEEE80211_
And now LEAP works (but still only if mode 11b is issued). This is now definitely two separate issues. This workaround is probably not the correct way with respect to security, so someone who knows the madwifi driver must comment as to what is probably going wrong.