50% frames missing on kali about rtl8812au HOT 15 OPEN

Update: similar behavior with linux-mint (this time using 4.3.2.1), though I noticed that when the LED on the card would blink fast (twice per second) then a flood of beacon frames would be seen in tshark. Otherwise when the LED was blinking slow - most of the time (once every two seconds), beacon frames were not there.

from rtl8812au.

I'm seeing similar behavior on the latest build of Raspian.

from rtl8812au.

I have similar issues with AWUS036AC, efficiency is less than classic AWUS036H.

from rtl8812au.

I have similar issues with AWUS036AC, efficiency is less than classic AWUS036H.

Why would you expect more?
The old AWUS036H is still the best option for 2.4 Ghz hacking.
And you are using a "low cost" version of the AWUS036ACH (the hgih power version with rtl8812au) which would be more comparable with AWUS036H.
I also use Kali Linux with AWUS036ACH and i can grab instantly the full 4-way handshake with some desaut'.
WPS cracking without a single error or time out with -80dBm reception conditions.
There is no 50% lost of packet a with the driver, I can ensure you that.

from rtl8812au.

from rtl8812au.

No? 😺
Well.... antennas have absolutely nothing to do with this, they have the same gain (5dBi) because they are the sames in both devices (i tried both and you did not) .
Why you say "no"?
Believe it or not you do not get the same with the 30€ device than the 60€ one.. Yes, life is a bitch I know , I know.... Believe it or not the hardware are very different if you open them and really check what is inside...
Your device performance are comparable to TP-Link Archer T4UH which is more or less at the same price (the alfa antennas are removable and better)
Anyway that is offtopic and it is not very important what you believe or what I say about AWOS036AC performances compared with other devices...
What is certain at this point is that there is not at all 50% of packet loss with the driver (in Kali or wherever). With such lost you wouldn't be able to send a single PIN with reaver....

from rtl8812au.

Okay - you are correct in that no hardware is exactly the same, but if you open it up I'm pretty sure the big metal square houses the power amplifier. Anyway - even if the RSSI is way different between the two, I ran an experiment with both adapters about 2 feet from the AP, so we should be at least seeing beacon frames consistently, about 10 per second, from each adapter, when capturing from both interfaces on wireshark. However, in most cases the 036ac does not even see the beacon frames. Airodump captures are also off...see below comparison...note the ESSID Mifi* is the AP that is two feet away:

ALFA AWUS051NH - Channel 1, 10 second capture
CH 1 ][ Elapsed: 6 s ][ 2017-04-06 08:06

BSSID PWR RXQ Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID

00:7F:28:69::F3 -9 8 103 40 4 1 54e. WPA2 CCMP PSK MiFi
60:A4:4C:21::04 -36 0 1 1 0 157 54e WPA2 CCMP PSK welcome-
9C:34:26:95::18 -70 1 0 0 0 1 54e. WPA2 CCMP PSK bik
10:86:8C:DC::08 -72 3 0 0 0 1 54e. WPA2 CCMP PSK Domin
AE:34:26:95::18 -72 0 1 0 0 1 54e. OPN xfinitywif
88:DC:96:3D::88 -73 61 99 0 0 1 54e. WPA2 CCMP PSK CheeseL

BSSID STATION PWR Rate Lost Frames Probe

(not associated) B8:27:EB:D6::1A -28 0 - 1 9 3
00:7F:28:69::F3 B8:27:EB:3A::E2 -1 0e- 0 0 1
00:7F:28:69::F3 B8:27:EB:61::EE -38 0e- 0e 0 2
00:7F:28:69::F3 02:22:91:00::04 -24 0 - 0e 0 6
00:7F:28:69::F3 4C:66:41:E7::7B -18 0 -24 0 4
00:7F:28:69::F3 B8:27:EB:28:*:83 -22 0e- 0e 0 2

ALFA AWUS036AC - Channel 1, 10 second capture
CH 1 ][ Elapsed: 12 s ][ 2017-04-06 08:13 ][ fixed channel wlan2: -1

BSSID PWR RXQ Beacons #Data, #/s CH MB ENC CIPHER AUTH E

00:7F:28:69:*:F3 -18 0 1 0 0 1 54e. WPA2 CCMP PSK M

BSSID STATION PWR Rate Lost Frames Probe

(not associated) E8:4E:06:3E::2E -71 0 - 1 18 8
00:7F:28:69::F3 02:22:91:00:*:04 -32 0 - 6 0 2

ALFA AWUS036AC - Channel 1, captured about 20 seconds to include when blue light blinks fast - and most of the stuff appears when the blue light blinks fast:
Note that the channels are not just limited to channel 1, even though airodump is set with --channel 1

CH 1 ][ Elapsed: 18 s ][ 2017-04-06 08:14 ][ fixed channel wlan2: -1

BSSID PWR RXQ Beacons #Data, #/s CH MB ENC CIPHER AUTH ESSID

60:A4:4C:21::00 -35 0 8 1 0 11 54e WPA2 CCMP PSK welcom
22:86:8C:DC::08 -79 0 3 0 0 1 54e. OPN xfinitywif
5C:96:9D:65::BF -30 33 8 5 0 6 54e. WPA2 CCMP PSK welcome 2
00:7F:28:69::F3 -25 0 15 9 0 1 54e. WPA2 CCMP PSK MiFi
30:B5:C2:B9::EA -51 18 6 0 0 6 54e. WPA2 CCMP PSK Yodel_2.
F8:E4:FB:4A::B0 -61 10 5 0 0 6 54e. WPA2 CCMP PSK 8JYV
00:26:62:A6::F2 -73 0 2 0 0 6 54e. WEP WEP 5YUH
00:18:01:EE::C8 -72 7 4 0 0 6 54e. WEP WEP FSGH
88:DC:96:3D::88 -73 17 13 0 0 1 54e. WPA2 CCMP PSK CheeseL
AE:34:26:95::18 -80 16 10 0 0 1 54e. OPN xfinitywifi
10:86:8C:DC::08 -76 6 2 0 0 1 54e. WPA2 CCMP PSK Domin
DE:34:26:95::18 -81 17 9 0 0 1 54e. WPA2 CCMP MGT <length: 0>
9E:34:26:95::18 -80 17 11 0 0 1 54e. WPA2 CCMP PSK <length: 0>
BE:34:26:95::18 -80 19 12 0 0 1 54e. WPA2 CCMP PSK <length: 0>
9C:34:26:95::18 -81 16 11 0 0 1 54e. WPA2 CCMP PSK bik*
52:86:8C:DC::08 -82 11 7 0 0 1 54e. WPA2 CCMP MGT <length: 0>
12:86:8C:DC::08 -81 15 8 0 0 1 54e. WPA2 CCMP PSK <length: 0>

BSSID STATION PWR Rate Lost Frames Probe

(not associated) 78:DD:08:D9:07:59 -33 0 - 1 0 1 welcom*

from rtl8812au.

pablocyber

Will you check v5.1.5?

from rtl8812au.

I just compiled and loaded the v5.1.5 driver from uminokoe/rtl8812AU/tree/driver-5.1.5 on rpi 4.1.12-v7+. I was able to put into monitor mode but unable to change channels (it was stuck on channel 1). Injection using aireplay --test was not working for me.
Next I tried mk-fg/rtl8812au and I was able to change channels, inject, and monitor most data rates. The similar issue to 4.3.2.1 with datarates. Because my phone (I suspect most phones) run 2x2 802.11 AC, the highest supported rate (on a 20mhz channel) by this driver appears to be 156 Mbps (I can see those occasionally on wireshark). Because it is not decoding the 173 Mbps frames (the phone tries to connect at the highest rate) - I miss most of the data frame traffic in wireshark, and instead only see "VHT NDP Announcement" and "Ack" control frames as evidence that invisible traffic is still flowing.
I will check v5.1.5 variants on Kali next.

from rtl8812au.

update: I couldn't get uminokoe version to compile on Kali 4.9.0-kali3-amd64. Maybe there is something I should change in the makefile? mk-fg version would compile but crash the kernel when I tried iwconfig wlan1 mode monitor.

from rtl8812au.

I just compiled and loaded the v5.1.5 driver from uminokoe/rtl8812AU/tree/driver-5.1.5 on rpi 4.1.12-v7+.

Clone and complie the v5.1.5 driver from this repo.

from rtl8812au.

I just compiled and loaded the v5.1.5 driver from uminokoe/rtl8812AU/tree/driver-5.1.5 on rpi 4.1.12-v7+.

Clone and complie the v5.1.5 driver from this repo.

I tried to add the flag CONFIG_PLATFORM_ARM_RPI = y to the makefile but it says recipe for target 'modules' failed. I tried the mk-fg Makefile and the 4.3.2.1 Makefile also. Unfortunately I don't know how to edit Makefiles /recipies very well to get it to compile for the rpi.

from rtl8812au.

Restore the original Makefile and follow the instructions #10.

from rtl8812au.

Thanks I had forgotten about that. I just compiled 5.1.5 from this repo for rpi3. Same issue with missing certain VHT datarates exists.
I also just tried on kali3-amd64 and same issue with missing a lot of frames except when the light blinks fast.

from rtl8812au.

how can I cross compile the kernel , I am using the raspy zero w, thx so much

from rtl8812au.