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 18:49:05
Message-Id: 49bf44f10901291049h1ac0336xb758261a51f4857c@mail.gmail.com
In Reply to: Re: [gentoo-user] Re: wlan0 promiscuous mode by Saphirus Sage
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 >>> I can't get that to work. I get:
17 >>>
18 >>> # airmon-ng start wlan0
19 >>> Interface Chipset Driver
20 >>> wlan3 ath5k_pci - [phy0]
21 >>> wlan0 Ralink 2573 USB rt73usb - [phy1]/usr/sbin/airmon-ng: line 338:
22 >>> /sys/class/ieee80211/phy1/add_iface: No such file or directory
23 >>> mon0: ERROR while getting interface flags: No such device
24 >>> (monitor mode enabled on mon0)
25 >>>
26 >>> It looks like I'm supposed to have /sys/class/ieee80211/phy1/add_iface
27 >>> which isn't there. I've tried with net.wlan0 started and stopped.
28 >>>
29 >>> - Grant
30 >>>
31 >>
32 >> Your driver has to support monitor-mode.
33 >> I am using an Atheros-based internal WiFi-card and an Alpha-USB-WiFi-device
34 >> with Realtek-Chip. The drivers I used a while ago needed a patch to work with
35 >> monitor-mode, but the recent drivers don't. Take a look at the driver-section
36 >> on the aircrack-ng homepage. Maybe your driver needs to be patched.
37 >>
38 >>
39 >>
40 > I'm using the same chipset with the same driver (ath5_pci with phy0),
41 > and my card can go into monitor mode. I'm wondering if you are using the
42 > driver compiled into the kernel or madwifi-ng drivers.
43
44 Are you using AR2425? dmesg tells me:
45
46 ath5k_pci 0000:04:00.0: enabling device (0000 -> 0002)
47 ath5k_pci 0000:04:00.0: registered as 'phy0'
48 ath5k phy0: Support for RF2425 is under development.
49 ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
50
51 but I can't get it to work yet. Not sure what's happening after
52 "Backgrounding".
53
54 - Grant