I did follow your steps but when i do like but i have some probs..
root@bt:~# airmon-ng
Interface Chipset Driver
wlan0 Unknown ar9170usb - [phy0]
why is the chipset unknown?
Printable View
I did follow your steps but when i do like but i have some probs..
root@bt:~# airmon-ng
Interface Chipset Driver
wlan0 Unknown ar9170usb - [phy0]
why is the chipset unknown?
The DWA-160A1 and DWA-160A2 both are same chipset (ar9170). The DWA-160B has a ralink chipset.Quote:
I have the D-Link DWA-160A2 (version A i think with a minor revision?).
Is this the same chipset as the DWA-160A or does it have the DWA-160B chipset?
Your lsmod output shows that you don't have any of the wireless modules loaded. To get all the modules loaded try runningQuote:
Needless to say my USB adapter isnt working, just my virtual ethernet connection to my onboard wireless card. The light on the USB is always off when mounted by VWware. Backtrack can see my device as an EHCI Host Controller - 11n adapter. Here are the details from backtrack.
If its still not working after that, it may be a VMware issue(I don't know shit about VMware).Code:modprobe -a ath ar9170usb mac80211 cfg80211 rfkill_backport led_class
--------------------------------------------------------------------
--------------------------------------------------------------------
The only reason it's unknown is because of:Quote:
I did follow your steps but when i do like but i have some probs..
why is the chipset unknown?Code:root@bt:~# airmon-ng
Interface Chipset Driver
wlan0 Unknown ar9170usb - [phy0]
/usr/sbin/airmon-ng
line 174it should beCode:if [ x$DRIVER = "xOtus" -o x$DRIVER = "xarusb_lnx" -o x$DRIVER = "xar9170" ]
line 174Code:if [ x$DRIVER = "xOtus" -o x$DRIVER = "xarusb_lnx" -o x$DRIVER = "xar9170usb" ]
thanks man that solved it :)
Hey thanks so much worked on the first try, but there is something wrong when I have them both on and I'm using my internal wireless network card the light keeps going on and off like it keeps turning on and off the page still loads but a tiny bit slower. What can I do to not make them conflict with eatch other.
Hi dustyboner,
Thanks a lot for your help, is this working with AirPcap TX?
can u run airodump with this driver and i have wnda3100
i have vmware 7 with win 7
thanks
the AirPcap TX has a different chipset than the NX. It won't work with the ar9170usb driver but probably will work with BT4. I think it uses the ath5k drivers.
-----------------------------------------------------------------------
You should be able to. Injection/monitor mode works, but i haven't tested it with vmware. Try it and let us know if it works.Quote:
can u run airodump with this driver and i have wnda3100
i have vmware 7 with win 7
Thanks for the tutorial, Dustyboner.
But I have something to ask.
I just bought TL WN821N usb wifi adapter, and has done like what u said. And it looks like it has been detected as wlan1 ( I use laptop, so wlan0 is for internal wifi ).
What I want to ask is about airmon-ng. I type this :
#airmon-ng
#airmon-ng start wlan1
#airodump-ng
after that it began to monitor,, but after a while (less than 1 minute) , my system seems to freeze, with caps lock light on and off.
Is that a problem with the wifi adapter?
i get this when i try airodump with wnda3100
root@bt:~# airodump-ng ath0
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 ath0 <#>'
Sysfs injection support was not found either.
dont know what its mean but is seem dont work can someone help thanks
Thanks so much for the tutorial Dustyboner. I just bought the TL-WN821N and was having issues until I ran across your write-up. Each set of the aircrack tools is working great now, thx again.