From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Atheros chip with airodump-ng
Date: Fri, 7 Nov 2008 11:03:29 +0000 [thread overview]
Message-ID: <358eca8f0811070303s2afd8361p3fb182e3f6c4ca3c@mail.gmail.com> (raw)
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=yes driver=ath_pci ip=XX.XX.XXX.XXX
latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes
wireless=IEEE 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=64K]
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
next reply other threads:[~2008-11-07 11:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 11:03 Mick [this message]
2008-11-07 12:50 ` [gentoo-user] Atheros chip with airodump-ng Fred Elno
2008-11-07 13:15 ` Mick
2008-11-13 19:32 ` Simon
2008-11-14 10:36 ` Mick
2008-11-14 10:58 ` Stroller
2008-11-16 15:14 ` Simon
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=358eca8f0811070303s2afd8361p3fb182e3f6c4ca3c@mail.gmail.com \
--to=michaelkintzios@gmail.com \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox