Hello,
Johannes Berg wrote:
We really need a raw monitor frame capture.
Not sure how I go about that one?
I have an external RTL8187 device I can stick into monitor mode? But
then it wouldn't be associated/encryption keys...
Tips anyone?
Cheers,
Dan.
We really need a raw monitor frame capture.
Not sure how I go about that one?
I have an external RTL8187 device I can stick into monitor mode? But
then it wouldn't be associated/encryption keys...
Tips anyone?
In this case, adding a monitor interface to your local b43 machine (with
Hello All,
Apologies if this has been fixed in a newer version. I was just
wondering if anyone has seen this bug before:
b43-phy1: Broadcom 4311 WLAN found
b43-phy1 debug: Found PHY: Analog 4, Type 2, Revision 9
b43-phy1 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
b43-phy1
On Tuesday 13 May 2008 10:19:23 Daniel wrote:
Hello All,
Apologies if this has been fixed in a newer version. I was just
wondering if anyone has seen this bug before:
Could you _please_ be so kind an explain your actual problem??
My magic crystalball is broken today.
b43-phy1: Broadcom
On Tue, 2008-05-13 at 09:19 +0100, Daniel wrote:
buffer size7wlan0: wrong buffer size
The missing newlines are fixed in today's wireless-testing repository.
--
Regards,
Pavel Roskin
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
Hello,
Michael Buesch wrote:
Could you _please_ be so kind an explain your actual problem??
My magic crystalball is broken today.
Sorry, it's the problem where after X minutes the device seems to loose
the ability to communicate. It seems to be on a high number of
connections/sec scenario.
On Tuesday 13 May 2008 23:31:17 Daniel wrote:
Hello,
Michael Buesch wrote:
Could you _please_ be so kind an explain your actual problem??
My magic crystalball is broken today.
Sorry, it's the problem where after X minutes the device seems to loose
the ability to communicate. It seems
Where does this wrong buffer size message come from, and what does it mean?
b43-phy1 debug: Using hardware based encryption for keyidx: 1, mac:
ff:ff:ff:ff:ff:ff
wlan0: wrong buffer size7wlan0: wrong buffer size7wlan0: wrong
buffer size7wlan0: wrong buffer size
It comes from
On Wednesday 14 May 2008 01:36:04 Johannes Berg wrote:
On Wed, 2008-05-14 at 01:33 +0200, Johannes Berg wrote:
Where does this wrong buffer size message come from, and what does it
mean?
b43-phy1 debug: Using hardware based encryption for keyidx: 1, mac:
ff:ff:ff:ff:ff:ff
On Wed, 2008-05-14 at 01:48 +0200, Johannes Berg wrote:
b43-phy1 debug: Found PHY: Analog 4, Type 2, Revision 9
b43-phy1 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
b43-phy1 debug: DebugFS (CONFIG_DEBUG_FS) not enabled in kernel config
phy1: Selected rate control
On Wed, 2008-05-14 at 01:27 +0200, Michael Buesch wrote:
Where does this wrong buffer size message come from, and what does it mean?
net/mac80211/rx.c
There are two instances of that message, both in ieee80211_rx_h_amsdu(),
and both in the code path that returns RX_DROP_UNUSABLE.
I guess the
11 matches
Mail list logo
