From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1KyQno-0008HN-TK for garchives@archives.gentoo.org; Fri, 07 Nov 2008 12:51:05 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A9F8AE02E6; Fri, 7 Nov 2008 12:51:03 +0000 (UTC) Received: from drakonix.fr (ip-192.net-81-220-112.brest.rev.numericable.fr [81.220.112.192]) by pigeon.gentoo.org (Postfix) with ESMTP id 5767AE02E6 for ; Fri, 7 Nov 2008 12:51:03 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by drakonix.fr (Postfix) with ESMTP id 40C5A2327 for ; Fri, 7 Nov 2008 13:50:41 +0100 (CET) X-Virus-Scanned: amavisd-new at fr Received: from drakonix.fr ([127.0.0.1]) by localhost (www.drakonix.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PK5V9IUoRpEX for ; Fri, 7 Nov 2008 13:50:39 +0100 (CET) Received: from www.drakonix.fr (localhost [127.0.0.1]) by drakonix.fr (Postfix) with ESMTP id CA0462317 for ; Fri, 7 Nov 2008 13:50:39 +0100 (CET) Received: from 81.220.112.192 (proxying for unknown) (SquirrelMail authenticated user raptor) by www.drakonix.fr with HTTP; Fri, 7 Nov 2008 13:50:39 +0100 (CET) Message-ID: In-Reply-To: <358eca8f0811070303s2afd8361p3fb182e3f6c4ca3c@mail.gmail.com> References: <358eca8f0811070303s2afd8361p3fb182e3f6c4ca3c@mail.gmail.com> Date: Fri, 7 Nov 2008 13:50:39 +0100 (CET) Subject: Re: [gentoo-user] Atheros chip with airodump-ng From: "Fred Elno" To: gentoo-user@lists.gentoo.org User-Agent: SquirrelMail/1.4.16 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 X-Priority: 3 (Normal) Importance: Normal Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 91e9c3d4-6c6f-4e39-ac7e-626e3f0b5ba2 X-Archives-Hash: a69718133bffaef32f3fede7a5dfcf0c > Hi All, > > I have been experimenting with my wireless cardbus and cannot get it > to work with airodump-ng: > > From lshw: > > *-network > description: Wireless interface > product: AR5212 802.11abg NIC > vendor: Atheros Communications, Inc. > physical id: 3 > bus info: pci@0000:04:00.0 > logical name: wifi0 > version: 01 > serial: XX:XX:XX:XX:XX:XX > width: 32 bits > clock: 33MHz > capabilities: pm bus_master cap_list logical ethernet > physical wireless > configuration: broadcast=3Dyes driver=3Dath_pci ip=3DXX.XX.XX= X.XXX > latency=3D168 maxlatency=3D28 mingnt=3D10 module=3Dath_pci multicast=3D= yes > wireless=3DIEEE 802.11g > > lspci -v gives: > > 04:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 > 802.11abg NIC (rev 01) > Subsystem: PROXIM Inc Device 0a10 > Flags: bus master, medium devsel, latency 168, IRQ 11 > Memory at 44000000 (32-bit, non-prefetchable) [size=3D64K] > Capabilities: [44] Power Management version 2 > Kernel driver in use: ath_pci > Kernel modules: ath_pci > > I am using net-wireless/madwifi-ng-0.9.4 > > When I run airmon-ng it shows my ath0 interface: > > # airmon-ng > > > Interface Chipset Driver > > wifi0 Atheros madwifi-ng > ath0 Atheros madwifi-ng VAP (parent: wifi0) > > Running 'airmon-ng start wifi0' it creates a new VAP ath1 and puts it > in Monitor mode. So far so good, but running airodump-ng shows no > data being captured. Trying to stop ath0 (in case it interferes) > shuts down /etc/init.d/net.ath0, although I still get ath1 shown in > iwconfig. > > Have I missed something basic here? Do I need perhaps to add net.ath1 > -> /etc/init.d/net.lo in the same way that I have done for ath0? > -- > Regards, > Mick > > Hi Mick, I have te same thing when using kismet, after starting kismet if I use ai= rmon-ng to look at my interfaces, I have this: $ airmon-ng wifi0 Atheros madwifi-ng ath0 Atheros madwifi-ng VAP (parent: wifi0) kis0 Atheros madwifi-ng VAP (parent: wifi0) Then if I want to shootdown kis0, I will use airmon-ng like this: $ airmon-ng stop kis0 And kis0 will be destroyed. So I think you can destroy any child of wifi0 by doing this with airmon-n= g For enabling monitor mode I do like you: $ airmon-ng start wifi0 It will create a new child of wifi0, ath1 in my case. Then starting 'airodump-ng ath1' will let me capture packet coming on ath= 1, if of course any AP are active in my neighbourhood To destroy ath1 you do like for destroying kis0 $ airmon-ng stop ath1 Hope it help http://www.drakonix.fr