Re: Restricted mode not working with MA101, kernel 2.6.5, driver 0.12 from cvs

Hi Alexander,

On Wed, 28 Apr 2004, Alexander Steppke wrote:

> Hi,
>
> for upgrading my kernel to 2.6.5 I got the latest drivers from cvs.
> With my old configuration from the 0.11 driver it was not possible to
> connect to the AP.
>
> The device is configured like this:
>
> wlan0     IEEE 802.11-DS  ESSID:"craven"  Nickname:"okuwlan"
>           Mode:Managed  Channel:1  Access Point: 00:00:00:00:00:00
>           Bit Rate:11Mb/s   Tx-Power=15 dBm
>           Retry limit:8   RTS thr:off   Fragment thr:off
>           Encryption key:my-key-here   Security mode:restricted
> ...
>
> Enabling the debugging showed that the card tries to connect but is not successful:
> ...
> I rechecked everything and changed the security mode from "restricted" to "open" and the card works now perfectly.
> With the old 0.11 driver "restricted" worked without problems. Is this a bug?

> My access point is configured for restricted connections (it is a Cisco
1100).

What does this mean (WEP on/off, MAC filter, open system / shared secret
authentication or cloaked SSID or ...)?

> It took me several hours to get my internet connecting
> working with this problem and I want to say thank you very much for the
> great support manual on the website and of course for the driver.

With 0.11 the shared secret authentication mode was
choosen by "iwpriv wlan0 auth_mode 1" while "iwconfig wlan0 encr XXXXXX
restr" only said that the client should drop received unencrypted data
packets.
To be consistent with the iwconfig description
"iwconfig wlan0 encr XXXXX restricted" now only switches the
authentication method. If WEP is configured all received unencrypted
packets are dropped (which may change in the future for WPA / 802.1x). In
your case it seems you used shared secret authentication and
your AP isn't configured for.

/Jörg