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