As far as the receive mode goes, according to the docs:
To be able to access packets from all access points, you need to place the
card in monitor mode. In this mode you cannot transmit. Since you will
not be associating with any of the access points, you will just be seeing
802.11 packets, so to get any usefull info out of it, you need to get the
raw 802.11 packets, which there doesn't seem to be a facility in Linux to
do yet... I left the #defines in there so that someone can play with it
(which people have :), but I didn't put it in the config file, since to do
anything useful you need to tweak the driver.
As far as the AP: field in the Status file: I always see the AP that I'm
assocated with unless I'm in adhoc mode.
Paul Castro <castrop@...>@csl.cse.ucsc.edu on 05/17/2000 08:40:08
Sent by: aironet-admin@...
Subject: [Aironet] diagnostics
Thanks to all for the good info on this mailing list! I'm hoping
someone might be able to help me.
I'd like to write a diagnostic tool for Aironet networks under linux
-- basically I want to collect statistics on access points, signal
qualities, etc in real-time. While it's easy to get information about
the access point the client is currently associated with, it seems
harder to get information about the entire network of access points,
clients, etc currently available to a client (in other words, at any
point in time what is the signal quality to all access points in the
WaveLAN comes with a nice utility that provides statistics on the
entire site. I can get signal quality measures and MAC addresses for
all access points currently seen by the client. Can this be done with
Here's what I think: if I can set the receive mode properly I should
get packets from all access points. The /proc/aironet/ethX/Status
file will then give me the info I need. 2 problems though: the AP:
field in Status is always blank so I don't know which AP I am talking
to, and I can't figure out how to set the receive mode in the airo
driver. I see the receive mode definitions in the driver but the
parsing of the /proc/aironet/ethX/Config file doesen't seem to take
into account this setting, nor does the module settings.
Has anyone done this?
Thanks in advance,
Aironet mailing list - Aironet@...
From: Daniel Bidwell <bidwell@an...> - 2000-05-17 16:24:00
On Wed, May 17, 2000 at 09:12:38AM -0700, breed@... wrote:
> Paul Castro <castrop@...>@csl.cse.ucsc.edu on 05/17/2000 08:40:08
> Here's what I think: if I can set the receive mode properly I should
> get packets from all access points. The /proc/aironet/ethX/Status
> file will then give me the info I need. 2 problems though: the AP:
> field in Status is always blank so I don't know which AP I am talking
> to ...
Are your AP's internally labeled? When you configure the individual
AP's there is a spot for a name. This name is what you see in the
Status display. If the name is not filled in for the AP, it doesn't
show up in the client either.
Daniel R. Bidwell | bidwell@...
Andrews University Information Technology Services
If two always agree, one of them is unnecessary
"Friends don't let friends do DOS"
"In theory, theory and practice are the same.
In practice, however, they are not."
No tema al pinguino.
From: Matt <matt@Typhoon.n0x.net> - 2000-05-17 16:26:16
I am running .99zd version and have been playing with trying to convert
my box into a bridge between the wireless and my local network.
Is there any special config other than turning bridging on with the little
utility(and the kernel changes) that I need be aware of? So far I haven't
been successful getting this thing to bridge...