You might check the Linux Wi-Fi driver community to find out which cards use Atheros chips and support the 'Madwifi' driver well, and then pick one of those; they're more likely to have a Windows driver that supports monitor mode well.
HelloI have had this wireless card working from day 1 on LinuxMint 10 using the Broadcom STA drivers currently '5.60.48.36-2' from the Additional Drivers repository.
Broadcom did actually release '5.100.82.38' last year, would be nice to have that, but I'm not familiar with how to make the install.
I now want to test a wireless router setup using the various tools including airodump-ng, but I'm getting stuck.
What I would like to know first off is should I be using the wl, b43 or even Ndiswrapper for the driver? I find it difficult to deduce which is the comprehensive most up to date information on this subject.
The following output may help, and thank you for helping in advance.
LinuxMint 10 Julia (native, not mint4win)
-------------------------
* I. scanning WIFI PCI devices...
-- Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
> PCI ID = 14e4:432b (rev 01)
-------------------------
* II. querying ndiswrapper...
-------------------------
* III. querying iwconfig...
lo no wireless extensions.
eth0 no wireless extensions.
eth1 IEEE 802.11abgn ESSID:'
Mode:Managed Frequency:2.457 GHz Access Point: Not-Associated
Bit Rate:16 Mb/s Tx-Power:24 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=5/5 Signal level=0 dBm Noise level=-93 dBm
Rx invalid nwid:0 Rx invalid crypt:1 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
ppp0 no wireless extensions.
-------------------------
* IV. querying ifconfig...
eth0 Link encap:Ethernet HWaddr 00:21:70:ae:6d:10
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:22 Memory:f6fe0000-f7000000
eth1 Link encap:Ethernet HWaddr 00:23:4d:c1:4e:cc
inet6 addr: fe80::223:4dff:fec1:4ecc/64 Scope:Link
UP BROADCAST MTU:1500 Metric:1
RX packets:5 errors:0 dropped:0 overruns:0 frame:5052
TX packets:4 errors:24 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:565 (565.0 B) TX bytes:572 (572.0 B)
Interrupt:17 Base address:0xc000
eth0:avahi Link encap:Ethernet HWaddr 00:21:70:ae:6d:10
inet addr:169.254.6.16 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
Interrupt:22 Memory:f6fe0000-f7000000
eth1:avahi Link encap:Ethernet HWaddr 00:23:4d:c1:4e:cc
inet addr:169.254.9.53 Bcast:169.254.255.255 Mask:255.255.0.0
UP BROADCAST MTU:1500 Metric:1
Interrupt:17 Base address:0xc000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2880 (2.8 KB) TX bytes:2880 (2.8 KB)
ppp0 Link encap:Point-to-Point Protocol
inet addr:187.90.11.172 P-t-P:10.64.64.64 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:4396 errors:0 dropped:0 overruns:0 frame:0
TX packets:4391 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:2700934 (2.7 MB) TX bytes:533106 (533.1 KB)
-------------------------
* V. querying DHCP...
There is already a pid file /var/run/dhclient.pid with pid 3062
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.3
Copyright 2004-2009 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth1/00:23:4d:c1:4e:cc
Sending on LPF/eth1/00:23:4d:c1:4e:cc
Listening on LPF/eth0/00:21:70:ae:6d:10
Sending on LPF/eth0/00:21:70:ae:6d:10
Sending on Socket/fallback
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 14
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 13
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
-------------------------
* VI. querying nslookup google.com...
Server: 200.220.227.57
Address: 200.220.227.57#53
Non-authoritative answer:
Name: google.com
Address: 74.125.229.48
Name: google.com
Address: 74.125.229.49
Name: google.com
Address: 74.125.229.50
Name: google.com
Address: 74.125.229.51
Name: google.com
Address: 74.125.229.52
Code: Select all
Found 4 processes that could cause trouble.If airodump-ng, aireplay-ng or airtun-ng stops working after
a short period of time, you may want to kill (some of) them!
PID Name
1044 NetworkManager
1050 avahi-daemon
1052 avahi-daemon
1076 wpa_supplicant
Interface Chipset Driver
eth1 Unknown wl (monitor mode enabled)
0c:00.0 Network controller: Broadcom Corporation BCM4322 802.11a/b/g/n Wireless LAN Controller (rev 01)
Subsystem: Dell Wireless 1510 Wireless-N WLAN Mini-Card
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 17
Region 0: Memory at f1ffc000 (64-bit, non-prefetchable)
Capabilities: <access denied>
Kernel driver in use: wl
Kernel modules: wl, ssb
Code: Select all
ioctl(SIOCSIWMODE) failed: Invalid argumentARP linktype is set to 1 (Ethernet) - expected ARPHRD_IEEE80211,
ARPHRD_IEEE80211_FULL or ARPHRD_IEEE80211_PRISM instead. Make
sure RFMON is enabled: run 'airmon-ng start eth1 <#>'
Sysfs injection support was not found either.
I also tried:
ioctl(SIOCSIWMODE) failed: Invalid argument
ARP linktype is set to 1 (Ethernet) - expected ARPHRD_IEEE80211,
ARPHRD_IEEE80211_FULL or ARPHRD_IEEE80211_PRISM instead. Make
sure RFMON is enabled: run 'airmon-ng start eth1 <#>'
Sysfs injection support was not found either.
If that is needed I really want to provide additional information, but I can only respond on helpfull answers and not on people replying without helping. You suggest me to look at 'How to Ask Questions the Smart Way' I suggest you 'How to Read Questions the Smart Way' since you did not read that the chip I was talking about was the BCM 4313 which could be seen in the thread title and from the lspci output. If I didn't do a search I wouldn't post this question. There is only one topic on this chip that ends with the proprietary broadcom driver and my question was about the b43 or new brcm43xx driver.
I also wrote (maybe you missed it) that I used the firmware package installer and offcourse verified that it installed the firmware files in the right place. The chip is simply not detected and even if it was then various dmesg or other logs would show any error or other information about it and they simply don't. Do a google search on b43 and bcm 4313 and you will see a lot more people having trouble on the b43/bcm4313 combination. So my question was plain and simple if anyone succeeded to get this chip in rfom mode wich can only be done with b43 or brcm43xx.
So I really appreciate the help, but try to be constructive without judging someones intentions. Kismet or any other rfmon program can also be used for legit purposes to find out channel occupation, signal strength and interference from other stations. Wich I need for network testing purposes.
I also wrote (maybe you missed it) that I used the firmware package installer and offcourse verified that it installed the firmware files in the right place. The chip is simply not detected and even if it was then various dmesg or other logs would show any error or other information about it and they simply don't. Do a google search on b43 and bcm 4313 and you will see a lot more people having trouble on the b43/bcm4313 combination. So my question was plain and simple if anyone succeeded to get this chip in rfom mode wich can only be done with b43 or brcm43xx.
So I really appreciate the help, but try to be constructive without judging someones intentions. Kismet or any other rfmon program can also be used for legit purposes to find out channel occupation, signal strength and interference from other stations. Wich I need for network testing purposes.