Monitor Mode on Asus RT-N66U

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware
View previous topic :: View next topic  
Author Message
mdenton
DD-WRT Novice


Joined: 30 Nov 2014
Posts: 5
PostPosted: Sun Nov 30, 2014 20:37    Post subject: Monitor Mode on Asus RT-N66U Reply with quote
Hi.

I'm trying to get monitor mode packet capture working on the Asus RT-N66U (specifically airodump, but kismet/tcpdump should work as well for monitor mode). It has a Broadcom BCM4331 chipset, which supposedly supports monitor mode. I'm using the firmware file "dd-wrt.v24-21676_NEWD-2_K3.x_mega_RT-N66U". It's K3.x, which I need to use because the K2.6 builds on this router don't support USB.

According to http://wireless.kernel.org/en/users/Drivers/b43, the b43 driver supports BCM4331. However, I'm still using wl, and I'm not sure if wl will work for monitor mode on this router. If it doesn't, I'm not sure how to switch to b43 (if that's possible). According to http://ubuntuforums.org/showthread.php?t=1373098, on ubuntu you need to use "b43-fwcutter".

I believe eth0, eth1, and eth2 are the three antennas and they get funneled into br0, though I'm not sure.

Code:
root@DD-WRT:~# wl monitor 1
root@DD-WRT:~# iwconfig
vlan1     no wireless extensions.

lo        no wireless extensions.

br0       no wireless extensions.

eth2      no wireless extensions.

teql0     no wireless extensions.

eth1      no wireless extensions.

eth0      no wireless extensions.

vlan2     no wireless extensions.

root@DD-WRT:~# opkg install wireless-tools
Package wireless-tools (29-5) installed in root is up to date.
root@DD-WRT:~# airodump-ng eth0
Can't find wireless tools, exiting.



This is trying to use tcmpdump to set it in monitor mode:
Code:

root@DD-WRT:~# tcpdump -i eth0 -I -n
tcpdump: eth0: That device doesn't support monitor mode




This is what it looks like when I run ifconfig:
Code:
root@DD-WRT:~# ifconfig
br0       Link encap:Ethernet  HWaddr 10:C3:7B:52:DD:12
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:128945 errors:0 dropped:3288 overruns:0 frame:0
          TX packets:160219 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:18752242 (17.8 MiB)  TX bytes:136096026 (129.7 MiB)

br0:0     Link encap:Ethernet  HWaddr 10:C3:7B:52:DD:12
          inet addr:169.254.255.1  Bcast:169.254.255.255  Mask:255.255.0.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

eth0      Link encap:Ethernet  HWaddr 10:C3:7B:52:DD:10
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:490636 errors:0 dropped:0 overruns:0 frame:0
          TX packets:243995 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:190788165 (181.9 MiB)  TX bytes:127856281 (121.9 MiB)
          Interrupt:4 Base address:0x2000

eth1      Link encap:Ethernet  HWaddr 10:C3:7B:52:DD:12
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:43849 errors:0 dropped:0 overruns:0 frame:18927759
          TX packets:55902 errors:1 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7878783 (7.5 MiB)  TX bytes:31136588 (29.6 MiB)
          Interrupt:3 Base address:0x8000

eth2      Link encap:Ethernet  HWaddr 10:C3:7B:52:DD:14
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:2258
          TX packets:15427 errors:6 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:2196492 (2.0 MiB)
          Interrupt:5 Base address:0x8000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING MULTICAST  MTU:65536  Metric:1
          RX packets:1281 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1281 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:640856 (625.8 KiB)  TX bytes:640856 (625.8 KiB)

vlan1     Link encap:Ethernet  HWaddr 10:C3:7B:52:DD:10
          UP BROADCAST RUNNING PROMISC MULTICAST  MTU:1500  Metric:1
          RX packets:85119 errors:0 dropped:0 overruns:0 frame:0
          TX packets:126148 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:11491350 (10.9 MiB)  TX bytes:108294233 (103.2 MiB)

vlan2     Link encap:Ethernet  HWaddr 10:C3:7B:52:DD:11
          inet addr:10.0.0.14  Bcast:10.0.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:405517 errors:0 dropped:145260 overruns:0 frame:0
          TX packets:117847 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:168502823 (160.6 MiB)  TX bytes:18586068 (17.7 MiB)





Trying to use iwconfig to set monitor mode:
Code:
root@DD-WRT:~# ifconfig eth0 down
root@DD-WRT:~# iwconfig eth0 mode monitor
Error for wireless request "Set Mode" (8B06) :
    SET failed on device eth0 ; Bad address.
root@DD-WRT:~# ifconfig eth0 up


Any help would be highly appreciated!
Back to top View user's profile Send private message
Sponsor
mdenton
DD-WRT Novice


Joined: 30 Nov 2014
Posts: 5
PostPosted: Fri Dec 12, 2014 7:38    Post subject: Reply with quote
bump
Back to top View user's profile Send private message
mdenton
DD-WRT Novice


Joined: 30 Nov 2014
Posts: 5
PostPosted: Wed Dec 17, 2014 1:18    Post subject: Reply with quote
Anyone have experience getting airecrack-ng working on their routers?
Back to top View user's profile Send private message
Per Yngve Berg
DD-WRT Guru


Joined: 13 Aug 2013
Posts: 6870
Location: Romerike, Norway
PostPosted: Sat Dec 20, 2014 9:59    Post subject: Reply with quote
I use tcpdump on the router and log to a file. Download the file with ftp and open with Wireshark.
Back to top View user's profile Send private message
mdenton
DD-WRT Novice


Joined: 30 Nov 2014
Posts: 5
PostPosted: Thu Jan 08, 2015 20:58    Post subject: Reply with quote
Yes, but unfortunately when I try to run tcpdump in monitor mode:

Code:

root@DD-WRT:/# tcpdump -I
tcpdump: eth0: That device doesn't support monitor mode


Any way I can actually get the router's wireless interfaces in monitor mode?
Back to top View user's profile Send private message
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum