Hi,
I have been testing the latest release of the driver with 3 cards
- Orinoco Gold Card PCMCIA (Hermes)
- EnGenius NL-2511CD+ EXT2 PCMCIA (Prism 2.5)
- EnGenius 2511MP+ miniPCI (Prism 2.5)
On the whole the driver works really well, having monitor mode and
scanning support is really nice. Thanks for all the hard work that has
been put into this release.
These cards were tested in a soekris (www.soekris.net) net 4521 using an
Orinoco AP-500. The miniPCI card was configured as eth2, the orinoco
PCMCIA card as eth3 and the prism 2.5 PCMCIA card as eth4. Logs of the
insertion of each card can be found at the end of the email.
- Scanning support appears to work perfectly on all of the cards.
- Throughput is reasonable with all of the cards
- There were no problems with general configuration tasks such as
connecting to an AP, configuring ESSID etc.
- In monitor mode using the Prism 2.5 based cards I didn't see any data
frames, only beacons and acknowledgements, perhaps I did something
wrong? The orinoco card was able to see both data, beacons and
acknowledgement frames (despite the errors described below).
I encountered the following problems:
1) Configuring an interface that uses a Prism based card results in
"Error -110 setting multicast list." (also reported by Stephen Scholz)
root-X6RhF4x9mZo@xxxxxxxxxxxxxxxx:~# ifconfig eth4 10.10.10.10 netmask
255.255.255.0
hermes @ IO 0x140: BAP offset error: reg=0x8000 offset=0x0
eth4: Error -110 setting multicast list.
hermes @ IO 0x140: BAP offset error: reg=0x8000 offset=0x0
eth4: Error -110 setting multicast list.
root-X6RhF4x9mZo@xxxxxxxxxxxxxxxx:~# ifconfig eth2 10.10.11.10 netmask
255.255.255.0
hermes @ MEM 0xc4825000: BAP offset error: reg=0x8000 offset=0x0
eth2: Error -110 setting multicast list.
This does not appear to affect the operation of the card.
2) Enabling Monitor Mode on Prism 2.5 PCMCIA card gives a BAP offset
error, followed by a funny link status error
root-X6RhF4x9mZo@xxxxxxxxxxxxxxxx:~# iwconfig eth4 mode monitor
hermes @ IO 0x100: BAP offset error: reg=0x8000 offset=0x4
eth4: New link status: UNKNOWN (c325)
Monitor mode appears to work correctly despite this.
3) Removing Prism 2.5 PCMCIA card results in lots (approx 50)
orinoco_lock() called with hw_unavailable (dev=c3255800)
messages followed by a single
dv_mc_discard: multicast leakage! dmi_users=1
4) Orinoco card in monitor mode results in lots of the following
messages
root-X6RhF4x9mZo@xxxxxxxxxxxxxxxx:~# iwconfig eth3 mode monitor
eth3: New link status: Connected (0001)
eth3: IRQ handler is looping too much! Resetting.
eth3: New link status: Connected (0001)
eth3: IRQ handler is looping too much! Resetting.
eth3: New link status: Connected (0001)
eth3: IRQ handler is looping too much! Resetting.
etc...
Does not stop until card is removed from monitor mode.
I also observed
root-X6RhF4x9mZo@xxxxxxxxxxxxxxxx:~# iwconfig eth3 mode monitor
hermes @ IO:0x100: Card removed while waiting for command completion.
eth3: Unable to disable port while reconfiguring card
eth3: Resetting instead...
eth3: New link status: Connected (0001)
eth3: IRQ handler is looping too much! Resetting.
etc...
I'm not sure if monitor mode is meant to work correctly with Orinoco
cards or not? Ignoring the errors above which sometimes stop after a few
seconds I can tcpdump on the orinoco card with sensible looking results.
Hope this helps. If there are any other scenarios that I can help
testing or you have questions about these results please let me know.
----- Card Initialisation Dumps -----
orinoco 0.15rc1STA (David Gibson
<hermes-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@xxxxxxxxxxxxxxxx>, Pavel
Roskin <proski-mXXj517/zsQ@xxxxxxxxxxxxxxxx>, et al)
orinoco_pci 0.15rc1STA (David Gibson
<hermes-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@xxxxxxxxxxxxxxxx> & Jean Tourrilhes
<jt-sDzT885Ts8HQT0dZR+AlfA@xxxxxxxxxxxxxxxx>)
orinoco_pci: Detected PCI device 00:10.0, memory 0xa0000000-0xa0000fff, irq 10
eth2: Hardware identity 8013:0000:0001:0000
eth2: Station identity 001f:0009:0001:0004
eth2: Firmware determined as Intersil 1.4.9
eth2: Ad-hoc demo mode supported
eth2: IEEE standard IBSS ad-hoc mode supported
eth2: WEP supported, 104-bit key
eth2: MAC address 00:02:6F:09:A7:17
eth2: Station name "Prism I"
eth2: ready
orinoco_cs 0.15rc1STA (David Gibson
<hermes-xT8FGy+AXnRB3Ne2BGzF6laj5H9X9Tb+@xxxxxxxxxxxxxxxx>, Pavel Roskin
<proski-mXXj517/zsQ@xxxxxxxxxxxxxxxx>, et al)
eth3: Hardware identity 0001:0004:0005:0000
eth3: Station identity 001f:0001:0008:0048
eth3: Firmware determined as Lucent/Agere 8.72
eth3: Ad-hoc demo mode supported
eth3: IEEE standard IBSS ad-hoc mode supported
eth3: WEP supported, 104-bit key
eth3: MAC address 00:02:2D:93:8B:1C
eth3: Station name "HERMES I"
eth3: ready
eth3: index 0x01: Vcc 5.0, irq 11, io 0x0100-0x013f
eth4: Hardware identity 800c:0000:0001:0000
eth4: Station identity 001f:0009:0001:0004
eth4: Firmware determined as Intersil 1.4.9
eth4: Ad-hoc demo mode supported
eth4: IEEE standard IBSS ad-hoc mode supported
eth4: WEP supported, 104-bit key
eth4: MAC address 00:02:6F:08:27:51
eth4: Station name "Prism I"
eth4: ready
eth4: index 0x01: Vcc 3.3, irq 11, io 0x0140-0x017f
Regards
--
Matt Brown
Email: matt-iKR4d6fC+5+9koe0gwxAeg@xxxxxxxxxxxxxxxx
GSM : 021 611 544
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
|
