On Wed, 21 Apr 2004, Matt Brown wrote:
> On Tue, 2004-04-20 at 18:32, Pavel Roskin wrote:
> > > - 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'm not aware of this problem. Maybe it's specific to 1.4.9 firmware.
>
> I just upgraded the firmware on my Prism 2.5 cards using prism2_srec and
> the firmware at http://www.red-bean.com/~proski/firmware/ my cards are
> now running the following versions
> PRI: id=0x15 v1.1.1
> STA: id=0x1f v1.8.0
>
> I still see the same problem, using tcpdump 3.8.3 when the interface is
> in monitor mode I see only acknowledgement and beacon frames. I loaded
> the hostap driver and repeated the same test - with the hostap driver I
> see data frames in the tcpdump output.
I cannot reproduce the problem with tcpdump. I guess it's related to WEP
somehow. Check WEP keys on all participating interfaces. Try unsetting
WEP keys everywhere.
I've just applied a patch that enables host decryption in monitor mode on
Symbol and Intersil firmware. It has no visible effect for me, but the
original monitor mode patch did it. Also, hostap does it.
If the problem is not WEP related, please run dump_recs and send me the
output (or send it to the list if the file is not too large and you don't
have WEP keys set).
> > > 1) Configuring an interface that uses a Prism based card results in
> > > "Error -110 setting multicast list." (also reported by Stephen Scholz)
> >
> > I have seen it. Prism cards are not quite ready for 5-10 milliseconds
> > after port 0 is enabled. That explains may failures immediately after
> > the interface is brought up. It needs to be fixed.
>
> I see this error even if I wait up to 30 seconds after inserting the
> card before configuring an IP address. Is port 0 enabled on card
> insertion on when the interface is brought up?
It's enabled when the interface is brought up.
> > Messages about orinoco_lock() come from the interrupt handler. They are
> > harmless. Perhaps they should be disabled.
>
> If they could be disabled it would be great, removing a card currently
> tends to flood my logs with >50 orinoco_lock() messages. A minor
> annoyance.
Alternatively, the interrupt handler should be disabled when the card is
removed. There is more than one solution. It's important that we don't
hide the real problems by removing the message.
> > Monitor mode is not working correctly in 8.72 firmware. Perhaps it should
> > be disabled for this firmware version. I still hope to find a less
> > radical solution. Disabling fast channel change helps somewhat, but not
> > much - the card still goes crazy after some time.
> >
> > snip
> >
> > Monitor mode is working fine with 6.16 firmware.
>
> Hmm, so basically monitor mode is not functional with Orinoco hardware?
> 6.16 must be firmware from the dark ages!
There are firmwares other than 6.16 and 8.72, and I haven't seen any
reports about monitor mode with those firmwares. One of the reason to
make a release candidate is to get such reports.
I still hope to find a workaround rather than disable the monitor mode
completely with 8.72 firmware. It's also possible (although not likely)
that the driver is doing something wrong.
> A couple of other errors I encountered today
>
> When placing the Prism 2.5 card into monitor mode after upgrading the
> firmware, I observed
>
> root-X6RhF4x9mZo@xxxxxxxxxxxxxxxx:~# iwconfig eth2 mode monitor
> hermes @ MEM 0xc4825000: BAP offset error: reg=0x8004 offset=0x0
> eth2: error -110 reading info frame. Frame Dropped.
That's a timeout.
> Using the Orinoco card in monitor mode, I observed
> root-X6RhF4x9mZo@xxxxxxxxxxxxxxxx:~# iwconfig eth4 mode monitor
> hermes @ IO 0x140: BAP offset error: reg=0x403c offset=0x3c
> eth4: error -5 reading monitor frame
That's a true error. I've improved the error message in CVS to show the
BAP number and distinguish between errors and timeouts.
I've seen this error with 8.72 firmware. I believe it's just one of the
symptoms of incorrect monitor mode support.
--
Regards,
Pavel Roskin
-------------------------------------------------------
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
|
| 
