Paul Marks wrote:
> On 1/26/07, Larry Finger <[EMAIL PROTECTED]> wrote:
>> Paul Marks wrote:
>> > I have a BCM4311 card, and ever since the PCI-E interrupts patch,
>> I've been
>> > able to associate just fine with my own WPA2-PSK access point, using
>> > wpa_supplicant with ap_scan=1.
>> >
>> > However, the access points at my school (Purdue) are all
>> WPA-Enterprise with
>> > a hidden SSID, and I so far haven't had any luck getting bcm43xx to
>> connect
>> > to these. If I use ndiswrapper instead, then these APs work as
>> expected.
>> >
>> > Am I doing something wrong, or is this a limitation in the driver? Has
>> > anyone gotten bcm43xx to work in a hidden-SSID situation?
>> >
>> > -snip-
>>
>> It should work. I just hid my SSID and had no trouble seeing the AP
>> when scanning nor any problem
>> with associating or authenticating.
>>
>> How close are you to the AP at Purdue? The 4311's don't broadcast with
>> much power and you might not
>> be in reach. I'm also not sure about the ap_scan=2 in your .conf file.
>> Please try a value of 1.
>>
>> One other thing to test. Once the system is trying to authenticate, do
>> an 'iwlist s' command to see
>> if any scans are getting through. It doesn't seem as if they are, but
>> this is another way to see.
>
> In order to get around the (possible) transmit power problem, I set my
> own AP to have a hidden SSID, and it's currently sitting about 1 meter
> from the laptop.
>
> I've been skimming through the wpa_supplicant source code to try to
> get a handle on what's going on. When ap_scan is set to 1,
> wpa_supplicant will walk through all of the entries in the config file
> that have "scan_ssid=1" set. For each of these SSIDs, it tells the
> driver to scan for that specific SSID, and when the results come back,
> it compares each resulting SSID with the SSID that it was originally
> scanning for, looking for an exact string match.
>
> So, it looks like it's the driver's job to scan for a specific SSID,
> and insert its name into one of the fields that would ordinarily be
> "<hidden>". The problem is, even after scanning for a specific SSID,
> the results from the driver never contain the SSID that we searched
> for. In the debug output for wpa_supplicant, I see:
>
> 0: 00:16:01:11:42:11 ssid='<hidden>' wpa_ie_len=26 rsn_ie_len=22 caps=0x11
> skip - SSID mismatch
>
> That's definitely my access point, but as you can see, the driver
> never inserted the correct SSID.
I will inquire what the software should insert when the SSID is hidden. The
piece of code that
inserts the "<hidden>" is ieee80211, which is not part of bcm43xx-softmac, but
was written by Intel
and is used by a number of drivers besides bcm43xx.
My system is working with the SSID hidden and the following conf file for
wpa_supplicant. It can
take a long time to authenticate as the scan doesn't always find the AP. That
is probably a problem
with the driver.
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
network={
scan_ssid=1
ssid="lwfdjf"
key_mgmt=WPA-PSK
psk="<removed>"
}
Larry
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
