From: Julien Valroff <julien@kirya.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] Can't associate with a particular AP
Date: Thu, 27 Oct 2011 20:36:06 +0200 [thread overview]
Message-ID: <20111027183606.GA16822@kirya.net> (raw)
In-Reply-To: <20111024195501.GA31592@jouni.qca.qualcomm.com>
Le lundi 24 oct. 2011 ? 21:55:01 (+0200 CEST), Jouni Malinen a ?crit?:
[...]
> You do not need to use Wireshark for the sniffer setup. Assuming the
> driver supports monitor mode, you can do this from the command line as
> root:
>
> ifconfig wlan0 down
> iw wlan0 set type monitor
> iw wlan0 set channel 6 HT20
> ifconfig wlan0 up
> tcpdump -i wlan0 -s 2500 -w /tmp/capture.dump
I cannot get anything to be captured - I have tried from 2 laptops using
different drivers with no success. I even manage to stale the whole laptop
after bringing the interface up the second time when in monitoring mode.
Should the interface be associated when capturing? If so, how is this
achievable? I cannot set the essid then.
Cheers,
Julien
--
.''`. Julien Valroff ~ <julien@kirya.net> ~ <julien@debian.org>
: :' : Debian Developer & Free software contributor
`. `'` http://www.kirya.net/
`- 4096R/ E1D8 5796 8214 4687 E416 948C 859F EF67 258E 26B1
next prev parent reply other threads:[~2011-10-27 18:36 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 16:36 [ath9k-devel] Can't associate with a particular AP Julien Valroff
2011-10-04 5:46 ` Mohammed Shafi
2011-10-04 18:35 ` Julien Valroff
2011-10-05 4:24 ` Julien Valroff
2011-10-15 4:51 ` Julien Valroff
2011-10-16 13:22 ` Mohammed Shafi
2011-10-16 15:01 ` Julien Valroff
2011-10-16 15:31 ` Adrian Chadd
2011-10-16 15:37 ` Mohammed Shafi
2011-10-16 15:40 ` Julien Valroff
2011-10-16 17:16 ` Peter Stuge
2011-10-23 14:25 ` Julien Valroff
2011-10-23 15:02 ` Peter Stuge
2011-10-23 15:54 ` Adrian Chadd
2011-10-23 16:25 ` Julien Valroff
2011-10-23 16:34 ` Julien Valroff
2011-10-23 16:52 ` Peter Stuge
2011-10-23 17:15 ` Julien Valroff
2011-10-23 18:16 ` Peter Stuge
2011-10-23 19:45 ` Adrian Chadd
2011-10-23 15:05 ` kang haiyang
2011-10-24 6:27 ` Alex Hacker
2011-10-24 18:59 ` Julien Valroff
2011-10-24 19:55 ` Jouni Malinen
2011-10-27 18:36 ` Julien Valroff [this message]
2011-10-27 19:13 ` Julien Valroff
2011-10-27 20:27 ` Jouni Malinen
2011-10-28 4:26 ` Julien Valroff
2011-10-28 8:35 ` Jouni Malinen
2011-10-28 19:30 ` Julien Valroff
2011-10-28 20:25 ` Peter Stuge
2011-10-27 20:31 ` Peter Stuge
2011-10-29 6:41 ` Julien Valroff
2011-10-29 6:50 ` Adrian Chadd
2011-10-29 16:27 ` Peter Stuge
2011-10-29 16:34 ` Julien Valroff
2011-10-29 17:09 ` Peter Stuge
2011-10-29 17:15 ` Adrian Chadd
2011-10-29 17:23 ` Peter Stuge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111027183606.GA16822@kirya.net \
--to=julien@kirya.net \
--cc=ath9k-devel@lists.ath9k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.