From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pavel Roskin <proski@gnu.org>
Date: Mon, 27 Jun 2011 12:59:43 -0400
Subject: [ath9k-devel] Monitor mode in ath9k
In-Reply-To: <BANLkTikNVqC=5RyC_diQW+oQQLh3aD4=4w@mail.gmail.com>
References: <BANLkTikuKqXouMk2vkAbLnnNSZFGHqL4vw@mail.gmail.com>	<4E08A7E3.1090107@gnu.org>
	<BANLkTikNVqC=5RyC_diQW+oQQLh3aD4=4w@mail.gmail.com>
Message-ID: <4E08B6FF.5080505@gnu.org>
List-Id: <ath9k-devel.lists.ath9k.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: ath9k-devel@lists.ath9k.org

On 06/27/2011 12:55 PM, mahaveer gupta wrote:
> Hi Pavel,
>
>      After setting the device in monitor mode, I was dumping out the
> packets at the kernel level by modifying some parts of the driver code
> (dumping from ath_rx_tasklet( ) before call to ieee80211_rx( )). I am
> not using any user-space software

Then use ifconfig or ip to set promiscuous mode, e.g.

ip link set wlan0 promisc on

-- 
Regards,
Pavel Roskin