From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Valroff Date: Thu, 27 Oct 2011 20:36:06 +0200 Subject: [ath9k-devel] Can't associate with a particular AP In-Reply-To: <20111024195501.GA31592@jouni.qca.qualcomm.com> References: <20111004183514.GC3463@kirya.net> <20111005042406.GA3734@kirya.net> <20111015045128.GP20598@kirya.net> <20111016150124.GA13160@kirya.net> <20111023142536.GA4633@kirya.net> <20111024062716.GA14603@infinet.ru> <20111024185932.GG4394@kirya.net> <20111024195501.GA31592@jouni.qca.qualcomm.com> Message-ID: <20111027183606.GA16822@kirya.net> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org 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 ~ ~ : :' : Debian Developer & Free software contributor `. `'` http://www.kirya.net/ `- 4096R/ E1D8 5796 8214 4687 E416 948C 859F EF67 258E 26B1