Re: [Madwifi-users] Configurat madwifi driver to capture 802.11

[hce <web...@gm...>]

On Dec 6, 2007 5:07 PM, Pavel Roskin <pr...@gn...> wrote:
> On Thu, 2007-12-06 at 16:45 +1100, hce wrote:
>
> > I did exactly that. Then I started  the wireshark. Now, the Link-layer
> > header type for ath0 is IEEE 802.11 plus Prism II monitor mode header,
> > but is in grey color. I started to capture data, but no packeckes.
>
> I don't understand that.  You can try "tshark -i ath0" - it's a text
> program, at least its output can be quoted.

# tshark -i ath0
Capturing on ath0

Nothing coming.

> My guess is that the interface is down.

How can I check to see it is down or not?


> > Please see following iwconfig, it seems that the AP is not associated,
> > or it does not matter?
>
> It should not be associated.
>
> > There are many APs here, how can I let the ath0 connect to my AP "Test
> > Wireless AP"?
>
> It's impossible.  But you can create a separate interface in managed
> mode.  It should be created before the interface in monitor mode:
>
> wlanconfig ath0 destroy
> wlanconfig ath0 create wlandev wifi0 wlanmode managed
> wlanconfig ath1 create wlandev wifi0 wlanmode monitor
>
> Now you can use ath0 for connection and ath1 for monitoring.
>
> But if you are debugging any problems, I suggest that you use physically
> separate devices for association and monitoring.  This way, you are
> guaranteed not to get any artifacts, only what's actually on air.

Thank you.

Kind Regards,

Jim