ELSA MC-2 Linux Driver
This is an open source linux driver for the ELSA MC-2 PCMCIA WLAN
card and the Siemens I-Gate M2, which is a re-labelled MC-2.
As this card is very similar to the ZCOM WL2430 chances are
that this driver works with it, too, or might be adapted in the future.
Requirements
You need a Linux kernel
2.2.x or 2.4.x and a recent
pcmcia-cs package
(3.1.x should be sufficient). If you use kernel PCMCIA
instead, you must manually copy the sources and adapt the make files.
Downloads
The latest version is
Version
1.52
Check the News for known bugs.
Firmware Versions
The latest official firmware version is 2.06.
Currently the linux driver does not support firmware updates, you
must update the firmware with an
(I)L-2 or under Win9x or NT4 using
these programs.
Version 2.06 contains a bug which won't let the card log into Agere access
points in closed network mode.
There is an unsupported beta version 2.10 available, in a
format to be used by WLU.EXE under Win (see below) and in a
format usable in an (I)L-2.
For an update under Win, the necessary steps are:
- download the
firmware and rename it giving it a .bin extension.
- download either
AirLancer_MC-2_FWupdate9X.EXE (Win9x),
AirLancer_MC-2_FWupdateNT4.ZIP (NT 4) or
AirLancer_MC-2_W2K.ZIP (W2K),
unpack it if necessary and execute AirLancer_MC-2_FWupdate9X.EXE
or WLU.EXE, while the MC-2 is inserted.
- click on Upgrade Firmware.
- choose the correct firmware file downloaded in the first step
- click on UPGRADE. The firmware is loaded into the card.
- choose EXIT
If you own an (I)L-2 access point, you
can alternatively update the inserted PC Card with this unsupported
firmware using the file
LC_AL2u.210.
Sniffing the Air
If the MC2 doesn't work in your environment or has a bad throughput
and you have double checked your settings, the syslog messages and
routing tables, a trace of the packets in the air could help a lot in
analysing your problem. Please check legal restrictions, which may
forbid scanning air traffic in your country!
You need:
- A recent version of ethereal,
which supports IEEE802.11 and Prism packet formats.
- A Prism2 based PC Card or USB adapter and the Linux wlan-ng
driver (version 0.1.15 worked for me) - go here for
both a device list and the driver. The device table on this page is
outdated, check the driver source if in doubt.
Alternatively a Orinoco PCMCIA card with orinoco_cs.o is usable, but
may require a patch for the driver and does not, AFAIK, provide
Prism header information.
Install ethereal and the device driver on the computer which shall
trace the traffic. Set the WLAN device into monitor mode, e.g. for
wlan-ng (where X is the channel number of the access point or
the adhoc station):
wlanctl-ng wlan0 lnxreq_wlansniff enable=true channel=X
prismheader=true keepwepflags=true
Now ethereal shall be able to record all packets, including management
packets on this interface.
News
- 16.02.2003: 1.53beta2: fixed a bug in adhoc mode
when the MC-2 started the IBSS. In this case all data packets
(arp, ping) were dropped by some peers (e.g. ATMEL AT76c503
USB adapter with firmware 0.100.x), because the MC2 used a
BSSID of all zeros in address3 field. This bug was present since
version 1.51 (incl.).
- 04.02.2003: fixed two bugs with WEP flags:
- when encryption in restricted mode was shut off,
unencrypted packets were still ignored
- encrypted packets were excepted even if no encryption
was configured
- 02.02.2003:
Version
1.52 released
(see our CVS):
- 25.01.2003: fixed compiler errors with kernel 2.2.13
- 11.01.2003: added conf entry for the Siemens I-Gate M2
- 05.01.2003:
- added support for sharing interrupts
- added debug output of module parameters at startup
- iwconfig will be able to set rate auto
- 10.12.2002: fixed bug in leaky bucket handling (forgot to stop
the netif leading to MdCfm with status 1).
leaky bucket does not count MdCfm with status 2 (Fail)
- 07.12.2002: added re-assembling of fragments on RX, fixed bug
in initialization of leaky buffer counter for failed
MdCfm, increased this threshold
- 26.11.2002: driver did not use WEP if the access point
(Agere) was configured for optional WEP -
fixed (use cvs tar ball)
- 06.11.2002: version 1.51 still doesn't work with Agere access
points. If you encounter problems in joining APs in closed
network mode, try the latest cvs tar ball.
- 04.11.2002:
Version
1.51
(see our CVS):
- merged 1.43 and 1.50
- WEP support was added in 1.50 (firmware >= 2.06 needed !)
- supports Belkin access points in closed network mode
- supports Agere access points in closed network mode
if firmware >= 2.10 is used
- 28.10.2002: Version 1.43
(see our CVS):
CVS Tar Balls
If you want to use one of the
cvs tar balls
you should call
make -f wl24n_cs.mk dist in the mc2 directory and unpack
the resulting tgz file into the pcmcia-cs root directory as described
in the README.wl24n file.
More Info
Closed Network Mode
So-called closed network or cloaked mode in the access points aims at
suppressing the SSID in the beacon transmission. It seems to be an
non-standarized feature. I try to collect a
list of implementations
for different access points. If you have more information or
experience problems with that mode, please drop me an email to
containing the AP's name, configuration and some syslog showing the ScanCfm lines
from /var/log/messages.
Contact, Feedback and Support
Just use the following mailing-lists:
or the project's forums.
Links
Tested Configurations
to be filled (in which configurations does it work)
Haftungshinweis: Trotz sorgfältiger inhaltlicher Kontrolle
übernehme ich keine Haftung für die Inhalte externer Links.
Für den Inhalt der verlinkten Seiten sind ausschließlich
deren Betreiber verantwortlich.
© 2003 by Jörg Albert, last update 13.06.2003
All rights reserved. All trademarks are the property of their respective owners.