1 |
> Hi All, |
2 |
> |
3 |
> I have been experimenting with my wireless cardbus and cannot get it |
4 |
> to work with airodump-ng: |
5 |
> |
6 |
> From lshw: |
7 |
> |
8 |
> *-network |
9 |
> description: Wireless interface |
10 |
> product: AR5212 802.11abg NIC |
11 |
> vendor: Atheros Communications, Inc. |
12 |
> physical id: 3 |
13 |
> bus info: pci@0000:04:00.0 |
14 |
> logical name: wifi0 |
15 |
> version: 01 |
16 |
> serial: XX:XX:XX:XX:XX:XX |
17 |
> width: 32 bits |
18 |
> clock: 33MHz |
19 |
> capabilities: pm bus_master cap_list logical ethernet |
20 |
> physical wireless |
21 |
> configuration: broadcast=yes driver=ath_pci ip=XX.XX.XXX.XXX |
22 |
> latency=168 maxlatency=28 mingnt=10 module=ath_pci multicast=yes |
23 |
> wireless=IEEE 802.11g |
24 |
> |
25 |
> lspci -v gives: |
26 |
> |
27 |
> 04:00.0 Ethernet controller: Atheros Communications, Inc. AR5212 |
28 |
> 802.11abg NIC (rev 01) |
29 |
> Subsystem: PROXIM Inc Device 0a10 |
30 |
> Flags: bus master, medium devsel, latency 168, IRQ 11 |
31 |
> Memory at 44000000 (32-bit, non-prefetchable) [size=64K] |
32 |
> Capabilities: [44] Power Management version 2 |
33 |
> Kernel driver in use: ath_pci |
34 |
> Kernel modules: ath_pci |
35 |
> |
36 |
> I am using net-wireless/madwifi-ng-0.9.4 |
37 |
> |
38 |
> When I run airmon-ng it shows my ath0 interface: |
39 |
> |
40 |
> # airmon-ng |
41 |
> |
42 |
> |
43 |
> Interface Chipset Driver |
44 |
> |
45 |
> wifi0 Atheros madwifi-ng |
46 |
> ath0 Atheros madwifi-ng VAP (parent: wifi0) |
47 |
> |
48 |
> Running 'airmon-ng start wifi0' it creates a new VAP ath1 and puts it |
49 |
> in Monitor mode. So far so good, but running airodump-ng shows no |
50 |
> data being captured. Trying to stop ath0 (in case it interferes) |
51 |
> shuts down /etc/init.d/net.ath0, although I still get ath1 shown in |
52 |
> iwconfig. |
53 |
> |
54 |
> Have I missed something basic here? Do I need perhaps to add net.ath1 |
55 |
> -> /etc/init.d/net.lo in the same way that I have done for ath0? |
56 |
> -- |
57 |
> Regards, |
58 |
> Mick |
59 |
> |
60 |
> |
61 |
|
62 |
Hi Mick, |
63 |
|
64 |
I have te same thing when using kismet, after starting kismet if I use airmon-ng to look at my interfaces, I have this: |
65 |
|
66 |
$ airmon-ng |
67 |
wifi0 Atheros madwifi-ng |
68 |
ath0 Atheros madwifi-ng VAP (parent: wifi0) |
69 |
kis0 Atheros madwifi-ng VAP (parent: wifi0) |
70 |
|
71 |
Then if I want to shootdown kis0, I will use airmon-ng like this: |
72 |
|
73 |
$ airmon-ng stop kis0 |
74 |
|
75 |
And kis0 will be destroyed. |
76 |
So I think you can destroy any child of wifi0 by doing this with airmon-ng |
77 |
|
78 |
For enabling monitor mode I do like you: |
79 |
|
80 |
$ airmon-ng start wifi0 |
81 |
|
82 |
It will create a new child of wifi0, ath1 in my case. |
83 |
Then starting 'airodump-ng ath1' will let me capture packet coming on ath1, if of course any AP are active in my |
84 |
neighbourhood |
85 |
|
86 |
To destroy ath1 you do like for destroying kis0 |
87 |
|
88 |
$ airmon-ng stop ath1 |
89 |
|
90 |
Hope it help |
91 |
|
92 |
|
93 |
http://www.drakonix.fr |