[driverloader] intel 2100 not working

[Linuxant support]

Hi,

DriverLoader supports all the channels. The limitation comes from some NDIS 
drivers and adapters that do not allow transmission and/or reception on 
channels 12 to 14.

In general, WEP problems can be fixed by one or a combination of these...

1) Use the latest release of DriverLoader.

2) Make sure the AP uses the same WEP settings as the adapter. Sometimes it is 
necessary to force "open" or "restricted" mode on both the AP and the 
adapter.

3) Upgrade the NDIS driver. You might even need to use a Windows XP driver 
from another vendor if it is newer and modify the INF file to add your 
adapter's PCI ID (e.g. Belkin usually supplies the latest driver for Broadcom 
based cards).

4) Upgrade wireless-tools.

5) Upgrade the AP's firmware.

If all of the above is unsuccessful, you can still report the problem to us 
and we might find a solution.

Regards,

Jean-Simon Durand
Technical specialist / Linuxant
www.linuxant.com
support at linuxant.com



On Saturday 08 November 2003 07:37, Anders Karlsson wrote:
> On Sat, 2003-11-08 at 11:53, Fritz Ganter wrote:
> >
> > 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