+ PCMCIA-USB bridge on ezusb chipset.
-91 dBm at 2 Mbps
-87 dBm at 5.5 Mbps
-82 dBm at 11 Mbps
-84 dBm at 11 Mbps
(page requires free registration)
(page requires free registration)
You must know, that there are 2 variants of ORiNOCO USB device: variant 1 and variant 2. This page will be only usable for variant 1 users, variant 2 users bets are off. Why? Please take 2 minutes to see the difference :-)
| x | Variant 1 | Variant 2 |
| Image | |
|
| Age | Old variant | New variant |
| Output Power | 15 dBm | 13 dBm |
| Partiality | Original Lucent ORiNOCO Classic Gold / Silver PCMCIA + PCMCIA-USB bridge on ezusb chipset. |
Single board, no PCMCIA inside |
| Chipset | Hermes-I (original ORiNOCO Classic card inside) | Intersil Prism II |
| Outdoor antenna connector | After removing cover (or drilling hole in it) you can use PCMCIA MCCARD connector to connect external antenna (but warranty will be void). | No outdoor antenna possibility. |
| Size | The same size. | |
| Voltage | 5 Volt due to ORiNOCO Classic PCMCIA 5 Volt inside | 3.3 Volt |
| Sensitivity | -94 dBm at 1 Mbps -91 dBm at 2 Mbps -87 dBm at 5.5 Mbps -82 dBm at 11 Mbps |
-88 dBm at 2 Mbps -84 dBm at 11 Mbps |
| Channels | 11, 13 or 14 | |
| Channel count changing | Easy (there is program to do it) | Probably difficult, Alchemy doesn't work with Intersil Prism cards. |
| Linux support | Yes (orinoco-usb drivers) - works with Kismet with 6.16 firmware. | Not working with orinoco-usb, support unknown. |
| WEP | Yes | |
| WPA | Yes (on Agere SR-03 drivers on Windows) | No |
| Fixed data rate | Not possible (only automatic con trolled by firmware) | Possible to set data rate, also automatic |
| Measurement signal and noise in dBm | Yes, full Netstumbler support (due to ORiNOCO Classic card inside) - noise and signal in dBm | Values shown in %. In Windows XP there is Netstumbler hack for Prism-based cards for dBm values, but this card is not "supported". |
| Possibilities of ORiNOCO Classic Card | All possibilities + USB connector. You can pull PCMCIA card from PCMCIA-USB bridge and use it in PCMCIA slot in laptop or PCI-PCMCIA adapter. This card use the same Client Manager that ORiNOCO Classic card. | Completely different card. |
| URL: | http://support.proxim.com/cgi-bin/proxim.cfg/php/enduser/popup_adp.php?p_faqid=1082 (page requires free registration) |
http://support.proxim.com/cgi-bin/proxim.cfg/php/enduser/std_adp.php?p_faqid=1311 (page requires free registration) |
Now you should see why this page is only about Variant 1 of this card :-) Variant 2 users please go here for stuff for you:
http://support.proxim.com/cgi-bin/proxim.cfg/php/enduser/std_adp.php?p_faqid=1311 (page requires free registration)
You can find here drivers, readme, users manual and quick start guide.
Under the cover this card looks like here (my own photo):
ORiNOCO Classic Card was invented and primary developed by Lucent Technologies. Then, Lucent was merged to Agere and the ORiNOCO brand was supported and developed by Agere Systems. Next, Agere sold ORiNOCO brand to Proxim and for a long time this card was sold and supported by Proxim. Now this card is no longer developed or sold, but Proxim still is providing support for it. You can still download old drivers and software from Proxim website. After selling ORiNOCO brand to Proxim, Agere still developed firmware and software for ORiNOCO cards for a little time. Agere was sold to LSI, so now you can download the latest drivers and software from LSI webpage (what is the best solution).
You must know, that ORiNOCO (Hermes-I), Prism 2, Prism 2.5 and Symbol cards are electrically almost the same! The difference between these cards are firmware and other flashable / programable areas. But these areas program voltage and other critical functions, so these brands of cards behave quite different. Also ORiNOCO brand on 6.16 and 9.42 or 8.72 firmware behaves different. But also you should know, that interface for firmware is very similar, so drivers for ORiNOCO and Prism devices are quite similar. For example one linux driver orinoco_cs supports ORiNOCO, symbol and prism cards - only some functions are different and demand different code.
Officially Proxim now supports ORiNOCO cards. But you know, that Proxim didn't create any of ORiNOCO components, so possibly better place for questions will be Lucent or Agere. I checked them both. Let's start!
1. Lucent
Contact with Lucent Technologies is now impossible. There is no e-mail address on Lucent's site - the only way to contact is using very hard to fill form. After filling this form you must write down you Lucent transaction ID, etc, etc - there is no possibility to contact. Also Lucent write on his page, that ORiNOCO products is NOT supported by Lucent anymore.
2. Agere
Contact with Agere is possible, but Agere's supporters will not tell you anything. This is answer to my e-mail about ORiNOCO product:
===8<==================================================================
Agere
Systems sold their ORiNOCO product line to Proxim. Please contact
Proxim for
further assistance.
PROXIM: Phone: 1-866-674-6626 or 1-408-731-2700
Site: http://www.proxim.com <http://www.proxim.com/>
Thank
you.
Agere Response Center
1-800-372-2447
===8<==================================================================
And this is answer of Agere to my question about AGERE Wireless USB Card Model 0801 (Vid_0D4E&Pid_1000) - this is Agere branded ORiNOCO card (only label is different, card is ORiNOCO):
===8<==================================================================
We cannot provide you with the information you seek. We apologize for
any
confusion.
Best Regards,
Agere Systems
===8<==================================================================
So, formally you should normally contact Proxim for ORiNOCO cards (and for Agere branded cards NO support is available). But.... read next paragraph.
3. Proxim
Contact with Proxim is always fast and accurate. But knowledge of Proxim supporters and cooperation possibilities are horrible inaccurate....
Please read some conversation between me and Proxim support (from top to down, personal details are replaced with "xxx"):
| Customer (XXX) | 03/12/2005 06:18 AM |
| Unfortunately it has got only 11 channels. Does
anybody know how can I enable 12, 13 (and maybe 14 channel)? Could
somebody tell me how to do it? Problem is with the firmware from PCMCIA
card - I can flash it in PCMCIA slot - somebody know how? In my country I
may use all 14 channels, but how? Best regards. | |
| Response (YYY) | 03/25/2005 10:33 AM |
| Hello XXX Unfortunately there is no way to add the last three channels, it sounds like you have the US version of the USB client, because the US only support 11 channels there is no way to modify that. Thank you | |
| Customer (XXX) | 03/13/2005 10:36 AM |
| Now I don't want support :-) I cracked PDA of this card by Alchemy, set 14 channels and flashed the card by new firmware from Proxim. This took a lot of time, because I had to crack Proxim drivers and Proxim firmware updater (change Product ID and Vendor ID inside drivers and firmware to these from my card). Please allow users to easily flash all cards, cracking drivers and firmware isn't problem for me, but for usual users it is... And usual users will not be able to rework this card for 14 channel support... | |
| Response (SSS) | 03/13/2005 08:48 PM |
| Dear XXX, Thanks for replying back. I appreciate your valuable attempt to find resolution for this issue. I request you to please share some of your workarounds with the issue so that we can update our information on the matter. Regards, SSS Proxim Technical Support | |
and this part (Proxim support couldn't recognize his card model):
| Customer (XXX) | 03/06/2005 01:36 PM |
| Hello, I bought an ORiNOCO USB Gold (or other such device)- (this is ORiNOCO Gold PCMCIA + integrated USB adapter). I bought it without drivers - CD and without documentation. And I have got many problems with this card. There was no drivers provided with this card, so I had to download it. I downloaded and installed these drivers: http://www.lsi.com/obsolete/wireless_lan.html Serial number: ------------------------- 02UT19415453 ------------------------- Caption from my card box: ----------------------------------------------------------------- Product description: 017803/B Wireless USB Client, 128RC4, World Card (kit) COMCODE: 700002495 Made in Taiwan ------------------------------------------------------------------ At the bottom of the card I can see: ------------------------------------------------------------------ Wireless USB Client Lucent Technologies Contains Transmitter Radio Type PC24E-H-FC FCC ID: IMRWLPCE24H MAC: 00-02-2D-5F-5B-25 ----------------------------------------------------------------- Under linux after "lsusb" I can see following: ----------------------------------------------------------------- Bus 002 Device 003: ID 0d4e:047a Agere Systems Netherland BV ------------------------------------------------------------------ Log from Wireless Client Manager: -------------------------------------------------------------------- - - - - - - Wireless network card Diagnostics Log - - - - - - - - This log file identifies the version level of the various Wireless network card components and systems settings of your computer. Please include this log file with every support request to your Wireless Technical Support Representative. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Date: 2005/03/05 18:41:44 OS: WIN2001 Version 5.01 Service Pack 1 Build 2600 Variant 1, Version 3.30 of Client Manager Variant 2, Version 7.82 of NDIS 5 USB driver Variant 1, Version 1.02 of USB Card Variant 3, Version 4.02 of WLAN USB Card Encryption capabilities: WEP + 128RC4 Max. data rate: 11 Mbit/s 02UT19415453 Variant 1, Version 1.02 of USB Bootloader Variant 1, Version 4.04 of Primary Functions firmware Variant 2, Version 9.42 of Station Functions firmware - - - - - - - - - - - - - - End of File - - - - - - - - - - - - - - -------------------------------------------------------------------------- I connected after removing cover to PCMCIA card external MCCARD/RPSMA connector and then an antenna. My problem is: With card Planet WL-8305, Netstumbler and Wireless Client Manager displays about 30 networks. With this ORiNOCO card I can see only 3 networks with WiFi Manager from Agere Systems (and in Netstumbler also only 3)... This WiFi Manager correctly reports signal, noise and SNR (-72/-92/20) dB. I checked and on these drivers my card didn't show any AP with active MAC filtering! Netstumbler and my software to ORiNOCO card do not show any AP which use MAC filtering! It could be stupid, but even in my desk I can put AP and it is showed by my card drivers. Then I select MAC filtering and what? Any software (also NS) do not report this AP. Whets up? Is it correct? In wl-8305 I don't have this problem... Very strange! Can you tell me what card I have got? What chipset? Maybe not ORiNOCO? Can you tell me which drivers should I install to install this card properly? Thanks! Answer please at address xxx@host.com Sorry for my English and many thanks for help! | |
| Response (SSS) | 03/11/2005 01:13 AM |
| Dear XXX, Thank you for contacting Proxim Technical Support. My name is SSS & I will be handling your enquiry. This USB device is only available with Windows support. The wireless card inside the USB comes with hermis2 chipset, which is said to be compatible with LINUX. We do have drivers for Linux for this card which you can download from the link given below. Apart from this I regret to inform you that we do not support Linux configurations. http://www.proxim.com/support/all/orinoco/software/dl2002_orinoco_linux_pccard_v616.html Regards, SSS Proxim Technical Support | |
| Customer (XXX) | 03/12/2005 04:26 AM |
| No, no, no, no :-) This USB device is fully compatible with Linux! I installed it properly without any problem - all features like signal and noise provided in dBm is working correctly in Linux - values are the same as in Windows! First of all I don't agree that the card is on Hermes-II chipset - this card is on Hermes-I chipset! Your Windows utility says that this is Hermes-I chipset. Netstumbler report it as Hermes-I chipset, Linux also... Here you can get working drivers for usb device (code from cvs only): http://www.nongnu.org/orinoco/ My device product id / vendor id is listed here as: "IBM Internal High Rate Wireless LAN PC Card 26P8030 (0x0d4e/0x047a)" on page: http://folk.uio.no/oeysteio/orinoco-usb/ Here is HOWTO install this device: http://folk.uio.no/oeysteio/orinoco-usb/install.html So this card is Hermes-I and it working very well on Linux with USB. Unfortunately "monitor mode" isn't supported, so Kismet is not working. Can you tell me which WINDOWS programs allows me to monitor my network in MONITOR mode (card is gathering packets from all wireless networks)? It can be free or commercial (even expensive) product. Thanks! | |
So, you know: Proxim Support is good for conversation, not for support :-)
ORiNOCO Classic PCMCIA and ORiNOCO USB variant 1 were sold with different names. If you can recognize your ProductID or VendorID (listed for example by Linux by lspci or lsusb), you have got ORiNOCO USB variant 1 with ORiNOCO Classic PCMCIA inside:
Wireless USB Card Model 0801 (Vid_0D4E&Pid_1000)
Wireless USB Card
Model 0802 (Vid_0D4E&Pid_1001)
Avaya Wireless USB Card
(Vid_0D98&Pid_0300)
Avaya Wireless USB Card
(Vid_0D9E&Pid_0300)
BUFFALO Airstation USB
(Vid_0411&Pid_000B)
BUFFALO WLI-USB-L11 Wireless LAN Adapter
(Vid_0411&Pid_0006)
BUFFALO WLI-USB-L11G Wireless LAN Adapter
(Vid_0411&Pid_000D)
ELSA AirLancer USB-11
(Vid_05CC&Pid_3100)
Joynet WLAN USB Card
(Vid_0E7C&Pid_0300)
ORiNOCO USB Card (Vid_047E&Pid_0300)
Samsung
SEW-2001u Card (Vid_04E8&Pid_5002&Rev_0000)
Samsung SEW-2001u Card
(Vid_04E8&Pid_5B11)
Samsung SEW-2003U Card
(Vid_04E8&Pid_7011)
I-GATE 11M USB Card
(Vid_0681&Pid_0012)
connect2AIR WLAN E-1100 USB
(Vid_0BF8&Pid_1002)
2Wire Wireless USB adapter
(Vid_1630&Pid_FF81)
WLAN USB Card (Vid_0D4E&Pid_047A)
Compaq WL215
USB Adapter (Vid_049F&Pid_001F)
Compaq WL215 USB Adapter
(Vid_049F&Pid_0082)
Compaq W200 USB Adapter (Vid_049F&Pid_0076)
Be careful, because some drivers / firmware updaters, etc do not accept cards with different ProductID or VendorID than expected. So, there is one useful hack to install any driver for any card and flash any firmware, etc, etc. You could also use semi-universal driver (but with no possibility to flashing firmware). How to do it? Read "Drivers" paragraph :-)
Sensitivity of ORiNOCO Classic Card (so also ORiNOCO USB) is described in table above. My own experience is the following:
Stable work with stable data rate (could be 128 kbps or other granted in router) is possible when received signal is -89 dBm or higher (it could jump to min -90 dBm) - if it jumps to -91 dBm or -92 dBm and it is sharpened, outgoing data rate is still high (for example 600 kbps), but download is very unstable (0-128 kbps with jumping rate).
My own observation in 3000 meters distance with no optical visibility and Yagi 20 dBi with 8 meters of H-155 + 2 RP-SMA connectors + pigtail MCCARD-RPSMA, on the second side Entarasys (ORiNOCO). SNR ~ 15 dB from each partner.
Due to small output power (15 dBm) many more APs I can discover with Planet WL-8305 card using Netsumbler and Windows utilities. Kismet and Linux utilities using passive scanning can discover all APs in range. With WL-8305 card I also notice always smaller packet loss than on ORiNOCO card. For example in situation when ORiNOCO shows SNR = 23 dB, Planet WL-8305 shows Signal = 76% (on the same antenna), the packet loss on ORiNOCO (ping 1200 bytes) is about 15% compared to 3% on WL-8305. Old drivers to WL-8305 cause 18 dBi gain, the newest cause 20 dBi gain on this card, so the difference to ORiNOCO is about 5 dBi (4*stronger signal). Linux driver for WL-8305 could get even 22 dBi gain for this card. So for desktop use I recommend Planet WL-8305 cards (sensitive and strong) for small distance and ORiNOCO card for notebooks and laptops. For longer distance (1000 meters and higher) I recommend ORiNOCO cards - the best cards for long distances that I know.
All ORiNOCO Classic Cards are technically identical!
PDA - it is a programmable area of card memory, which decides about card's possibilities. By modifying PDA you can change:
a) encryption possibilities;
b) MAC address;
c) serial number;
d) available channels (11, 13 or 14);
e) company code (but NO Pid or Vid);
f) many more.
If you would like to change some cards possibilities, you must use alchemy.
Alchemy you could run also with USB adapter - you do not need to pull card out from USB adapter! After running alchemy to apply your modifications you must flash firmware. You could flash the same version of firmware as you have, newer or older - but you must do it. Simply settings from PDA's are integrated with firmware when you are flashing firmware, in other time PDA is not used at all. Please remember it!
If you would like to use Alchemy, you should use card with original drivers from Proxim (cracked or not). If you will use Alchemy with different drivers (e.g. from Agere), you could see information about corrupted PDA or something else! Read "Drivers" section to learn how to use original Proxim drivers with your ORiNOCO card!
Original, 14 channels PDA for users with corrupted PDA (this PDA could be flashed with Alchemy): ORiNOCO PDA.
Example, how to change count of available channels from 11 to 14 (log from my modifications):
==========================================================================================================
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft
Corp.
D:\orinoco_cd\alchemy>alchemy
Lincomatic Alchemy 1.00 (Apr 30
2004 10:20:08)
Copyright (c) 2004 lincomatic ALL RIGHTS RESERVED
0:
WLAN USB Card
1: MAC Bridge Miniport
2: Enter driver name
3: Abort
program
WARNING: the list above may contain non-ORiNOCO adapters
SELECTING
A non-ORiNOCO ADAPTER MAY DAMAGE IT!!!
Select an ORiNOCO adapter (0-3):
0
Driver name: {71FA7E78-68CA-48F8-9BBE-D508FC8FFA8D}
Driver
\\.\{71FA7E78-68CA-48F8-9BBE-D508FC8FFA8D} opened successfully
driver
connection handle: 820062c0
Reading
PDA...
--------------------------
Original PDA
0001(08): 4130 3135 3330
3441
0002(08): 3234 5432 3231 3733
0003(0c): 3032 5554 3139 3431 3534
3533
0004(78): 0000 0000 FA67 A340 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000
0005(0a): 0000 0600 0100 0200 0200
0006(0a): 0000 0100 0100 0300
0300
0007(0a): 0000 0200 0100 0600 0600
0008(08): 0100 0300 0400
0200
0010(1c): 1120 EE20 2220 3320 441F 551D 661F 7723 8825 9925 AA24 BB21
CC20 DD20
0020(1c): 116B EE6A 2267 3364 4461 555E 665D 775D 885C 995B
AA5B BB5B CC5D DD60
0030(1c): 1152 2252 3352 4452 5552 6652 7752 8852
9952 AA52 BB54 CC54 DD54 EE55
0040(04): 0008 0008
0101(06): 0002 2D5F
5B25
0102(08): 0000 0000 0000 0000
0103(0c): 0600 1020 3031 3241 0000
0000
0104(02): FF07
0105(02): 0A00
0106(02): 0000
0107(02):
0100
0108(04): D170 4C5C
0109(0a): 0329 0300 2B00 0000 0000
0110(1c):
2013 2013 2013 1F13 1D13 1F13 2313 2513 2513 2413 2113 2013 2013
2013
0120(1c): 6B12 6712 6412 6112 5E12 5D12 5D12 5C12 5B12 5B12 5B12
5D12 6012 6A12
0130(1c): 5244 5244 5244 5244 5244 5244 5244 5244 5244
5244 5444 5444 5444 5544
0140(04): 0842 0843
0000(02):
89BF
--------------------------
Change advanced PDA settings? (y/n)
y
Read PDA from binary file? (y/n) n
Serial Number: 02UT19415453
Change
Serial Number? (y/n) n
Mac Address : 00-02-2d-5f-5b-25
Change Mac Address?
(y/n) n
Channels (07ff): 1 2 3 4 5 6 7 8 9 10 11
Change allowed channels?
(y/n) y
WARNING: CHANGING THE ALLOWED CHANNELS MAY MAKE YOUR CARD ILLEGAL IN
YOUR REGULA
TORY DOMAIN
Enter new channel mask (e.g. 07ff =
1-13):
3fff
New allowed channels (3fff): 1 2 3 4 5 6 7 8 9 10 11 12 13
14
Current manufacturer code (0=Lucent/Agere): 29
Change manufacturer
code? (y/n) n--------------------------
Patched PDA
0001(08): 4130 3135
3330 3441
0002(08): 3234 5432 3231 3733
0003(0c): 3032 5554 3139 3431 3534
3533
0004(78): 0000 0000 FA67 A340 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000
0000
0005(0a): 0000 0600 0100 0200 0200
0006(0a): 0000 0100 0100 0300
0300
0007(0a): 0000 0200 0100 0600 0600
0008(08): 0100 0300 0400
0200
0010(1c): 1120 EE20 2220 3320 441F 551D 661F 7723 8825 9925 AA24 BB21
CC20 DD20
0020(1c): 116B EE6A 2267 3364 4461 555E 665D 775D 885C 995B
AA5B BB5B CC5D DD60
0030(1c): 1152 2252 3352 4452 5552 6652 7752 8852
9952 AA52 BB54 CC54 DD54 EE55
0040(04): 0008 0008
0101(06): 0002 2D5F
5B25
0102(08): 0000 0000 0000 0000
0103(0c): 0600 1020 3031 3241 0000
0000
0104(02): FF3F
0105(02): 0A00
0106(02): 0000
0107(02):
0100
0108(04): D170 4C5C
0109(0a): 0329 0300 2B00 0000 0000
0110(1c):
2013 2013 2013 1F13 1D13 1F13 2313 2513 2513 2413 2113 2013 2013
2013
0120(1c): 6B12 6712 6412 6112 5E12 5D12 5D12 5C12 5B12 5B12 5B12
5D12 6012 6A12
0130(1c): 5244 5244 5244 5244 5244 5244 5244 5244 5244
5244 5444 5444 5444 5544
0140(04): 0842 0843
0000(02):
0397
--------------------------
Write new PDA to card? (y/n) y
Writing
new PDA...
Gold PDA successfully updated
press a key to
exit
D:\orinoco_cd\alchemy>
==========================================================================================================
How to flash firmware? Read corresponded paragraph of this article :-)
Other corresponded links about changing PDA:
http://www.maco.sk/wireless/orinoco/hack/howto-14-channels.html
http://www.nervous.it/hw/dlink_dwl660_orinoco.html
http://www.andrewhakman.dhs.org/orinoco/
ORiNOCO Classic PCMCIA card inside USB adapter contains standard MCCARD external antenna connector. Moreover, PCMCIA card contains its own internal antennas under PCMCIA cover, which are good when operating in nearness of an access point. If you put external antenna connector to MCCARD slot, internal antenna is automatically disconnected, even if the signal from internal antenna is much greater than the signal from external antenna! To get antenna connector more suitable I recommend adding MCCARD-RPSMA pigtail, so you can then screw any antenna with RPSMA connector (like for WL-8305 and many APs). This MCCARD-RPSMA pigtail looks like (photo from "Pluscom" - Polish WLAN shop):
|
To connect an antenna to the PCMCIA you must unfortunately remove temporary USB cover (warranty will be voided...) and then drill the hole in the cover to put through this pigtail. This is very good solution to extend range of this card.
How to remove the cover? Simply unstick the rubber mat at the bottom of the USB card. There are 4 fasteners under it - you must lever up them and remove the bottom plastic cover of USB card and the upper plastic cover. Look at the pictures (from http://www.wirelesslan.com.pl):
In Windows you could use different drivers. Windows drivers aren't developed from many years and slowly official pages abandon supporting ORiNOCO, so I decided to copy the drivers and Client Manager to my server and give you all the information here (also about drivers for MS-DOS and Mac OS). Which are best for you?
- URL: http://support.proxim.com/cgi-bin/proxim.cfg/php/enduser/popup_adp.php?p_faqid=1082 (page requires free registration)
- official drivers for Windows XP (PC Card & USB)
- official drivers for Windows 2000 (PC Card & USB)
- official drivers for Windows ME (PC Card & USB)
- official drivers for Windows 98 (PC Card & USB)
- official drivers for Windows CE (PC Card only 2.x, 3.x, 4.x)
- official drivers for Windows NT (PC Card only)
- official drivers for Windows 95 (PC Card only)
- official drivers for MS-DOS (PC Card only)
- official drivers for Mac OS (PC Card only)
- official Client Manager for Windows 98/ME/2000/XP (PC Card & USB)
- official firmware version 8.72
- drivers contain 8.72 version of firmware
- DO NOT support WPA
- Client Manager DO NOT support Windows XP (you must use Wireless Zero Configuration) - SP2 strongly recommended
- In Windows XP NO "Work as Access Point" mode available
- ONLY this version of drivers is working with firmware updaters - if you would like to update the firmware, you MUST use this version of drivers. Also use this version when you use Alchemy
- Formally only 1 card is supported: ORiNOCO USB Card (Vid_047E&Pid_0300) - if you would like to use other card with this driver (for example to update firmware), you must use one safe and trivial hack - read down how to do it
- URL: http://www.lsi.com/obsolete/wireless_lan.html
- the latest Agere drivers for Windows 98/ME/2000/XP (PC Card & USB)
- the latest Agere drivers for Windows CE (PC Card only 2.x, 3.x, 4.x)
- the latest Agere Client Manager for Windows 98/ME/2000/XP (PC Card & USB)
- drivers contain 9.42 version of firmware
- WPA support. To enable WPA you must disable Client Manager and use Wireless Zero Configuration on Windows XP, or free WPA supplicant on other operating systems (Win98 SE, NT4, W2k)
- Client Manager supports Windows XP
- Client Manager supports "Act as Base Station" mode
- these drivers DO NOT work with firmware updaters and should NOT be used with Alchemy
- included support for next brands of cards:
Wireless USB Card Model 0801 (Vid_0D4E&Pid_1000)
Wireless USB Card
Model 0802 (Vid_0D4E&Pid_1001)
Avaya Wireless USB Card
(Vid_0D98&Pid_0300)
Avaya Wireless USB Card
(Vid_0D9E&Pid_0300)
BUFFALO Airstation USB
(Vid_0411&Pid_000B)
BUFFALO WLI-USB-L11 Wireless LAN Adapter
(Vid_0411&Pid_0006)
BUFFALO WLI-USB-L11G Wireless LAN Adapter
(Vid_0411&Pid_000D)
ELSA AirLancer USB-11
(Vid_05CC&Pid_3100)
Joynet WLAN USB Card
(Vid_0E7C&Pid_0300)
ORiNOCO USB Card (Vid_047E&Pid_0300)
Samsung
SEW-2001u Card (Vid_04E8&Pid_5002&Rev_0000)
Samsung SEW-2001u Card
(Vid_04E8&Pid_5B11)
Samsung SEW-2003U Card
(Vid_04E8&Pid_7011)
I-GATE 11M USB Card
(Vid_0681&Pid_0012)
connect2AIR WLAN E-1100 USB
(Vid_0BF8&Pid_1002)
2Wire Wireless USB adapter
(Vid_1630&Pid_FF81)
WLAN USB Card (Vid_0D4E&Pid_047A)
- if you would like to use other card with this driver (for example to update firmware), you must use one safe and trivial hack - read down how to do it.
For normal usage, use Agere drivers. For firmware updates and using Alchemy use Proxim drivers.
If you have got Hermes-I based card, but not supported natively by driver, you can hack the driver. It is very useful when you want to flash firmware, but with Proxim drivers only ORiNOCO USB Card (Vid_047E&Pid_0300) is supported. For example we have got WLAN USB Card (Vid_0D4E&Pid_047A) and we would like to upgrade firmware. We should use Proxim drivers, but Proxim drivers DO NOT support such card. What will we do?
We will crack the Proxim driver!
So, we need at first to download 2 things:
- Proxim driver;
- Freeware Hex Editor XVI32 from http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm.
Unpack hex editor and learn how to use it, including searching binary and text, manualy replacing hex and text, etc, etc.
Now, we can hack the driver. First of all, open in Notepad WLLUC51B.INF file. Find identifier of Original ORiNOCO USB device (Vid_047E&Pid_0300) and replace it with our one (Vid_0D4E&Pid_047A) - do it in all places. Then, open all binary files in XVI32, find Original ORiNOCO USB device (Vid_047E&Pid_0300) and replace it with our one (Vid_0D4E&Pid_047A) - do it in all places. And that's all! You can now install original Proxim driver and your device will be identified as "ORiNOCO USB Card".
To upgrade firmware this hack is sufficient. But not in all situations. For example we would like to install Client Manager, but client manager would not discover our card. We can crack Client Manager in the same way as USB drivers. Open in XVI32 file "Cmluc.dll". Find identifier of Original ORiNOCO USB device (Vid_047E&Pid_0300) and replace it with our one (Vid_0D4E&Pid_047A) - do it in all places. Now Client Manager will work with your USB device :-)
But how to get card Vid and Pid? There is at least 2 ways to do it:
- use linux command "lsusb" for USB device or "lspci" for PC or PCI or PCMCIA in PCI-PCMCIA adapter device. For "lsusb" output should be like:
debian:~# lsusb
Bus 002 Device 003: ID 0d4e:047a Agere Systems
Netherland BV
So, you know, that proper values will be Vid_0D4E&Pid_047A.
- second way (less universal, but maybe easier and could be used for determine PCI and PCMCIA devices Vids and Pids).
1. First of all, download Agere drivers. Then edit in Notepad WLAGSALL.INF.
2. Find line with your device name, for example: "N68="WLAN USB Card". Remember the number (here 68). Go to the top of the file and find first from the top line with this number (here it is: "%N68%=D68,USB\Vid_0D4E&Pid_047A"). You now see the Pid and Vid. The same method could be used for PCMCIA card. For example for "N65="WLAN PC Card" it is "%N65%=D65,PCMCIA\Wireless-WLAN_PC_Card-5C91", so the identifier is "Wireless-WLAN_PC_Card-5C91".
At the end of this part of material I will tell you how to crack PCMCIA drivers (for example you pulled PCMCIA from your PCMCIA-USB adapter and put to PCMCIA or PCMCIA-PCI bridge for flashing firmware purpose). For example when you have got "WLAN USB Card", the PCMCIA inside it will be discovered as "WLAN PC Card". With the method described above you know, that identifier of this device is "Wireless-WLAN_PC_Card-5C91". So, you must edit original drivers and replace original identifier (with methods described above) in INF and binary files by your device identifier. And that's all.
There are two kinds of firmware: flashable and third party firmware. Third party firmware is currently supported only by Windows. Third party firmware is embed in Windows drivers (for more information see "Drivers" paragraph). Upgrading to the latest version of firmware requires on Windows only installing the newest version of Windows drivers.
There is also the second kind of firmware: flashable firmware, flashed inside of the PCMCIA card. This firmware is used under other OS than Windows and under Windows, when the firmware embed in drivers is not newer than flashed one.
If you want to use monitor mode under Linux, you MUST use 6.16 version of flashable firmware!!! Monitor mode DO NOT work under > 6.16 version of firmware. You should know it.
To flash older version than 8.x firmware you should use Windows 98. I had many problems to get cards properly flashed under other OS'es than Windows 98 (firmware updater didn't want to work). With Windows 98 there is no problem to flash any version of firmware.
To flash other firmware than 8.72 you must have firmware updaters cracked. Not-cracked firmware updaters DO NOT work in 90% times. You can try these, but I could use only cracked ones. You must use also Proxim drivers (read "Drivers" section).
Here you can find cracked versions of firmware updaters (and 8.72 one, which do not demand cracking and could be also normally flashed at USB adapter without ejecting PCMCIA card):
If you would like to change the firmware in other USB card than the following:
ORiNOCO USB Card (Vid_047E&Pid_0300)
you must crack this "cracked" firmware updaters like drivers (see "Drivers" section). Edit in binary editor firmware updater and change Vid&Pid to your device ID's.
During flashing firmware updater could give you several errors - ignore them all.
Under Linux OS (only) you can use ORiNOCO's USB adapter also for Prism-2 and Prism-2.5 5V cards! These cards are also supported by orinoco-usb Linux driver. Read more in "Linux support" paragraph. But you must know, that not all cards (even Prism) will work in this adapter. Why? Because simply for high-powered cards (100 mW, 200 mW) the USB voltage is not sufficient. So I recommend using only low-powered (e.g. 30 mW) cards in this adapter. You can use high-powered cards in this adapter, but in this case you must adapt PCMCIA-USB bridge to use external power supply - if you will do it - even 300 mW cards will work :-)
In Windows environment I recommend to use the newest Agere drivers (firmware 9.42 included) + the Agere Client Manager (all described above). This is screenshot from the main page of Client Manager:
You can get know if the card isn't broken on Diagnostic page:
And Site Monitor page:
Site Monitor page displays all APs with SSID choosen in Selection tab. On the upper image there is only one AP with SSID "maciek", so only one AP is displayed. At the bottom image you could see multiple APs with SSID "iele":
If your partner is ORiNOCO or Prism one (AP, card in Ad-Hoc mode, etc), then you can choose "Link test" option:
"Test History" tab is very important - especially "Signal/Noise" graph on the partner side. You can get know if your partner receives good signal:
In image above you can find that on the partner side often the noise is greater than the signal, so even if Netstumbler shows good signal on your side you will have problems: your partner station will disconnect you often (when the noise is greater than the signal - SNR in a moment goes to 0 and lower)!!! The "Lucent Test" special protocol is only protocol which allow you to know signal and noise from both stations in one time!!!
This card (like ORiNOCO Classic PCMCIA Card) is fully supported by Netstumbler!!! For more information read Netstumbler manual and WWW pages about Netstumbler + ORiNOCO Classic PCMCIA cards. At the screenshot below you can see very sharpened signal, so the link quality is very low. Excellent quality of signal is when the green area is continuous in time (there is no blue or black bars between green signal). When you use Netstumbler, please DO NOT surf the web, ping AP, ping any host. While scanning pings are very irregular and transfer is very low!
So, what is netstumbling?
Netstumbler uses "active scanning". Netstumbler uses functions from hcf library (library created by Lucent for drivers for Hermes cards under Windows OS and probably for wavelan_cs for Linux, also not-open source). Netstumbler sends to card scanning request (query 0x11 with parameter 0xF101). This request tells card, that card must send Probe Request and keeps information about nodes which send Probe Response to a card. This method is asynchronous - when card gets response, sends communicate to procedure which serves interrupts. Netstumbler can request following parameters:
a) channel number;
b) noise level;
c) signal level;
d) AP MAC
(BSSID);
e) beacon interval;
f) WEP enabled;
g) ssid length;
h)
SSID.
To do antenna positioning it is the best to use Windows XP operating system with Wireless Client Manager from Agere and the latest version of drivers.
First of all, you must know that there are 2 major ways to put antennas in correct position. You can use Wireless Client Manager from Agere. If Client Manager shows "excellent" radio connection, you can be sure, that your link quality and signal strength is OK:
If not, you can think of changing antenna place. To get correct position, use Site Monitor feature:
Please position antenna go get the highest possible and stable SNR value.
After this, please test your connection by pings. In Windows XP OS type:
ping -t -l 1444 AP_IP_Address
The loss of packets should be lower than 5%:
Ping-method is the only method that you can use than you have to place antenna with non-ORiNOCO, Prism or Atheros based card. This method is very simple - and very efficient. But if you observe packet loss, you will not be able to guess why. This can be only discovered with proper utilities, like Agere Client Manager or Netstumbler.
You can also use Netstumbler to place antenna in proper position. How to use Netstumbler? Read Netstumbler documentation :-)
Simply turn off auto-reconfigure and track signal and noise chart. Signal is in green, noise in red. Examples of good signal:
and of bad signal:
So, why signal is good or bad?
Good signal = signal continuous. There should not be any purple or black spaces. Purple or black spaces mean lack of signal. And the green bars (signal) should be as high as possible, red bars (noise) should be as low as possible :-) If you forget to turn off Auto-Reconfigure, you will observe lack of signal, even if the link quality is excellent!
Please look at few examples:
a) AP's overview:
b) very strong signal (up to -50 dBm), but also quite irregular, high noise (SNR is jumping from 45 dB to 15 dB):
c) very weak and sharpened signal - signal quality is very low. Pings will be irregular and very long, throughput will be very small:
d) signal very high (up to -55 dBm), but also noise is jumping. Link quality is quite good:
e) signal is very week (-90 dBm), but also noise is very small (up to -95 dBm). Signal is continuous, SNR still >= 5 dB - radio connection will be marginal, but on ORiNOCO cards will be no problem with pings (will be small and continuous) and with transfers:
f) the same as in e) point:
g) scanning with a directional antenna. You could find that the strongest signal was about -40 dBm and you can properly place your antenna:
h) using Wireless Client Manager: displaying all AP's in range with SSID "iele":
When you use Netstumbler, please DO NOT surf the web, ping AP, ping any host. While scanning pings are very irregular and transfer is very low!
1. Ethereal - full support.
2. Wild Packets driver (and other allowing to passive monitoring under Windows) - no support!!
3. Kismet (passive scanning under Linux) - full support (Linux, see Linux notes).
4. Most of other Windows utilities supporting ORiNOCO PCMCIA Classic Card DO NOT support this card in USB adapter.
5. Most of other Windows utilities supporting ORiNOCO PCMCIA Classic Card support this card in PCMCIA-PCI adapter.
6. Linux utilities supporting ORiNOCO PCMCIA Classic Card support this card in USB adapter.
7. Other Linux utilities (Airsnort, etc, etc) - full support where Hermes-I chipset is supported!!!
If you get one of above errors or all of them (alerted by Netsumbler, Windows, Hardware Manager, etc) everything with your hardware IS OK!! Under Windows OS, when ORiNOCO Classic Card detects some bad frames, it will freeze... This is known defect. These bad frames can be produced by some D-Links in bridge mode and some others APs. The only known "bad AP" is WAP-11, possibly another one: Belkin's Pre-N. When you often have got this kind of error please buy card on not-Hermes-I chipset or use your ORiNOCO card on Linux. With Linux OS I didn't experience this problem yet with any configuration.
Linux ORiNOCO USB driver has got the same possibilities as PCMCIA version. The reason is simple: Linux ORiNOCO driver is modular. There is main module which contains all the code to manage Hermes-I, Prism-2, Prism-2.5 and Symbol devices. There are also other modules responsible for management of PCMCIA interface, USB interface, PCI interface, etc, etc. So, even you can put to ORiNOCO-USB bridge Prism-2 and Prism-2.5 PCMCIA card and it will work as PCMCIA one!!! But Symbol cards are known to NOT work in USB interface!
As soon as there is no ORiNOCO USB driver in Linux kernel, there is best to use SVN version of this driver with actual changes - the driver changes sometimes frequently.
You can't change (upgrade, downgrade) your firmware in Linux! This operation is only supported by Agere / Proxim Windows utility (see Windows notes above).
Linux can use only flashed firmware inside PCMCIA (dynamic firmware memory loading is not supported). So, in Windows you can use WPA (embed in 9.42 firmware included in drivers). The most recent flashable version of firmware is 8.72, so in Linux you can use only 8.72 as the highest version!
Official ORiNOCO Driver project: http://www.nongnu.org/orinoco/
SVN
repository (orinoco-usb driver included): https://sourceforge.net/svn/?group_id=44338
USB
driver is included in subversion (SVN) repository as branches/usb
Linux ORiNOCO USB driver supports all the devices supported by Windows ORiNOCO USB driver:
Wireless USB Card Model 0801 (Vid_0D4E&Pid_1000)
Wireless USB Card
Model 0802 (Vid_0D4E&Pid_1001)
Avaya Wireless USB Card
(Vid_0D98&Pid_0300)
Avaya Wireless USB Card
(Vid_0D9E&Pid_0300)
BUFFALO Airstation USB
(Vid_0411&Pid_000B)
BUFFALO WLI-USB-L11 Wireless LAN Adapter
(Vid_0411&Pid_0006)
BUFFALO WLI-USB-L11G Wireless LAN Adapter
(Vid_0411&Pid_000D)
ELSA AirLancer USB-11
(Vid_05CC&Pid_3100)
Joynet WLAN USB Card
(Vid_0E7C&Pid_0300)
ORiNOCO USB Card (Vid_047E&Pid_0300)
Samsung
SEW-2001u Card (Vid_04E8&Pid_5002&Rev_0000)
Samsung SEW-2001u Card
(Vid_04E8&Pid_5B11)
Samsung SEW-2003U Card
(Vid_04E8&Pid_7011)
I-GATE 11M USB Card
(Vid_0681&Pid_0012)
connect2AIR WLAN E-1100 USB
(Vid_0BF8&Pid_1002)
2Wire Wireless USB adapter
(Vid_1630&Pid_FF81)
WLAN USB Card (Vid_0D4E&Pid_047A)
and some other cards:
Compaq WL215 USB Adapter (Vid_049F&Pid_001F)
Compaq W200 USB Adapter
(Vid_049F&Pid_0076)
Compaq WL215 USB Adapter (Vid_049F&Pid_0082)
This instruction is useful for installing orinoco-usb Variant-1 devices (with
PCMCIA inside) and kernels >= 2.6.11.
Long time ago SVN files had got
"Assorted cleanups/merges from mainline, via for_linus branch" - after it SVN
code does NOT compile on kernels < 2.6.11 (like 2.6.8) - please use 2.6.12
for best results. 2.6.11 version included in SuSE 9.3 is OK.
I must add,
that you MUST use HOTPLUG Linux distribution, like Linux Debian Sarge / Sid /
SuSE. It will work with Debian Testing / Unstable / SuSE distribution, but it
CANNOT work in some post-Debian distributions like Ubuntu / Kubuntu without
some modifications (read next paragraphs)!
1. Download kernel source
files (for example 2.6.12) and compile kernel from source:
http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.12.3.tar.bz2
2. Download from SVN branch orinoco-usb by:
svn co
https://svn.sourceforge.net/svnroot/orinoco/branches/usb orinoco
to check out only USB branch. If you would like to download all SVN repository, type simply:
svn co https://svn.sourceforge.net/svnroot/orinoco orinoco
Alternatively, to download only trunk (main development line - USB drivers not included), type:
svn co https://svn.sourceforge.net/svnroot/orinoco/trunk orinoco
3. Go
to newly created by SVN "orinoco" folder and do:
- make
- make
install
All modules including orinoco-usb should be installed
without problems.
4. Untar contents of file firmware.tar.gz DIRECTLY to /usr/lib/hotplug/firmware
folder on Debian. If you use other distribution untar attached file contents
DIRECTLY to /usr/lib/hotplug/firmware and to /lib/firmware and
/lib/hotplug/firmware. If you use SuSE please check which folder from mention
above you have got and then put firmware files to proper directories.
All
done! You can insert your orinoco-usb device now!
SuSe: http://www.dot7.de/linux/w200.html
RedHat / SuSe: http://folk.uio.no/oeysteio/orinoco-usb/
SuSe (German language): http://www.zdv.uni-mainz.de/1721.php
If you have got error: "orinoco_usb: No firmware to download" read this paragraph!
> ============================================
> May 10 22:23:29
blanche kernel: usb 2-1:
> new full speed USB device using uhci_hcd and
address 4
> May 10 22:23:29 blanche kernel: orinoco_usb: No firmware to
download
> May 10 22:23:29 blanche kernel: orinoco_usb:
> probe of
2-1:1.0 failed with error -14
>
============================================
This errors appears, when you haven't got "orinoco_ezusb_fw" and
"orinoco_usb_fw.h" in usr/lib/hotplug/firmware and in /lib/firmware and in
/lib/hotplug/firmware.
Copy these 2 files to mentioned directories and it
should work OK
If you will still have got problems after doing this steps
please make sure, that your ORiNOCO USB device is "ORiNOCO USB VARIANT 1"
(old ORiNOCO USB)!
You were warned, that ANY OTHER VARIANTS LIKE
"ORiNOCO USB VARIANT 2" (new ORiNOCO USB) DO NOT WORK ON LINUX (at least with
these orinoco-usb drivers, because new ORiNOCO USB is on Prism-2, not Hermes-1
chipset. Maybe these new ORiNOCO USB devices work with linux-wlan-ng, try
it!
Above error could also be displayed unexpectly in Ubuntu / Kubuntu and partialy in Debian, when "tmpfs" in kernel source was enabled. To get rid this error please compile kernel with "tmpfs" option "disabled" - disable also all options above and below "tmpfs" option.
Monitor mode (rfmon) in Linux works only on 6.16 firmwares. It may work also on < 6.16 firmwares (6.06, 5.x, etc), but I didn't test it. Also many people reported that monitor mode works fine with the best for monitoring 6.16 firmware. And there is NO person who reported that 6.16 firmware does not work with monitor mode :-) So, if you want to run monitor mode (for example for kismet, ethereal, airsnort, etc), please use 6.16 firmware. Monitor mode with 0.15 SVN drivers and 6.16 firmware is very stable, it worked 3 days without any interrupts (then I closed Kismet, but I suspect that this card in monitor mode will work for unlimited time).
Firmwares 7.x DO NOT work with monitor mode (confirmed for many people and me, but some people reported that it works - probably unstable)!!!
Firmware 8.72 PARTIALLY support monitor mode (without channel hoping) and card freezes in monitor mode after about 15 minutes!!! If you want to use monitor mode with 8.x firmwares you must enable support for them in orinoco.c. Simply change "force_monitor = 0" to "1". Support for 8.x firmwares in monitor mode was rejected in drivers, so you must manually enable it. Kismet: you must DISABLE channel hoping (with channel hoping this card freezes) and then set "initial channel" back of "source" directive (read kismet manual).
In 6.16 firmware there is no problem and monitor mode works always stable! To enable monitor mode type:
iwconfig eth1 mode monitor
when your ORiNOCO's interface is "eth1".
To disable monitor mode, set the mode which you like. For example:
iwconfig eth1 mode managed
If you would like to run Kismet, please at first read paragraph "Monitor mode in Linux". After reading it, you will know, that to run Kismet properly you must probably have 6.16 firmware.
Unfortunately 0.15 SVN drivers are a little incompatible with Kismet. Mike Kershaw, author of Kismet did a patch to fix this incompatibility. You can find it in Kismet download page in section "ORiNOCO Driver Patches for CVS" (some time ago orinoco drivers were in CVS, not in SVN).
Kismet, drivers, patches are changing frequently. If something today work,
tomorrow can not. So, I did a snapshot of all things required to run Kismet
properly - if you have got a problem with the newest versions, use this
snapshot:
Linux
kernel 2.6.13.3
ORiNOCO 0.15 SVN
drivers
ORiNOCO 0.15 CVS patch
by Mike Kershaw (works for SVN drivers from link above)
Kismet-2006-04-R1
WARNING: CVS patch from Dragorn does not work with current SVN drivers! So the instructions below are only useful, if you will download snapshot from link above. If you will download current SVN drivers, you must only compile it in way described in paragraph "Instruction of installation orinoco-usb on Debian Unstable / Testing with kernel 2.6.12 or SuSE 9.3 or higher" and set "orinoco" as capture source in Kismet configuration file. Please note, that if you will use current SVN code (without Dragorn patch), captured frames will not have Prism header (so signal and noise statistics will not be provided) and will not have FCS bytes (so there is no iwpriv command to turn it off).
Now, we have to recompile ORiNOCO drivers. Follow points 1 and 2 from paragraph "Instruction of installation orinoco-usb on Debian Unstable / Testing with kernel 2.6.12 and higher or SuSE 9.3 or higher" - you may use above snapshots if you like instead of the newest driver SVN sources. Before point 3 you must apply the "ORiNOCO 0.15 CVS patch by Mike Kershaw" - if you want to use the newest patch, download it from Kismet download page. To apply the patch, copy it to directory with 0.15 SVN drivers (in which you can see orinoco.c) and in terminal type:
patch -p1 < orinoco-0.15rc2-dragorn-02.diff
Patch is now applied - you can now follow rest points (3. and later) from paragraph "Instruction of installation orinoco-usb on Debian Unstable / Testing with kernel 2.6.12 and higher or SuSE 9.3 or higher".
Consequences of adding this patch:
- added Prism header (now
measurement of signal and noise will be provided);
- added FCS bytes.
FCS bytes and Prism header are turned on by default. You must know, that some utilities (also Kismet!) DO NOT work properly with FCS bytes enabled. In Ethereal you can in Preferences check "Assume FCS appended" box - then Ethereal will work properly with FCS bytes. But most of applications WILL NOT WORK properly with FCS and you must turn FCS off before launching such applications (also Kismet!).
So, before starting Kismet (or any other application working bad with FCS), type following:
iwpriv eth1 set_fcsbytes 0
(eth1 should be replaced by the proper interface name). After this, you can run successfully Kismet or Ethereal without "Assume FCS appended" checked, etc.
To run Kismet you can simply type "kismet" without enabling monitor mode - monitor mode will be enabled automatically!
Use Kismet with "orinoco" capture source!
After closing Kismet ORiNOCO gets cleanly from monitor mode and reverts any previous settings (6.16 firmware, 0.15 SVN drivers).
ORiNOCO drivers support also other utilities, like Ethereal, Airsnort, etc. In Linux there is no difference between PCMCIA and USB version of ORiNOCO Classic Card!!!
ORiNOCO driver support fully Wireless Tools. To configure the interface (for example "eth1") you can do:
iwlist scanning (scan for APs and clients in ad-hoc mode)
iwconfig eth1 mode managed (I will connect to AP)
iwconfig eth1 essid AP1 (I will connect to AP with SSID "AP1")
ifconfig eth1 192.128.1.45 netmask 255.255.255.0 up (get up the interface)
route add default gw 192.168.1.1 (I will add default gateway)
Then you can edit file /etc/resolv.conf and write your DNSes, for example
nameserver 194.204.159.1
User mailing list: subscription, archives.
Developers mailing list: subscription, archives.
You can contact me to send your suggestions, information, etc, etc at: orinoco@skatnet.dk