From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: wlan0 promiscuous mode
Date: Wed, 28 Jan 2009 16:08:06 -0600 [thread overview]
Message-ID: <58965d8a0901281408j1c96e353g7e4e1b2471a0c0ea@mail.gmail.com> (raw)
In-Reply-To: <49bf44f10901281217p12538284sf0be3011083cbb7b@mail.gmail.com>
On Wed, Jan 28, 2009 at 2:17 PM, Grant <emailgrant@gmail.com> wrote:
>>> > Does anyone know how to put my USB wireless network adapter into
>>> > promiscuous mode so I can see everything that's happening wirelessley
>>> > on my network in wireshark?
>>>
>>> ifconfig eth1 promisc
>>>
>>> But at least tcpdump puts the interface into promiscous mode
>>> automatically, so there is a chance that wireshark does the same.
>>>
>>>
>>
>> Another way is to use airmon-ng from the aircrack-ng package:
>>
>> airmon-ng start wlan0
>
> Thanks everyone. I didn't realize it but monitor mode is what I'm
> after. aircrack-ng looks interesting too. Is there something similar
> with a GUI? airsnort seems to be discontinued. What is iw for?
iw - show / manipulate wireless devices and their configuration
Usage: iw [options] command
Options:
--debug enable netlink debugging
--version show version
Commands:
help
event
list
phy <phyname> info
dev <devname> set channel <channel> [HT20|HT40+|HT40-]
phy <phyname> set channel <channel> [HT20|HT40+|HT40-]
dev <devname> set freq <freq> [HT20|HT40+|HT40-]
phy <phyname> set freq <freq> [HT20|HT40+|HT40-]
phy <phyname> set name <new name>
dev <devname> set meshid <meshid>
dev <devname> set monitor <flag> [...]
dev <devname> info
dev <devname> del
dev <devname> interface add <name> type <type> [mesh_id
<meshid>] [flags ...]
phy <phyname> interface add <name> type <type> [mesh_id
<meshid>] [flags ...]
dev <devname> station dump
dev <devname> station set <MAC address> plink_action <open|block>
dev <devname> station del <MAC address>
dev <devname> station get <MAC address>
dev <devname> mpath dump
dev <devname> mpath set <destination MAC address> next_hop
<next hop MAC address>
dev <devname> mpath new <destination MAC address> next_hop
<next hop MAC address>
dev <devname> mpath del <MAC address>
dev <devname> mpath get <MAC address>
reg set <ISO/IEC 3166-1 alpha2>
dev <devname> get mesh_param <param>
dev <devname> set mesh_param <param> <value>
next prev parent reply other threads:[~2009-01-28 22:08 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 17:00 [gentoo-user] wlan0 promiscuous mode Grant
2009-01-28 17:08 ` Paul Hartman
2009-01-28 17:17 ` [gentoo-user] " Miernik
2009-01-28 19:46 ` Dominic Kexel
2009-01-28 19:50 ` Saphirus Sage
2009-01-28 20:17 ` Grant
2009-01-28 20:38 ` Saphirus Sage
2009-01-28 20:51 ` Grant
2009-01-28 22:08 ` Paul Hartman [this message]
2009-01-29 2:29 ` Grant
2009-01-29 15:33 ` Paul Hartman
2009-01-29 16:00 ` Grant
2009-01-29 16:06 ` Paul Hartman
2009-01-29 17:06 ` Grant
2009-01-29 17:19 ` Saphirus Sage
2009-01-29 5:23 ` Grant
2009-01-29 11:43 ` Zhu Sha Zang
2009-01-29 12:46 ` Dominic Kexel
2009-01-29 13:15 ` Saphirus Sage
2009-01-29 18:49 ` Grant
2009-01-29 18:45 ` Grant
2009-01-29 20:29 ` Paul Hartman
2009-01-29 22:05 ` Grant
2009-01-29 22:48 ` Paul Hartman
2009-01-30 20:34 ` Dominic Kexel
2009-01-31 22:51 ` Grant
2009-02-04 18:07 ` Dominic Kexel
2009-02-04 20:28 ` Grant
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=58965d8a0901281408j1c96e353g7e4e1b2471a0c0ea@mail.gmail.com \
--to=paul.hartman+gentoo@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