Gentoo Archives: gentoo-user

From: Grant <emailgrant@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Re: wlan0 promiscuous mode
Date: Thu, 29 Jan 2009 17:06:33
Message-Id: 49bf44f10901290906j2f530211j8f0a32c1c6e7e09a@mail.gmail.com
In Reply to: Re: [gentoo-user] Re: wlan0 promiscuous mode by Paul Hartman
1 >>>>>>>> > Does anyone know how to put my USB wireless network adapter into
2 >>>>>>>> > promiscuous mode so I can see everything that's happening wirelessley
3 >>>>>>>> > on my network in wireshark?
4 >>>>>>>>
5 >>>>>>>> ifconfig eth1 promisc
6 >>>>>>>>
7 >>>>>>>> But at least tcpdump puts the interface into promiscous mode
8 >>>>>>>> automatically, so there is a chance that wireshark does the same.
9 >>>>>>>>
10 >>>>>>>>
11 >>>>>>>
12 >>>>>>> Another way is to use airmon-ng from the aircrack-ng package:
13 >>>>>>>
14 >>>>>>> airmon-ng start wlan0
15 >>>>>>
16 >>>>>> Thanks everyone. I didn't realize it but monitor mode is what I'm
17 >>>>>> after. aircrack-ng looks interesting too. Is there something similar
18 >>>>>> with a GUI? airsnort seems to be discontinued. What is iw for?
19 >>>>>
20 >>>>> iw - show / manipulate wireless devices and their configuration
21 >>>>>
22 >>>>> Usage: iw [options] command
23 >>>>> Options:
24 >>>>> --debug enable netlink debugging
25 >>>>> --version show version
26 >>>>> Commands:
27 >>>>> help
28 >>>>> event
29 >>>>> list
30 >>>>> phy <phyname> info
31 >>>>> dev <devname> set channel <channel> [HT20|HT40+|HT40-]
32 >>>>> phy <phyname> set channel <channel> [HT20|HT40+|HT40-]
33 >>>>> dev <devname> set freq <freq> [HT20|HT40+|HT40-]
34 >>>>> phy <phyname> set freq <freq> [HT20|HT40+|HT40-]
35 >>>>> phy <phyname> set name <new name>
36 >>>>> dev <devname> set meshid <meshid>
37 >>>>> dev <devname> set monitor <flag> [...]
38 >>>>> dev <devname> info
39 >>>>> dev <devname> del
40 >>>>> dev <devname> interface add <name> type <type> [mesh_id
41 >>>>> <meshid>] [flags ...]
42 >>>>> phy <phyname> interface add <name> type <type> [mesh_id
43 >>>>> <meshid>] [flags ...]
44 >>>>> dev <devname> station dump
45 >>>>> dev <devname> station set <MAC address> plink_action <open|block>
46 >>>>> dev <devname> station del <MAC address>
47 >>>>> dev <devname> station get <MAC address>
48 >>>>> dev <devname> mpath dump
49 >>>>> dev <devname> mpath set <destination MAC address> next_hop
50 >>>>> <next hop MAC address>
51 >>>>> dev <devname> mpath new <destination MAC address> next_hop
52 >>>>> <next hop MAC address>
53 >>>>> dev <devname> mpath del <MAC address>
54 >>>>> dev <devname> mpath get <MAC address>
55 >>>>> reg set <ISO/IEC 3166-1 alpha2>
56 >>>>> dev <devname> get mesh_param <param>
57 >>>>> dev <devname> set mesh_param <param> <value>
58 >>>>
59 >>>> Are we talking about the same thing?
60 >>>>
61 >>>> iw: "nl80211 userspace tool for use with aircrack-ng"
62 >>>>
63 >>>> - Grant
64 >>>
65 >>> Yes, it was installed as a dep of aircrack-ng.
66 >>>
67 >>> Paul
68 >>
69 >> I've got aircrack-ng installed and I get:
70 >>
71 >> # emerge -pv iw
72 >> These are the packages that would be merged, in order:
73 >> Calculating dependencies... done!
74 >> !!! All ebuilds that could satisfy "net-wireless/iw" have been masked.
75 >> !!! One of the following masked packages is required to complete your request:
76 >> - net-wireless/iw-0.9.7 (masked by: ~amd64 keyword)
77 >> - net-wireless/iw-0_p20080605 (masked by: ~amd64 keyword)
78 >>
79 >> - Grant
80 >
81 > I'm using ~amd64 and emerged net-wireless/aircrack-ng-1.0_rc1 which
82 > pulled in net-wireless/iw-0.9.7 as a dependency. Actually the
83 > aircrack-ng fails to build but that's irrelevant :)
84
85 Got it, thank you.
86
87 - Grant