[Bug 304126] Re: Cannot connect to Enterprise WPA2 wireless (Invalid Compound_MAC)

2012-05-16 Thread Maarten Bezemer
This bug report is being closed due to the last two comments regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn mo

[Bug 304126] Re: Cannot connect to Enterprise WPA2 wireless (Invalid Compound_MAC)

2009-01-12 Thread Wirawan Purwanto
Confirming that this is not a problem with 0.6.7. Just FYI, I am reporting another bug which seems to be unrelated: https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/316460 Wirawan -- Cannot connect to Enterprise WPA2 wireless (Invalid Compound_MAC) https://bugs.launchpad.net/bugs/30

[Bug 304126] Re: Cannot connect to Enterprise WPA2 wireless (Invalid Compound_MAC)

2008-12-14 Thread Jouni Malinen
The interop issue is now resolved in git version of wpa_supplicant and the fix should show up in 0.6.7 with the 0.6.6-workaround removed. -- Cannot connect to Enterprise WPA2 wireless (Invalid Compound_MAC) https://bugs.launchpad.net/bugs/304126 You received this bug notification because you are

[Bug 304126] Re: Cannot connect to Enterprise WPA2 wireless (Invalid Compound_MAC)

2008-12-01 Thread Jouni Malinen
This is an interoperability issue with EAP-PEAPv0 Cryptobinding between wpa_supplicant and Windows Server 2008 NPS. wpa_supplicant 0.6.6 works around this by disabling cryptobinding use by default. This can be done in older versions, too, by adding crypto_binding=0 into the network configuration pa