Reply With QuoteI'd be lookiing at what driver Ubuntu is using and trying to get that installed.
Is Kali using rt3572sta or the rt2800? Or something else?
Junior Member
Hy!
I have an Alfa awus051nh (v2) and using Kali 2017.1 installed
https://wikidevi.com/wiki/ALFA_Network_AWUS051NH_v2
The FIRST bad sign is that the device is too HOT !!!Code:lsusb: Bus 001 Device 008: ID 148f:3572 Ralink Technology, Corp. RT3572 Wireless Adapter
The SECOND bad sign is that the MAC address isnt equal to the manufacturer MAC address.
(manufacturer mac address : 00:C0:CA:xx:xx:xx)
SO, the problem is: i cant use this wifi dongle. I cant see and cant connect to any AP.Code:ifconfig wlan1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 12:0f:24:db:8a:ad txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
With Aircrack-ng:
1, Monitor mode IS working. (airmon-ng check kill does not matter, the result is the same with/without it)
2, Pocket Injection test IS NOT working.Code:PHY Interface Driver Chipset phy0 wlan0 ath10k_pci Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) phy3 wlan1 rt2800usb Ralink Technology, Corp. RT3572 (mac80211 monitor mode vif enabled for [phy3]wlan1 on [phy3]wlan1mon) (mac80211 station mode vif disabled for [phy3]wlan1)
3, airodump-ng IS working but its useless ( internal wifi card with network manager list 6 ap)Code:aireplay-ng -9 wlan1mon 19:20:27 Trying broadcast probe requests... 19:20:29 No Answer... 19:20:29 Found 0 APs
4, handshake: obviously cant captureCode:CH 1 ][ Elapsed: 3 mins ][ 2017-09-11 19:38 BSSID PWR Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID xx:xx:xx:xx:xx:xx -79 133 28 0 6 54e. WPA2 CCMP PSK myEssid BSSID STATION PWR Rate Lost Frames Probe (not associated) cc:cc:cc:cc:cc:cc -66 0 - 1 70 2 xx:xx:xx:xx:xx:xx aa:aa:aa:aa:aa:aa -76 0 - 1 10 26
I dont understand this because i tried the wifi adapter on Ubuntu 16.04 and its work fine.
Thanks for your help!
some terminal command:
Code:rfkill list 10: phy4: Wireless LAN Soft blocked: no Hard blocked: noCode:dmesg | grep rt2800 [ 727.441592] usbcore: registered new interface driver rt2800usb [ 727.450284] rt2800usb 1-2:1.0: firmware: direct-loading firmware rt2870.bin [ 1933.057133] rt2800usb 1-5:1.0: firmware: direct-loading firmware rt2870.bin [ 7144.699328] rt2800usb 1-2:1.0: firmware: direct-loading firmware rt2870.bin [15643.966709] rt2800usb 1-2:1.0: firmware: direct-loading firmware rt2870.binlater :Code:iwconfig wlan1 IEEE 802.11 ESSID:off/any Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm Retry short long limit:2 RTS thr:off Fragment thr:off Encryption key:off Power Management:off
Code:dmesg [18495.478046] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready [18496.574912] ieee80211 phy4: rt2800usb_fill_rxdone: Error - Bad frame size 8208, forcing to 0 [18496.574921] ieee80211 phy4: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840 [18811.485189] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready
Junior Member
I'd be lookiing at what driver Ubuntu is using and trying to get that installed.
Is Kali using rt3572sta or the rt2800? Or something else?
Junior Member
rt2800usb
But i think the problem source is the linux kernel. I tried with Parrot Os and Ubuntu 17, and the driver also failed. All of this os uses linux kernel 4.10 and above
Senior Member
For what it's worth, I updated Kali yesterday, and was able to do monitor mode & packet injection with my AWUS051NH v.2. However, when using Kismet, it doesn't seem to hop on 5 ghz channels...just 2.4
Seems like I saw something similar to this posted at bugs.kali.org not long ago regarding the 4.12 kernel. I'm still searching there
Junior Member
I've had very similar issues with my Panda Wireless PAU09. Upgraded Kali and Virtual box. Tried all sorts of fixes.
Common issues:
1. Device gets hot
2. wlan0 shows up, no ip address assigned to it
Wireless networks occasionally show up, but I am unable to connect to any of them.
Code:# dmesg | tail [ 12.966195] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 13.895104] ieee80211 phy0: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -110 [ 18.937481] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 19.127533] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 19.429739] fuse init (API version 7.26) [ 353.939615] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 674.906813] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 731.321502] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 757.037451] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 764.294992] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not readyCode:lsusb Bus 001 Device 002: ID 148f:5572 Ralink Technology, Corp. RT5572 Wireless Adapter
Junior Member
Looks like I have the same issue with my Panda PAU09:
Some additional information:root@kali:~# lsusb
Bus 001 Device 002: ID 148f:5572 Ralink Technology, Corp. RT5572 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@kali:~# dmesg |grep rt2
[ 5.860724] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 5592, rev 0222 detected
[ 6.391182] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 000f detected
[ 6.423982] usbcore: registered new interface driver rt2800usb
[ 6.437618] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt2870.bin'
[ 6.442374] rt2800usb 1-1:1.0: firmware: direct-loading firmware rt2870.bin
[ 6.442378] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.36
[ 428.098309] ieee80211 phy0: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x101c with error -110
[ 428.212376] ieee80211 phy0: rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x101c with error -110
root@kali:~# ifconfig
eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 08:00:27:c1:f6:66 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 11511 bytes 996090 (972.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 11511 bytes 996090 (972.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether b2:de:9c:88:be:f7 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@kali:~# iwconfig
wlan0 IEEE 802.11 ESSIDff/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry short long limit:2 RTS thr
Encryption key
Power Management
lo no wireless extensions.
eth0 no wireless extensions.
root@kali:~# modinfo rt2800usb |grep 5572
alias: usb:v148Fp5572d*dc*dsc*dp*ic*isc*ip*in*
I'm running Kali in Virtualbox using a bridged adapter:
Attachment 2783
When checking the network settings with the machine powered off I actually selected a different name - the USB card:
network before startup.JPG
Not sure if that's a problem or not.
I checked the thread in the Ubuntu forums at https://ubuntuforums.org/showthread.php?t=1420984 but when I blacklist as described the device doesn't show up as wlan0 anymore.
Any help or pointers appreciated!
PS: If people feel I hijacked this thread, feel free to tell me to open a new one.
Junior Member
According to this thread in regards to another USB adapterits a linux firware issue.
The devs are aware and working on fix.
https://forums.kali.org/showthread.p...as-broken-Wifi
Panda support responded with this message when I contacted them:
There are a lot of problems with different WiFi adapters on Kali.
Kali is a rolling release and it will pick up all the changes from the
kernel. Some of the changes in the kernel will screw up some
WiFi adapter to operate correctly in Kali. Then Kali need to find and
fix the problem.
As of today. the monitor and packet injection feature is not suppored
by Kernel and Kali developers apply their own patch on the kernel
used in Kali. It will take times for Kali developers to fix the problems
created by the updates from the kernel development.
Let me know if you have any other questions.
Junior Member
hi! Have you solved this problem?Originally Posted by gorbedani
I have everything the same with Kali 2017.2 (((
Junior Member
No, I didnt find anything. I bought a tl-wn722n v1, but its not good for 5ghz.
Junior Member
Hi, bro! checked today in kali 2016.1 - works fine and does not get warm!
Apparently it's in the Linux kernel .. with 2017.1-3 kali has not figured it out yet
Senior Member
Monitor mode & packet injection are working fine on my Alfa AWUS051NH v.2 with the current kernel (4.14)
Junior Member
Alfa awus051nh (v2) works excellent using 2017.3 Kali
Junior Member
Well, my wireless adapter was working last week. Now no dice, assuming some update is causing an issue again.
Posting Permissions
