[driverloader] intel 2100 not working
Anders Karlsson
anders at trudheim.com
Sat Nov 8 12:37:36 EST 2003
On Sat, 2003-11-08 at 11:53, Fritz Ganter wrote:
> Am Sam, den 08.11.2003 schrieb Sven Westenberg um 07:42:
> > Don't know if this helps. We also had problems connecting to the AP with
> > encryption enabled. The Intel support just told us "optional encryption
> > is not supported". So optional encryption on the AP is not recognized as
> > WEP encryption by the 2100 pro wireless chip. Try to set the AP to allow
> > non encrypted connections and disable the encryption of the interface.
> This is nonsense.
> I have the Intel 2100 working in my notebook with 128 (104) bit
> encryption. it works fine.
I will have to do more testing, but it appears that I also have it
working at the moment. (DL v1.33)
> Please make a "iwconfig" and see if your key is set (you must be root to
> see the key).
It was set all the time, but would still not talk to the AP.
> Some days ago I had the same problem, but this was an issue of the
> iwtools from SuSE 8.2. With this version I was unable to set the key.
I updated the tools as well, but not for this reason.
> I have downloaded wireless-tools version 26, now it works.
>
> Maybe this should be mentioned in the FAQ.
Also something to mention in the FAQ would be that DriverLoader and
Intel PRO/2100 does not support channel 12 and 13 (Europe Only
Channels). Marc Boucher suggested me trying Channel 11 on the AP, and
with the AP in auto mode (allowing both encrypted and non-encrypted
packets) the whole mess is now actually working. (Still some testing to
do.)
Regards,
--
Anders Karlsson <anders at trudheim.com>
Trudheim Technology Limited
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://www.linuxant.com/pipermail/driverloader/attachments/20031108/e5d1b9a6/attachment.bin
More information about the driverloader
mailing list