Page 2 of 2 FirstFirst 12
Results 51 to 93 of 93

Thread: How to install AWUS036ACH Drivers and getting it running?

  1. #51
    Join Date
    2018-Feb
    Posts
    1
    Hi All,

    I'm new to the forum (only just registered!), not so new to Linux as it's part of my job, but new to Kali.
    I wanted to share a small victory in getting the drivers for Alfa AWUS036ACH installed - finally!

    I've installed 4.13.0 Kali on HP 440 g3, applied all the updates and couldn't see the card apart from looking in the dmesg.
    I've been getting error messages about missing directories in /lib/modules/4.13.0-kali1-amd64/ and after reviewing few forums, reinstalling Kali twice, I've finally found the correct way.

    After installing Kali, I've obviously had to run the below, otherwise it didn't want to update.

    apt-key adv --keyserver hkp://keys.gnupg.net --recv-keys 7D8D0BF6

    Then, it was a matter of apt-get update, followed with apt-get upgrade.
    After that was finished, I've started searching for the correct headers for my version of Kali - without any luck, unfortunately.

    I've found an article on a different forum, which pointed me to the right direction.
    First, I had to check for a newer version by running the below:

    apt-cache search linux-image
    apt-cache search linux-headers

    The results shown that there's 4.14.0-kali3-amd64 available and now it was a matter of installing the headers for it as well.

    apt install linux-image-4.14.0-kali3-amd64
    apt install linux-headers-4.14.0-kali3-amd64

    Then a quick, necessary reboot:

    shutdown -r now

    Finally, when the system booted uname -r shows that the upgrade was successful.
    One last attempt to get all the latest updates and it's time to install the driver. Fingers crossed.

    apt install realtek-rtl88xxau-dkms

    After the installation was finished, I've plugged in the USB WIFI, checked dmesg - it's present, and now it shows when running airmon-ng!
    Success It took a bit of google'ing to figure this one out and even though my friends at work also used to use Kali, they never had problems installing wifi cards.

    Either way, if someone will find this useful - happy days! : )

  2. #52
    Join Date
    2018-Feb
    Location
    USA
    Posts
    5
    If I’m not mistaken the WiFi USB adapter you speak of should work right out the box. I am using Kali rolling version 3 on MacBook Pro dual boot, with reFINd. The adapter worked for me right out the box before my keyboard and touchbar. I had to downgrade my kernel to get the keyboard drivers to work from the newist rolling version. However with the WiFi adapter, try to plug it in and do a fresh install see if Kali recognizes the device, which it should, and then it should configure it correctly. This is on dual boot. I would take the gentleman’s advise on the matter for virtual machines because majority if not all computers have started using usb 3.0 for a while now. Gotta love Kali though ! hope it helps !

  3. #53
    Join Date
    2018-Feb
    Posts
    1
    Just registered to say THANK YOU to everyone on this thread, especially re4son and Bu5h1d0. It's taken all of yesterday, most of last night and up to now but it appears to be working! Packet injection testing ok! I'm going for a lie down now ha.

    I encountered loads of problems, including headers not installing, packages not located, updating and upgrading etc. I work in computing (datacentres) so am quite computer literate but I'm completely new to Kali and Linux. As annoying as the last 24 hours have been, I feel like I've also learnt a fair bit too.

    Cheers everyone

    Charlie.

  4. #54
    Join Date
    2013-Aug
    Location
    St. Louis, MO
    Posts
    1
    Hello all; after messing with this, and reading much in these forums, I am still having an issue. First, the environment: Windows 10 laptop, Fall Creator's pkg, ASUS with Intel internal wifi. I have this Alfa 036ach usb card. I'm running Kali Linux rolling 3.xx in VMWorkstation, version 14.xxx. I have gone round and round, updating everything. Rest assured, A. Host OS is updated, B. Guest Kali OS has been apt-get updated, upgraded, and dist-upgraded. I'm on Kernel 4.14.0-kali3-amd64, with the apt install realtek-rtl88xxau-dkms done. My issue is something that I've not seen mentioned elsewhere:
    Card works fine in Win10 environment. When I try and get it to work in the Kali VM, it's problematic. Even with everything updated. One of the specific issues I'm having is that Kali works fine with the internal card. Soon as I try and click over to the ALFA card, I either have it show up twice and it says that there is a driver error, and it wont let me unconnect back to the host (it just gives me an error box), or if I do get some type of connectivity, I keep getting "Destination Host Unreachable" errors if I attempt to ping 8.8.8.8. I can ping internal network and gateway fine.

    I have uninstalled and re-installed the drivers, and the problem persists. I am making sure that I turn off "WiFi" in Win10 environment, and make sure WiFi3 is turned on. Win10 box is working fine.

    So, right now, my Win10 box is connected to Alfa card. I ensured I uninstalled the card from device manager, then plugged it back in. Re-installed drivers. All good; it's been working fine for 30 minutes. It's Wifi is off, but WiFi3 is on. I can see the MAC address of the device, so I know it's the one working. I fired up VM Workstation v 14.xx, and launch Kali. I can hear Windows ding as it disconnects the USB and attempts to connect it to the Kali VM. The icon at lower right corner of the VM environment is showing Realtek 8812AU wireless card. Kali launches...

    and when I attempt to ping 8.8.8.8, Destination Host Unreachable! What the heck is going on with this??? If I click on the Network Manager and pull down wifi settings, it's all blank. But I can ping internal ip's such as 127.0.0.1, my gateway, and other machines. But I can't ping outside network.

    Now, if I change USB slots, I can hear Windows disconnecting from OS and back into the VM, and now suddenly it sees the network. I can see the list of networks in Network Manager. But still get Destination Host Unreachable msgs!!!

  5. #55
    Join Date
    2018-Feb
    Posts
    1
    Hi
    I want Installed driver for USB Wireless Adapter in Kali linux with this command:
    apt install realtek-rtl8821au-dkms
    but I saw this message: E:unable to locate package realtek-rtl8821au-dkms
    and when I typed ifconfig in terminal , I didn't have a wifi in my option which I can use it.

  6. #56
    Join Date
    2018-Feb
    Posts
    2
    Hello Guys,

    Kali Linux (Just registered to this forum today but has been reading through the past week) newbie here but venturing to IT Security. My background is on networking and I am still having an issue getting the wifi adapter working on my machine even after following re4son and Bu5h1d0's posts.

    I am getting this on dmesg after connecting the adapter:

    [ 414.598663] usb 1-2: new high-speed USB device number 5 using xhci_hcd
    [ 414.989343] usb 1-2: New USB device found, idVendor=0bda, idProduct=8812
    [ 414.989350] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [ 414.989355] usb 1-2: Product: 802.11n NIC
    [ 414.989358] usb 1-2: Manufacturer: Realtek
    [ 414.989361] usb 1-2: SerialNumber: *removed*
    [ 415.192704] 8812au: loading out-of-tree module taints kernel.
    [ 415.195064] 8812au: Unknown symbol __x86_indirect_thunk_rcx (err 0)
    [ 4286.162920] 8812au: Unknown symbol __x86_indirect_thunk_rcx (err 0)
    [ 4286.163030] 8812au: Unknown symbol __x86_indirect_thunk_rdx (err 0)
    [ 4286.163097] 8812au: Unknown symbol __x86_indirect_thunk_r13 (err 0)
    [ 4286.163103] 8812au: Unknown symbol __x86_indirect_thunk_r12 (err 0)
    [ 4286.163113] 8812au: Unknown symbol __x86_indirect_thunk_rax (err 0)
    [ 4286.163167] 8812au: Unknown symbol __x86_indirect_thunk_r8 (err 0)
    [ 4286.213568] 8812au: Unknown symbol __x86_indirect_thunk_rcx (err 0)
    [ 4286.213665] 8812au: Unknown symbol __x86_indirect_thunk_rdx (err 0)
    [ 4286.213753] 8812au: Unknown symbol __x86_indirect_thunk_r13 (err 0)
    [ 4286.213762] 8812au: Unknown symbol __x86_indirect_thunk_r12 (err 0)
    [ 4286.213776] 8812au: Unknown symbol __x86_indirect_thunk_rax (err 0)
    [ 4286.213853] 8812au: Unknown symbol __x86_indirect_thunk_r8 (err 0)



    I can see the adapter on lsusb but not in ifconfig.

    root@****:~# uname -r
    4.14.0-kali3-amd64

    I am also not seeing any errors on modinfo 8812au

    I am running Kali Linux 2018.1 on a VMWare workstation (for now) on a Win7 machine. Any help would be great!
    Last edited by harv3y; 2018-02-25 at 01:45. Reason: adding details

  7. #57
    Join Date
    2018-Feb
    Posts
    2
    UPDATE: I think i have solved my own issue. I had to uninstall the previous driver:


    apt remove realtek-rtl88xxau-dkms && apt purge realtek-rtl88xxau-dkms
    apt autoremove && apt autoclean
    reboot now

    For good measure; I also deleted the git clone folder (https://github.com/kimocoder/rtl8812au

    The only difference this time, beside doing
    apt-get update
    apt-get upgrade

    I continued with apt-get dist-upgrade. After it has completed, Its just a matter of following re4son's post.

    git clone https://github.com/kimocoder/rtl8812au
    cd rtl8812au
    make && make install

    Wireless adapter is now visible in lsusb, ifconfig and iwconfig. I'll test monitor and injection some time this week.

  8. #58
    Join Date
    2018-Feb
    Posts
    1

    Lightbulb

    Hi all.

    I got it kinda working...I have tried to deploy Alfa on Kali Linux on my laptop and PC ( No VM ware , standalone installs. ).
    On my PC and Laptop I have installed a fresh Kali Linux ( latest version ).
    After the installation I ran the following commands:
    Code:
    apt-get update
    apt-get upgrade 
    apt-get dist-upgrade 
    git clone https://github.com/kimocoder/rtl8812au
    cd rtl8812au
    make && make install (in case of errors run: sudo apt install linux-headers-amd64)
    And voila my Alfa started to giving blue light ( it's alive! )

    Code:
    ip link set wlan0 down
    iwconfig wlan0 mode monitor
    ip link set wlan0 up
    Tested monitor, injection - all working. Deauthed and received handshake.

    Now if someone could help me with the laptop. It's not working, it does detect my dongle lsusb , but it doesn't respond, seems to be switched off. And I think it might have something to do with the internal card and Atheros driver.
    Code:
    03:00.0 Ethernet controller [0200]: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller [1969:e091] (rev 13)
    04:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 20)
    And I don't know how to turn it off permanently so that I can only use dongle. Uninstall the drivers? I don't know how and if that would help anyway?

    Thanks in advance for brainstorming with me

    [Update] Funny - For my laptop I have apt install realtek-rtl88xxau-dkms and magic! started to work..
    Last edited by svg1mpr0r; 2018-03-01 at 18:21.

  9. #59
    Join Date
    2018-Mar
    Location
    Ontario, Canada
    Posts
    1
    I'm having an issue using this Adapter on Kali 2017.3 on VBox where it looks like it installs properly, i run "lsusb" after installation but BEFORE I plug in my adapter, and it obviously doesn't show up, I then plug it in and immediately run "lsusb" again and it shows up properly, i then hit "up arrow"+"Enter" and it no longer shows the adapter... so it shows it for a split second just as I plug it in, then disappears again. No idea whats going on... I'm new to Linux and I wouldn't be surprised if I did something wrong, but I am fairly confident I didn't, as I have reloaded snapshots of clean installs and tried installing the driver a few different ways now and it always ends up doing the same thing.

    Here is what it looks like:

    Code:
    root@kali:~# lsusb
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    root@kali:~# lsusb
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 005: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter
    Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    root@kali:~# lsusb
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Also, I dont see Wlan0 in iwconfig

    Code:
    root@kali:~# iwconfig
    lo        no wireless extensions.
    
    eth0      no wireless extensions.
    No idea whats going on...
    Last edited by RedKarma; 2018-03-02 at 17:41.

  10. #60
    Join Date
    2018-Mar
    Posts
    1

    Stumped

    Ok, I am stumped. I have installed these drivers every way shown in this thread. I have the latest version of Kali running on VMware Workstation 12 player. The drivers seem to install fine. When I plug in the AWUSO36ACH lsusb sees it for a few seconds then it disappears.
    Now you see it:
    Bus 001 Device 007: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
    Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
    Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

    Now you don't:
    root@kali:~# lsusb
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    Bus 002 Device 004: ID 0e0f:0008 VMware, Inc.
    Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
    Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

    I have updated, installed headers, installed and uninstalled drivers, purged, binged and everything you good people recommended. Nothing.

    Anyone have anything else to recommend?

  11. #61
    also am a bit stumped and dont knbow what i could be missing any suggestions would be great!

  12. #62
    Join Date
    2018-Mar
    Posts
    2
    Hi,

    Is anyone able to run Packet Injection on the latest Kali 2018.1 + updates with AWUS036ACH on VMware Workstation 14 Pro?

    Spent 3 days now, used all instruction here, without success. In some cases I can see SSID's but Pocket Injection not working.

    Please give me some advise.

  13. #63
    Join Date
    2018-Feb
    Posts
    2
    Quote Originally Posted by Trace View Post
    Hi dk89 ... it would appear this is quite a common problem with some hardware (including my own) ... I get terrible range from all drivers after 4.3.20.

    Check out this page on github where we've been discussing it with some driver developers and leave your hardware details as it may help towards a solution:

    https://github.com/aircrack-ng/rtl8812au/issues/77

    Also try out the new 5.2.20 drivers (didn't work for me) and let us know how you get on:

    https://github.com/kimocoder/rtl8812au-1
    Hi @Trace

    thanks for your info and the referenced issue. I kept reading it and it look like the newest 5.1.5 version of the driver solved the problem for me. Within my VM I can see the same networks my internal wifi displays - even with the default setting of 18dbm. Atm I'm playing with the tx-power. Had not much time for testing but so far it looks promising.

  14. #64
    Join Date
    2017-Dec
    Posts
    21
    Quote Originally Posted by dk89 View Post
    Hi @Trace

    thanks for your info and the referenced issue. I kept reading it and it look like the newest 5.1.5 version of the driver solved the problem for me. Within my VM I can see the same networks my internal wifi displays - even with the default setting of 18dbm. Atm I'm playing with the tx-power. Had not much time for testing but so far it looks promising.
    Cool you got it working.... but changing tx-power settings made no difference in the previous 5.1.5 driver (current tested with an ammeter) as you can see on the Github thread ...

  15. #65
    Join Date
    2018-Mar
    Posts
    2
    Hi All,

    I see many people having some problems with correct working drivers on AWUS036ACH. Can any one make it working on VMware workstation Pro?

    What do you suggest? What img shall I use 2017.1, 2017.3 or 2018.1? Which one is more stable?

  16. #66
    Join Date
    2018-Mar
    Posts
    1
    I tried all the weekend to install the 8812au driver on my Lenovo S10e (i686).
    No success.
    On a VM (amd64) I already had success after hours but on the 32bit version I always get errors when I modprobe the 8812au (No errors during make and make install, no complaining about missing linux-headers).
    Explicitly executed before make:
    apt-get install bc
    apt-get install linux-headers-$(uname -r)


    I tried both, the driver from kali rep (realtek-rtl88xxau-dkms) and the
    driver directly from github <https://github.com/kimocoder/rtl8812au>.

    Always removed and cleaned up the old driver before...(remove,purge,autoremove,autoclean, resp. make uninstall, clean)

    I ended up with symbol errors, as seen in the dmesg output.

    I am on a clean kali 2018.1 installation.
    Tried already to upgrade, but after rebooting the upgraded system the computer is totally frozen (no keys, no mouse).
    So I think it should work on a clean 2018.1 too...

    Code:
    root@kali:~/rtl8812au# make
    make -j 2 ARCH=i386 CROSS_COMPILE= -C /lib/modules/4.14.0-kali3-686-pae/build M=/root/rtl8812au  modules
    make[1]: Verzeichnis „/usr/src/linux-headers-4.14.0-kali3-686-pae“ wird betreten
      CC [M]  /root/rtl8812au/core/rtw_cmd.o
      CC [M]  /root/rtl8812au/core/rtw_security.o
      CC [M]  /root/rtl8812au/core/rtw_debug.o
      CC [M]  /root/rtl8812au/core/rtw_io.o
      CC [M]  /root/rtl8812au/core/rtw_ioctl_query.o
      CC [M]  /root/rtl8812au/core/rtw_ioctl_set.o
      CC [M]  /root/rtl8812au/core/rtw_ieee80211.o
      CC [M]  /root/rtl8812au/core/rtw_mlme.o
      CC [M]  /root/rtl8812au/core/rtw_mlme_ext.o
      CC [M]  /root/rtl8812au/core/rtw_mi.o
      CC [M]  /root/rtl8812au/core/rtw_wlan_util.o
      CC [M]  /root/rtl8812au/core/rtw_vht.o
      CC [M]  /root/rtl8812au/core/rtw_pwrctrl.o
      CC [M]  /root/rtl8812au/core/rtw_rf.o
      CC [M]  /root/rtl8812au/core/rtw_recv.o
      CC [M]  /root/rtl8812au/core/rtw_sta_mgt.o
      CC [M]  /root/rtl8812au/core/rtw_ap.o
      CC [M]  /root/rtl8812au/core/rtw_xmit.o
      CC [M]  /root/rtl8812au/core/rtw_p2p.o
      CC [M]  /root/rtl8812au/core/rtw_tdls.o
      CC [M]  /root/rtl8812au/core/rtw_br_ext.o
      CC [M]  /root/rtl8812au/core/rtw_iol.o
      CC [M]  /root/rtl8812au/core/rtw_sreset.o
      CC [M]  /root/rtl8812au/core/rtw_btcoex.o
      CC [M]  /root/rtl8812au/core/rtw_beamforming.o
      CC [M]  /root/rtl8812au/core/rtw_odm.o
      CC [M]  /root/rtl8812au/core/efuse/rtw_efuse.o
      CC [M]  /root/rtl8812au/os_dep/osdep_service.o
      CC [M]  /root/rtl8812au/os_dep/linux/os_intfs.o
      CC [M]  /root/rtl8812au/os_dep/linux/usb_intf.o
      CC [M]  /root/rtl8812au/os_dep/linux/usb_ops_linux.o
      CC [M]  /root/rtl8812au/os_dep/linux/ioctl_linux.o
      CC [M]  /root/rtl8812au/os_dep/linux/xmit_linux.o
      CC [M]  /root/rtl8812au/os_dep/linux/mlme_linux.o
      CC [M]  /root/rtl8812au/os_dep/linux/recv_linux.o
      CC [M]  /root/rtl8812au/os_dep/linux/ioctl_cfg80211.o
      CC [M]  /root/rtl8812au/os_dep/linux/rtw_cfgvendor.o
      CC [M]  /root/rtl8812au/os_dep/linux/wifi_regd.o
      CC [M]  /root/rtl8812au/os_dep/linux/rtw_android.o
      CC [M]  /root/rtl8812au/os_dep/linux/rtw_radiotap.o
      CC [M]  /root/rtl8812au/os_dep/linux/rtw_proc.o
      CC [M]  /root/rtl8812au/os_dep/linux/ioctl_mp.o
      CC [M]  /root/rtl8812au/hal/hal_intf.o
      CC [M]  /root/rtl8812au/hal/hal_com.o
      CC [M]  /root/rtl8812au/hal/hal_com_phycfg.o
      CC [M]  /root/rtl8812au/hal/hal_phy.o
      CC [M]  /root/rtl8812au/hal/hal_dm.o
      CC [M]  /root/rtl8812au/hal/hal_btcoex.o
      CC [M]  /root/rtl8812au/hal/hal_mp.o
      CC [M]  /root/rtl8812au/hal/hal_mcc.o
      CC [M]  /root/rtl8812au/hal/hal_hci/hal_usb.o
      CC [M]  /root/rtl8812au/hal/led/hal_usb_led.o
      CC [M]  /root/rtl8812au/hal/HalPwrSeqCmd.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/Hal8812PwrSeq.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/Hal8821APwrSeq.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/rtl8812a_xmit.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/rtl8812a_sreset.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/rtl8812a_hal_init.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/rtl8812a_phycfg.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/rtl8812a_rf6052.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/rtl8812a_dm.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/rtl8812a_rxdesc.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/rtl8812a_cmd.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/usb/usb_halinit.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/usb/rtl8812au_led.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/usb/rtl8812au_xmit.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/usb/rtl8812au_recv.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/usb/usb_ops_linux.o
      CC [M]  /root/rtl8812au/hal/efuse/rtl8812a/HalEfuseMask8812A_USB.o
      CC [M]  /root/rtl8812au/hal/efuse/rtl8812a/HalEfuseMask8821A_USB.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/hal8812a_fw.o
      CC [M]  /root/rtl8812au/hal/rtl8812a/hal8821a_fw.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_debug.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_antdiv.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_antdect.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_interface.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_hwconfig.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm.o
      CC [M]  /root/rtl8812au/hal/phydm/halphyrf_ce.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_edcaturbocheck.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_dig.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_pathdiv.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_rainfo.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_dynamicbbpowersaving.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_powertracking_ce.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_dynamictxpower.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_adaptivity.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_cfotracking.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_noisemonitor.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_acs.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_beamforming.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_dfs.o
      CC [M]  /root/rtl8812au/hal/phydm/txbf/halcomtxbf.o
      CC [M]  /root/rtl8812au/hal/phydm/txbf/haltxbfinterface.o
      CC [M]  /root/rtl8812au/hal/phydm/txbf/phydm_hal_txbf_api.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_kfree.o
      CC [M]  /root/rtl8812au/hal/phydm/phydm_ccx.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_fw.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_mac.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_bb.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_rf.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8812a/halphyrf_8812a_ce.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8812a/phydm_regconfig8812a.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8812a/phydm_rtl8812a.o
      CC [M]  /root/rtl8812au/hal/phydm/txbf/haltxbfjaguar.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8821a/halhwimg8821a_fw.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8821a/halhwimg8821a_mac.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8821a/halhwimg8821a_bb.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8821a/halhwimg8821a_rf.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8821a/halphyrf_8821a_ce.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8821a/phydm_regconfig8821a.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8821a/phydm_rtl8821a.o
      CC [M]  /root/rtl8812au/hal/phydm/rtl8821a/phydm_iqk_8821a_ce.o
      CC [M]  /root/rtl8812au/platform/platform_ops.o
      CC [M]  /root/rtl8812au/core/rtw_mp.o
      LD [M]  /root/rtl8812au/8812au.o
      Building modules, stage 2.
      MODPOST 1 modules
      CC      /root/rtl8812au/8812au.mod.o
      LD [M]  /root/rtl8812au/8812au.ko
    make[1]: Verzeichnis „/usr/src/linux-headers-4.14.0-kali3-686-pae“ wird verlassen
    root@kali:~/rtl8812au# make install
    install -p -m 644 8812au.ko  /lib/modules/4.14.0-kali3-686-pae/kernel/drivers/net/wireless/
    /sbin/depmod -a 4.14.0-kali3-686-pae
    root@kali:~/rtl8812au# modprobe 8812au
    modprobe: ERROR: could not insert '8812au': Unknown symbol in module, or unknown parameter (see dmesg)
    
    
    [ 4211.971644] 8812au: loading out-of-tree module taints kernel.
    [ 4211.976515] 8812au: Unknown symbol __x86_indirect_thunk_edx (err 0)
    [ 4211.976765] 8812au: Unknown symbol __x86_indirect_thunk_edi (err 0)
    [ 4211.976984] 8812au: Unknown symbol __x86_indirect_thunk_ecx (err 0)
    [ 4211.977220] 8812au: Unknown symbol __x86_indirect_thunk_esi (err 0)
    [ 4211.977366] 8812au: Unknown symbol __x86_indirect_thunk_ebx (err 0)
    [ 4211.977781] 8812au: Unknown symbol __x86_indirect_thunk_eax (err 0)
    root@kali:~/rtl8812au#
    Code:
    root@kali:~/rtl8812au# uname -a
    Linux kali 4.14.0-kali3-686-pae #1 SMP Debian 4.14.12-2kali1 (2018-01-08) i686 GNU/Linux

    I am clueless...All help welcome
    TIA

  17. #67
    Join Date
    2018-Apr
    Posts
    1
    Good evening ,
    I too, several users have encountered many problems in the installation of these blessed drivers of Kali; I use 4.14 kali3-amd64 / 2018.1 (updated, upgraded ) and when I was about to give it up I found the right solution and I hope it will help the people find themselves reading this post.
    So I performed the steps that are rightly recommended by those who participate in this discussion but with a variant that eventually turned out to be the solution. Let's move on to the commands:

    apt-get remove -y realtek-rtl88xxau-dkms

    apt-get purge realtek-rtl88xxau-dkms

    reboot

    apt-get install -y realtek-rtl88xxau-dkms

    Enjoy!

    I hope you can help!

    ~H.
    Last edited by HowL; 2018-04-30 at 06:36.

  18. #68
    Join Date
    2018-May
    Posts
    1
    Hi All,

    Did anybody manage to make the adapter work with Kali 2018.2?
    My Kali is running in VMWare Workstation 14 Pro on a Laptop Dell Latitude 7440 and I tried also on a Dell Precision 1700.
    The adapter is connected to a USB 3 port.

    I've installed the driver realtek-rtl88xxau-dkms and it seems it has been installed without any errors:

    root@kali:~# apt install realtek-rtl88xxau-dkms
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages were automatically installed and are no longer required:
    libhttp-parser2.7.1 libnfs8 libqgis-analysis2.18.17 libqgis-core2.18.17
    libqgis-gui2.18.17 libqgis-networkanalysis2.18.17 libqgis-server2.18.17
    libqgispython2.18.17 libsynctex1 libtcl8.5 libtk8.5 libx265-146 python3-h11
    tk8.5
    Use 'apt autoremove' to remove them.
    The following additional packages will be installed:
    dkms linux-compiler-gcc-7-x86 linux-headers-4.15.0-kali3-amd64
    linux-headers-4.15.0-kali3-common linux-headers-amd64 linux-kbuild-4.15
    Suggested packages:
    python3-apport
    The following NEW packages will be installed:
    dkms linux-compiler-gcc-7-x86 linux-headers-4.15.0-kali3-amd64
    linux-headers-4.15.0-kali3-common linux-headers-amd64 linux-kbuild-4.15
    realtek-rtl88xxau-dkms
    0 upgraded, 7 newly installed, 0 to remove and 0 not upgraded.
    Need to get 11.6 MB of archives.
    After this operation, 72.9 MB of additional disk space will be used.
    Do you want to continue? [Y/n] y
    Get:1 http://ftp.halifax.rwth-aachen.de/kali kali-rolling/main amd64 dkms all 2.3-3 [74.9 kB]
    Get:2 http://ftp.halifax.rwth-aachen.de/kali kali-rolling/main amd64 linux-compiler-gcc-7-x86 amd64 4.15.17-1kali1 [554 kB]
    Get:3 http://ftp.halifax.rwth-aachen.de/kali kali-rolling/main amd64 linux-headers-4.15.0-kali3-common all 4.15.17-1kali1 [7,938 kB]
    Get:4 http://ftp.halifax.rwth-aachen.de/kali kali-rolling/main amd64 linux-kbuild-4.15 amd64 4.15.17-1kali1 [796 kB]
    Get:5 http://ftp.halifax.rwth-aachen.de/kali kali-rolling/main amd64 linux-headers-4.15.0-kali3-amd64 amd64 4.15.17-1kali1 [471 kB]
    Get:6 http://ftp.halifax.rwth-aachen.de/kali kali-rolling/main amd64 linux-headers-amd64 amd64 4.15+92+kali1 [7,000 B]
    Get:7 http://ftp.halifax.rwth-aachen.de/kali kali-rolling/contrib amd64 realtek-rtl88xxau-dkms all 5.1.5~20180125-0kali1 [1,746 kB]
    Fetched 11.6 MB in 2s (5,976 kB/s)
    Selecting previously unselected package dkms.
    (Reading database ... 342191 files and directories currently installed.)
    Preparing to unpack .../0-dkms_2.3-3_all.deb ...
    Unpacking dkms (2.3-3) ...
    Selecting previously unselected package linux-compiler-gcc-7-x86.
    Preparing to unpack .../1-linux-compiler-gcc-7-x86_4.15.17-1kali1_amd64.deb ...
    Unpacking linux-compiler-gcc-7-x86 (4.15.17-1kali1) ...
    Selecting previously unselected package linux-headers-4.15.0-kali3-common.
    Preparing to unpack .../2-linux-headers-4.15.0-kali3-common_4.15.17-1kali1_all.deb ...
    Unpacking linux-headers-4.15.0-kali3-common (4.15.17-1kali1) ...
    Selecting previously unselected package linux-kbuild-4.15.
    Preparing to unpack .../3-linux-kbuild-4.15_4.15.17-1kali1_amd64.deb ...
    Unpacking linux-kbuild-4.15 (4.15.17-1kali1) ...
    Selecting previously unselected package linux-headers-4.15.0-kali3-amd64.
    Preparing to unpack .../4-linux-headers-4.15.0-kali3-amd64_4.15.17-1kali1_amd64.deb ...
    Unpacking linux-headers-4.15.0-kali3-amd64 (4.15.17-1kali1) ...
    Selecting previously unselected package linux-headers-amd64.
    Preparing to unpack .../5-linux-headers-amd64_4.15+92+kali1_amd64.deb ...
    Unpacking linux-headers-amd64 (4.15+92+kali1) ...
    Selecting previously unselected package realtek-rtl88xxau-dkms.
    Preparing to unpack .../6-realtek-rtl88xxau-dkms_5.1.5~20180125-0kali1_all.deb ...
    Unpacking realtek-rtl88xxau-dkms (5.1.5~20180125-0kali1) ...
    Setting up linux-kbuild-4.15 (4.15.17-1kali1) ...
    Setting up dkms (2.3-3) ...
    Setting up linux-headers-4.15.0-kali3-common (4.15.17-1kali1) ...
    Processing triggers for man-db (2.8.3-2) ...
    Setting up linux-compiler-gcc-7-x86 (4.15.17-1kali1) ...
    Setting up realtek-rtl88xxau-dkms (5.1.5~20180125-0kali1) ...
    Loading new realtek-rtl88xxau-5.1.5~20180125 DKMS files...
    Building for 4.15.0-kali3-amd64
    Building initial module for 4.15.0-kali3-amd64
    Done.


    8812au:
    Running module version sanity check.
    - Original module
    - No original module exists within this kernel
    - Installation
    - Installing to /lib/modules/4.15.0-kali3-amd64/updates/


    8814au.ko:
    Running module version sanity check.
    - Original module
    - No original module exists within this kernel
    - Installation
    - Installing to /lib/modules/4.15.0-kali3-amd64/updates/


    depmod.........


    DKMS: install completed.
    Setting up linux-headers-4.15.0-kali3-amd64 (4.15.17-1kali1) ...
    Setting up linux-headers-amd64 (4.15+92+kali1) ...
    root@kali:~#





    Though wlan0 is not showing up:

    iwconfig
    eth0 no wireless extensions.


    lo no wireless extensions.


    Then I uninstalled it:
    apt-get remove realtek-rtl88xxau-dkms

    apt-get purge realtek-rtl88xxau-dkms

    reboot



    And tried the driver from kimocodo:


    root@kali:~/rtl8812au# make && make install
    make -j 4 ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.15.0-kali3-amd64/build M=/root/rtl8812au modules
    make[1]: Entering directory '/usr/src/linux-headers-4.15.0-kali3-amd64'
    CC [M] /root/rtl8812au/core/rtw_cmd.o
    CC [M] /root/rtl8812au/core/rtw_security.o
    CC [M] /root/rtl8812au/core/rtw_debug.o
    CC [M] /root/rtl8812au/core/rtw_io.o
    CC [M] /root/rtl8812au/core/rtw_ioctl_query.o
    CC [M] /root/rtl8812au/core/rtw_ioctl_set.o
    CC [M] /root/rtl8812au/core/rtw_ieee80211.o
    CC [M] /root/rtl8812au/core/rtw_mlme.o
    CC [M] /root/rtl8812au/core/rtw_mlme_ext.o
    CC [M] /root/rtl8812au/core/rtw_mi.o
    CC [M] /root/rtl8812au/core/rtw_wlan_util.o
    CC [M] /root/rtl8812au/core/rtw_vht.o
    CC [M] /root/rtl8812au/core/rtw_pwrctrl.o
    CC [M] /root/rtl8812au/core/rtw_rf.o
    CC [M] /root/rtl8812au/core/rtw_recv.o
    CC [M] /root/rtl8812au/core/rtw_sta_mgt.o
    CC [M] /root/rtl8812au/core/rtw_ap.o
    CC [M] /root/rtl8812au/core/rtw_xmit.o
    CC [M] /root/rtl8812au/core/rtw_p2p.o
    CC [M] /root/rtl8812au/core/rtw_tdls.o
    CC [M] /root/rtl8812au/core/rtw_br_ext.o
    CC [M] /root/rtl8812au/core/rtw_iol.o
    CC [M] /root/rtl8812au/core/rtw_sreset.o
    CC [M] /root/rtl8812au/core/rtw_btcoex.o
    CC [M] /root/rtl8812au/core/rtw_beamforming.o
    CC [M] /root/rtl8812au/core/rtw_odm.o
    CC [M] /root/rtl8812au/core/efuse/rtw_efuse.o
    CC [M] /root/rtl8812au/os_dep/osdep_service.o
    CC [M] /root/rtl8812au/os_dep/linux/os_intfs.o
    CC [M] /root/rtl8812au/os_dep/linux/usb_intf.o
    CC [M] /root/rtl8812au/os_dep/linux/usb_ops_linux.o
    CC [M] /root/rtl8812au/os_dep/linux/ioctl_linux.o
    CC [M] /root/rtl8812au/os_dep/linux/xmit_linux.o
    CC [M] /root/rtl8812au/os_dep/linux/mlme_linux.o
    CC [M] /root/rtl8812au/os_dep/linux/recv_linux.o
    CC [M] /root/rtl8812au/os_dep/linux/ioctl_cfg80211.o
    CC [M] /root/rtl8812au/os_dep/linux/rtw_cfgvendor.o
    CC [M] /root/rtl8812au/os_dep/linux/wifi_regd.o
    CC [M] /root/rtl8812au/os_dep/linux/rtw_android.o
    CC [M] /root/rtl8812au/os_dep/linux/rtw_radiotap.o
    CC [M] /root/rtl8812au/os_dep/linux/rtw_proc.o
    CC [M] /root/rtl8812au/os_dep/linux/ioctl_mp.o
    CC [M] /root/rtl8812au/hal/hal_intf.o
    CC [M] /root/rtl8812au/hal/hal_com.o
    CC [M] /root/rtl8812au/hal/hal_com_phycfg.o
    CC [M] /root/rtl8812au/hal/hal_phy.o
    CC [M] /root/rtl8812au/hal/hal_dm.o
    CC [M] /root/rtl8812au/hal/hal_btcoex.o
    CC [M] /root/rtl8812au/hal/hal_mp.o
    CC [M] /root/rtl8812au/hal/hal_mcc.o
    CC [M] /root/rtl8812au/hal/hal_hci/hal_usb.o
    CC [M] /root/rtl8812au/hal/led/hal_usb_led.o
    CC [M] /root/rtl8812au/hal/HalPwrSeqCmd.o
    CC [M] /root/rtl8812au/hal/rtl8812a/Hal8812PwrSeq.o
    CC [M] /root/rtl8812au/hal/rtl8812a/Hal8821APwrSeq.o
    CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_xmit.o
    CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_sreset.o
    CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_hal_init.o
    CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_phycfg.o
    CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_rf6052.o
    CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_dm.o
    CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_rxdesc.o
    CC [M] /root/rtl8812au/hal/rtl8812a/rtl8812a_cmd.o
    CC [M] /root/rtl8812au/hal/rtl8812a/usb/usb_halinit.o
    CC [M] /root/rtl8812au/hal/rtl8812a/usb/rtl8812au_led.o
    CC [M] /root/rtl8812au/hal/rtl8812a/usb/rtl8812au_xmit.o
    CC [M] /root/rtl8812au/hal/rtl8812a/usb/rtl8812au_recv.o
    CC [M] /root/rtl8812au/hal/rtl8812a/usb/usb_ops_linux.o
    CC [M] /root/rtl8812au/hal/efuse/rtl8812a/HalEfuseMask8812A_USB.o
    CC [M] /root/rtl8812au/hal/efuse/rtl8812a/HalEfuseMask8821A_USB.o
    CC [M] /root/rtl8812au/hal/rtl8812a/hal8812a_fw.o
    CC [M] /root/rtl8812au/hal/rtl8812a/hal8821a_fw.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_debug.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_antdiv.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_antdect.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_interface.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_hwconfig.o
    CC [M] /root/rtl8812au/hal/phydm/phydm.o
    CC [M] /root/rtl8812au/hal/phydm/halphyrf_ce.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_edcaturbocheck.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_dig.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_pathdiv.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_rainfo.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_dynamicbbpowersaving.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_powertracking_ce.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_dynamictxpower.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_adaptivity.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_cfotracking.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_noisemonitor.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_acs.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_beamforming.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_dfs.o
    CC [M] /root/rtl8812au/hal/phydm/txbf/halcomtxbf.o
    CC [M] /root/rtl8812au/hal/phydm/txbf/haltxbfinterface.o
    CC [M] /root/rtl8812au/hal/phydm/txbf/phydm_hal_txbf_api.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_kfree.o
    CC [M] /root/rtl8812au/hal/phydm/phydm_ccx.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_fw.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_mac.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_bb.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_rf.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8812a/halphyrf_8812a_ce.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8812a/phydm_regconfig8812a.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8812a/phydm_rtl8812a.o
    CC [M] /root/rtl8812au/hal/phydm/txbf/haltxbfjaguar.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8821a/halhwimg8821a_fw.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8821a/halhwimg8821a_mac.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8821a/halhwimg8821a_bb.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8821a/halhwimg8821a_rf.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8821a/halphyrf_8821a_ce.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8821a/phydm_regconfig8821a.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8821a/phydm_rtl8821a.o
    CC [M] /root/rtl8812au/hal/phydm/rtl8821a/phydm_iqk_8821a_ce.o
    CC [M] /root/rtl8812au/platform/platform_ops.o
    CC [M] /root/rtl8812au/core/rtw_mp.o
    LD [M] /root/rtl8812au/8812au.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /root/rtl8812au/8812au.mod.o
    LD [M] /root/rtl8812au/8812au.ko
    make[1]: Leaving directory '/usr/src/linux-headers-4.15.0-kali3-amd64'
    install -p -m 644 8812au.ko /lib/modules/4.15.0-kali3-amd64/kernel/drivers/net/wireless/
    /sbin/depmod -a 4.15.0-kali3-amd64


    Same problem, wlan0 is not showing up:


    iwconfig
    eth0 no wireless extensions.


    lo no wireless extensions.


    I'd highly appreciate your response. I don't have any ideeas left...
    Thanks a lot.

    Update: I managed to make it working.
    I've set the USB of the host in VMWare from 2.0 to 3.0.
    It has though a strange behaviour: sometime it finds a lot of SSID, sometime only 4-5... most of the time it finds only 2,4 GHz of my AP, but not the 5GHz.

    Do you have any advice?
    Thanks!

    Regards,
    crymy
    Last edited by crymy; 2018-05-08 at 13:45.

  19. #69
    Join Date
    2018-May
    Posts
    8
    I have the same unit and can not get it to work. I plugged in another antenna and it works fine so it's not the OS. I emailed ALFA twice but got no answer. I would not advise anyone to by there stuff. I will keep trying and good luck to you.

  20. #70
    Join Date
    2018-May
    Posts
    1
    Quote Originally Posted by cold iron View Post
    I have the same unit and can not get it to work. I plugged in another antenna and it works fine so it's not the OS. I emailed ALFA twice but got no answer. I would not advise anyone to by there stuff. I will keep trying and good luck to you.
    Are you running in VM?

    Across 3 different machines (all Virtualbox with extensions), I can get it installed and up, but after a reboot or two it'll die and never come back, ever.

    I tried dual booting with 2017.3 and can get it to work and inject but with USB3 power limitations on 5g. USB2 seems to work fine. Pain in the *** adapter without a proper driver (that can run through VM), when my $8 adapter works just fine, with the same range and no 5g.

  21. #71
    Join Date
    2018-May
    Posts
    1
    First time post and wanting to help out.
    I picked up the AWUS036ACH after reading that it was one of the more supported adapters from Alfa. Spent the last few days messing around and here's my results.
    Dont bother trying with a previous version as the rolling releases don't automatically let you update. (keys are out of synch for apt-get update).

    Installed 2018.2 as it was the latest I could grab.
    updated, upgraded all packages to be current. (apt-get update && apt-get upgrade)

    Then, went through the dkms install but it would complain that the headers werent installed. So i had to manually install those. Anyone with a fresh install of 2018.2 is going to have to to this.


    root@illium:~/Downloads# apt-get install realtek-rtl88xxau-dkms
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages were automatically installed and are no longer required:
    libfile-copy-recursive-perl python-unicodecsv python3-configargparse python3-flask python3-itsdangerous python3-jsbeautifier
    python3-pyinotify python3-simplejson python3-werkzeug
    Use 'apt autoremove' to remove them.
    The following NEW packages will be installed:
    realtek-rtl88xxau-dkms
    0 upgraded, 1 newly installed, 0 to remove and 77 not upgraded.
    Need to get 1,745 kB of archives.
    After this operation, 18.1 MB of additional disk space will be used.
    Get:1 http://kali.mirror.globo.tech/kali kali-rolling/contrib amd64 realtek-rtl88xxau-dkms all 5.1.5~20180513-0kali1 [1,745 kB]
    Fetched 1,745 kB in 2s (956 kB/s)
    Selecting previously unselected package realtek-rtl88xxau-dkms.
    (Reading database ... 351805 files and directories currently installed.)
    Preparing to unpack .../realtek-rtl88xxau-dkms_5.1.5~20180513-0kali1_all.deb ...
    Unpacking realtek-rtl88xxau-dkms (5.1.5~20180513-0kali1) ...
    Setting up realtek-rtl88xxau-dkms (5.1.5~20180513-0kali1) ...
    Loading new realtek-rtl88xxau-5.1.5~20180513 DKMS files...
    Building for 4.15.0-kali2-amd64
    Module build for kernel 4.15.0-kali2-amd64 was skipped since the
    kernel headers for this kernel does not seem to be installed.


    Okay, removed it using apt-get remove realtek-rtl88xxau-dkms
    Okay, so I guess i have to find the headers...


    root@illium:~/Downloads# uname -r
    4.15.0-kali2-amd64


    Checked here from another post I was reading to go find the headers I need: http://mirror.internode.on.net/pub/k.../main/l/linux/

    root@illium:~/Downloads# wget http://mirror.internode.on.net/pub/k...1kali1_all.deb
    root@illium:~/Downloads# wget http://mirror.internode.on.net/pub/k...ali1_amd64.deb

    Install em..



    root@illium:~/Downloads# dpkg -i linux-headers-4.15.0-kali2-common_4.15.11-1kali1_all.deb
    root@illium:~/Downloads# dpkg -i ./linux-headers-4.15.0-kali2-amd64_4.15.11-1kali1_amd64.deb

    Then install the driver again

    root@illium:~/Downloads# apt-get install realtek-rtl88xxau-dkms
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    The following packages were automatically installed and are no longer required:
    libfile-copy-recursive-perl python-unicodecsv python3-configargparse python3-flask python3-itsdangerous python3-jsbeautifier
    python3-pyinotify python3-simplejson python3-werkzeug
    Use 'apt autoremove' to remove them.
    The following NEW packages will be installed:
    realtek-rtl88xxau-dkms
    0 upgraded, 1 newly installed, 0 to remove and 77 not upgraded.
    Need to get 0 B/1,745 kB of archives.
    After this operation, 18.1 MB of additional disk space will be used.
    Selecting previously unselected package realtek-rtl88xxau-dkms.
    (Reading database ... 368104 files and directories currently installed.)
    Preparing to unpack .../realtek-rtl88xxau-dkms_5.1.5~20180513-0kali1_all.deb ...
    Unpacking realtek-rtl88xxau-dkms (5.1.5~20180513-0kali1) ...
    Setting up realtek-rtl88xxau-dkms (5.1.5~20180513-0kali1) ...
    Loading new realtek-rtl88xxau-5.1.5~20180513 DKMS files...
    Building for 4.15.0-kali2-amd64
    Building initial module for 4.15.0-kali2-amd64
    Done.


    8812au:
    Running module version sanity check.
    - Original module
    - No original module exists within this kernel
    - Installation
    - Installing to /lib/modules/4.15.0-kali2-amd64/updates/


    8814au.ko:
    Running module version sanity check.
    - Original module
    - No original module exists within this kernel
    - Installation
    - Installing to /lib/modules/4.15.0-kali2-amd64/updates/


    depmod.....


    DKMS: install completed.

    Yay! rebooted just to be safe, and lo and behold the adapter shows up under iwconfig.

    headache but only because I'm not knowledgeable about header versions.

    Hope this helps others with the same adapter and latest version.

  22. #72
    Join Date
    2018-Jun
    Posts
    1

    I want to said thanks

    Im also new and having using linux for a while...Greeting to all of you and for all the effort...Thanks!!!
    having the device sitting for a few days finally found make it to work I follow the step and boom is running like a 991 Turbo S. I have the same exact issue about the headers and your workaround make a perfect solution for me.
    Im using kali boot on SD USB 256 GB persistence on Asus w/12 gb

    Again thanks!!!!



    Quote Originally Posted by psielke View Post
    Hi All,

    I'm new to the forum (only just registered!), not so new to Linux as it's part of my job, but new to Kali.
    I wanted to share a small victory in getting the drivers for Alfa AWUS036ACH installed - finally!

    I've installed 4.13.0 Kali on HP 440 g3, applied all the updates and couldn't see the card apart from looking in the dmesg.
    I've been getting error messages about missing directories in /lib/modules/4.13.0-kali1-amd64/ and after reviewing few forums, reinstalling Kali twice, I've finally found the correct way.

    After installing Kali, I've obviously had to run the below, otherwise it didn't want to update.

    apt-key adv --keyserver hkp://keys.gnupg.net --recv-keys 7D8D0BF6

    Then, it was a matter of apt-get update, followed with apt-get upgrade.
    After that was finished, I've started searching for the correct headers for my version of Kali - without any luck, unfortunately.

    I've found an article on a different forum, which pointed me to the right direction.
    First, I had to check for a newer version by running the below:

    apt-cache search linux-image
    apt-cache search linux-headers

    The results shown that there's 4.14.0-kali3-amd64 available and now it was a matter of installing the headers for it as well.

    apt install linux-image-4.14.0-kali3-amd64
    apt install linux-headers-4.14.0-kali3-amd64

    Then a quick, necessary reboot:

    shutdown -r now

    Finally, when the system booted uname -r shows that the upgrade was successful.
    One last attempt to get all the latest updates and it's time to install the driver. Fingers crossed.

    apt install realtek-rtl88xxau-dkms

    After the installation was finished, I've plugged in the USB WIFI, checked dmesg - it's present, and now it shows when running airmon-ng!
    Success It took a bit of google'ing to figure this one out and even though my friends at work also used to use Kali, they never had problems installing wifi cards.

    Either way, if someone will find this useful - happy days! : )

  23. #73
    Join Date
    2013-Jun
    Posts
    79
    You would think that the latest kali image would fully support this card by now! Seems like quite the popular card these days.

  24. #74
    Join Date
    2018-May
    Posts
    8
    Stringbean..you did it. Thanks!!
    I finely got the light to turn on!! That's a big deal for me. Only problem is when I try to get into monitor mode I get a message that it failed! It see's all the wifi stations around me fine. And it can open a web site.
    Any ideas?

  25. #75
    Join Date
    2018-Jul
    Posts
    1
    Hi! i have tried for three days now without success.
    Im running a raspberry pi 3 with kali linux (sticky finger)
    with ASUS awus036AC

    i have kali linux full installation
    with recent apt-upgrade/update

    i ve cloned the realtek driver and installed it.

    before typing any cmds. ifconfig says
    (mac id marked with xx)
    wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.1.xx netmask 255.255.255.0 broadcast 192.168.1.255
    inet6 fe80::46cd:xxxx:cb47:xxxx prefixlen 64 scopeid 0x20<link>
    ether b8:27:eb:xx:xx:xx txqueuelen 1000 (Ethernet)
    RX packets 42356 bytes 52721928 (50.2 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 25594 bytes 3201181 (3.0 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    wlan1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
    ether da:7b:16:xx:xx:xx txqueuelen 1000 (Ethernet)
    RX packets 0 bytes 0 (0.0 B)
    RX errors 0 dropped 6 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    ----------------------------------------------------------------------------

    iwconfig says:
    wlan1 IEEE 802.11 ESSIDff/any
    Mode:Managed Access Point: Not-Associated Tx-Power=18 dBm
    Retry short limit:7 RTS thrff Fragment thrff
    Encryption keyff
    Power Managementff

    eth0 no wireless extensions.

    wlan0 IEEE 802.11 ESSID:"EAI"
    Mode:Managed Frequency:2.462 GHz Access Point: xx:xx:xx:xx:xx:xx
    Bit Rate=72.2 Mb/s Tx-Power=31 dBm
    Retry short limit:7 RTS thrff Fragment thrff
    Encryption keyff
    Power Managementn
    Link Quality=57/70 Signal level=-53 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    lo no wireless extensions.

    -------------------------------------------------------
    Airmon-ng:

    airmon-ng start wlan1

    Found 3 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 run 'airmon-ng check kill'

    PID Name
    4122 NetworkManager
    4131 wpa_supplicant
    4760 dhclient

    PHY Interface Driver Chipset

    phy0 wlan0 brcmfmac Broadcom 43430
    phy6 wlan1 8812au Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter
    cat: /sys/class/ieee80211/phy6/device/net/wlan1mon/type: No such file or directory

    Newly created monitor mode interface wlan1mon is *NOT* in monitor mode.
    Removing non-monitor wlan1mon interface...

    WARNING: unable to start monitor mode, please run "airmon-ng check kill"

    -----------------------------------------------------------------------
    i have tried with check kill without success.
    ----------------------------------------------------------------------
    But if i type:

    ip link set wlan1 down
    iwconfig wlan1 mode monitor
    ip link set wlan1 up
    ---------------------------------------------------------------------
    i get following
    (mac adress marked with x)
    ifconfig:
    eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
    ether b8:27:eb:xx:xx:xx 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 1 (Local Loopback)
    RX packets 57042 bytes 8695636 (8.2 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 57042 bytes 8695636 (8.2 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
    inet 192.168.x.xx netmask 255.255.255.0 broadcast 192.168.1.255
    inet6 fe80::46cd:xxxx:xxx:xxxx prefixlen 64 scopeid 0x20<link>
    ether b8:27:eb:xx:xx:xx txqueuelen 1000 (Ethernet)
    RX packets 42414 bytes 52734029 (50.2 MiB)
    RX errors 0 dropped 0 overruns 0 frame 0
    TX packets 25657 bytes 3208669 (3.0 MiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

    wlan1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
    unspec AE-2B-5D-88-4D-8D-30-30-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
    RX packets 366 bytes 0 (0.0 B)
    RX errors 0 dropped 418 overruns 0 frame 0
    TX packets 0 bytes 0 (0.0 B)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
    ------------------------------------------------------
    iwconfig;

    iwconfig
    wlan1 IEEE 802.11 Mode:Monitor Frequency:2.412 GHz Tx-Power=18 dBm
    Retry short limit:7 RTS thrff Fragment thrff
    Power Managementff

    eth0 no wireless extensions.

    wlan0 IEEE 802.11 ESSID:"xxxxxxxxxx"
    Mode:Managed Frequency:2.462 GHz Access Point: 1C:B7:xx:xx:xxxx
    Bit Rate=65 Mb/s Tx-Power=31 dBm
    Retry short limit:7 RTS thrff Fragment thrff
    Encryption keyff
    Power Managementn
    Link Quality=53/70 Signal level=-57 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:0 Invalid misc:0 Missed beacon:0

    lo no wireless extensions.
    -----------------------------------------------------------------------
    Airmon-ng

    airmon-ng start wlan1

    Found 3 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 run 'airmon-ng check kill'

    PID Name
    4122 NetworkManager
    4131 wpa_supplicant
    4760 dhclient

    PHY Interface Driver Chipset

    phy0 wlan0 brcmfmac Broadcom 43430
    phy6 wlan1 8812au Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter

    (mac80211 monitor mode already enabled for [phy6]wlan1 on [phy6]10)
    ----------------------------------------------------------------------------
    airodump-ng -i wlan1 seems to be working.

    So far good but the issues occur running kismet.

    In managed mode. (mac adress marked xxxx)
    ----------------------------------------------
    kismet -c wlan1
    it detects access points but also gives

    INFO: Detected new 802.11 Wi-Fi access point XXXXXXXXX packet 78
    debug - IE tags corrupt
    INFO: Detected new 802.11 Wi-Fi access point XXXXXXXXX packet 79
    debug - IE tags corrupt
    debug - IE tags corrupt
    debug - IE tags corrupt
    debug - IE tags corrupt
    and finds one and another AP and gives same debug.
    ----------------------------------------------------------------------
    kismet in monitormode (if needed) gives:
    ERROR: Unable to find driver for 'wlan1mon'. Make sure that any plugins
    required are loaded.
    ERROR: Data source 'wlan1mon' failed to launch: Unable to find driver for
    'wlan1mon'. Make sure that any plugins required are loaded.
    ---------------------------------------------------------------------------------

    airmong-ng refers to cat: /sys/class/ieee80211/phy6/device/net/wlan1mon/type: No such file or directory

    and i only have wlan1 directory.
    but starting up with iwconfig works.

    But why cant i get the kismet to work properly? driver issues or something else?

  26. #76
    Join Date
    2018-Aug
    Posts
    1
    I got the 36ACH a couple of days ago thinking it would take only two commands to get it to work.. Oh boy was I mistaken.
    The current situation: OS(VM) is able to detect, there is an interface, nothing is using the interface, I am not able to see any wi-fi networks(I can on my Windows host), monitor mode seems to be working and so does
    injection
    .

    uname -a
    Linux kali 4.15.0-kali2-amd64 #1 SMP Debian 4.15.11-1kali1 (2018-03-21) x86_64 GNU/Linux


    I installed the 4.15.0 kbuild and headers including the compiler needed for this.
    Got them here:
    http://ftp.nl.debian.org/debian/pool...17-1_amd64.deb

    http://mirror.internode.on.net/pub/kali/pool/main/l/linux/linux-headers-4.15.0-kali2-common_4.15.11-1kali1_all.deb
    http://mirror.internode.on.net/pub/kali/pool/main/l/linux/linux-headers-4.15.0-kali2-amd64_4.15.11-1kali1_amd64.deb

    I had to use the apt-get method, because the github one didn't even show me an interface.

  27. #77
    Join Date
    2013-Jul
    Posts
    41
    Quote Originally Posted by HaloHole View Post
    [COLOR=#333333]

    I had to use the apt-get method, because the github one didn't even show me an interface.
    Just obtained a AWUS036ACH

    I went ahead and downloaded the RTL8812AU drivers from https://github.com/kimocoder/rtl8812au . I nstalled using DKMS , followed readme instructions.

    After reading https://medium.com/@adam.toscher/con...c-1fb65c6ada57 I went ahead and wrote this small script to put card into monitor and raise TX power .
    Code:
    ip link set wlan1 down
    iwconfig wlan1 mode monitor
    ip link set wlan1 up 
    iwconfig wlan1 txpower 30
    iwconfig | grep wlan1
    Everything seems to be working okay so far ( Injection ) .

    Not sure if airmon-ng would be better suited to switch card into monitor mode.

    I've had issues right away with airodump-ng .

    Possibly the drivers too ? As the interface randomly drops after 5 or so minutes. Any one else experience this issue ?

    As of today what are most recent / updated RTL8812AU drivers.
    **** UPDATE
    Do not see chipset in lspci output..

    Issues with aireplay injection. It is hit and miss with airodump showing networks as well.

    I really had my hopes up with this adapter. Anyone having better luck than I ?
    *** LATEST UPDATE .
    After getting this " Beast " working . Packet injection failed 3/4 times .

    I've refunded for a AWUS036NHA.
    Last edited by hightech316; 2018-08-21 at 01:58.

  28. #78
    Join Date
    2018-May
    Posts
    4
    Quote Originally Posted by hightech316 View Post
    *** LATEST UPDATE .
    After getting this " Beast " working . Packet injection failed 3/4 times .

    I've refunded for a AWUS036NHA.
    Just be aware that the range on the AWUS036NHA is almost useless.

    Although it's flagged high-power manufacturer never released driver to support high-power operation.

    I have one and can confirm it sucks. Even with a 9dB antenna.

  29. #79
    Join Date
    2013-Jul
    Posts
    41
    Quote Originally Posted by playgear View Post
    Just be aware that the range on the AWUS036NHA is almost useless.

    Although it's flagged high-power manufacturer never released driver to support high-power operation.

    I have one and can confirm it sucks. Even with a 9dB antenna.
    I just recieved the 36NHA today. After testing , it is working better than the 36ACH.

    Haven't sent ACH back, I may just send the NHA back and hope to get the ACH working..

    I all confused . Side to Side IDK which one to pick.

    ACH better specs. NHA suppose to be better supported.

    What do you guys think?

  30. #80
    Join Date
    2013-Jul
    Posts
    41
    Quote Originally Posted by playgear View Post
    Just be aware that the range on the AWUS036NHA is almost useless.

    Although it's flagged high-power manufacturer never released driver to support high-power operation.

    I have one and can confirm it sucks. Even with a 9dB antenna.
    Sorry to hear you had a bad experience with the RTL8812AU.

    Most definitely a stubborn chip set, Although once I found right combination of drivers and modules its been working .

    Only issue at the moment , capturing handshakes. Anyone else have this issue? The handshake packet seems very delayed .

    Although I am receiving great range . Finding Five more AP's that usually do not. Not too impressed on injection tests.

    Bumping Tx-Power helped range .
    40dbm.jpg
    wlan1 is the 36ACH
    wlan0 is onboard Centrino Advanced-N 6235 .

    injection.jpg

    So I ended up keeping the 36ACH and sending back the 36NHA.
    36ACH does have driver issues, in time the bugs will be ironed out. In meantime my usb ASUS N13 does great for pentesting.

  31. #81
    Join Date
    2013-Jun
    Posts
    79
    Quote Originally Posted by hightech316 View Post
    Sorry to hear you had a bad experience with the RTL8812AU.

    Most definitely a stubborn chip set, Although once I found right combination of drivers and modules its been wrking .

    Only issue at the moment , capturing handshakes. Anyone else have this issue? The handshake packet seems very delayed .

    Although I am receiving great range . Finding Five more AP's that usually do not. Not too impressed on injection tests.

    Bumping Tx-Power helped range .
    40dbm.jpg
    wlan1 is the 36ACH
    wlan0 is onboard Centrino Advanced-N 6235 .

    injection.jpg

    So I ended up keeping the 36ACH and sending back the 36NHA.
    36ACH does have driver issues, in time the bugs will be ironed out. In meantime my usb ASUS N13 does great for pentesting.
    I have had mixed results as well, bad .cap file or what seems to look like good signal is not good enough to capture a handshake properly. Works great in windows environment lol. Works in kali as well, just a pita.

  32. #82
    Join Date
    2018-Aug
    Posts
    6
    Well I finally have my 036ACH working now. Packet injection is good, airmon-ng works! Finally time to have some fun. Big thanks to everyone who contributed.

  33. #83
    Join Date
    2018-Sep
    Posts
    1
    Soo what was the final setup that was agreed upon to get this working? (as best as possible I mean) ? a summary would be greatly appreciated

  34. #84
    Join Date
    2018-May
    Posts
    4
    Quote Originally Posted by bchuck View Post
    Well I finally have my 036ACH working now. Packet injection is good, airmon-ng works! Finally time to have some fun. Big thanks to everyone who contributed.
    Quote Originally Posted by OxycodonIV View Post
    Soo what was the final setup that was agreed upon to get this working? (as best as possible I mean) ? a summary would be greatly appreciated
    Agreed, it would be great to know the exact set of requirements to get this thing fully functional.

    Incidentally, has anyone tried with Kali 2018.3, and did it make any different out of the box?

  35. #85
    Join Date
    2018-Aug
    Posts
    6
    2018.3 is what seemed to be working for me. If you look at the bug fixes the drivers install was fixed. After installing a fresh Kali 2018.3 I just did everything listed.

    - apt-get update && upgrade commands
    - After update was completed I went ahead and installed the dkms files
    - Quick Reboot
    - Then I installed the github files.
    - Uninstalled the dkms files and reinstalled.
    - Cards blue light finally kicked on and I could see wifi. Packet injection and monitor mode worked great.

  36. #86
    Join Date
    2018-May
    Posts
    4
    Quote Originally Posted by bchuck View Post
    2018.3 is what seemed to be working for me. If you look at the bug fixes the drivers install was fixed. After installing a fresh Kali 2018.3 I just did everything listed.

    - apt-get update && upgrade commands
    - After update was completed I went ahead and installed the dkms files
    - Quick Reboot
    - Then I installed the github files.
    - Uninstalled the dkms files and reinstalled.
    - Cards blue light finally kicked on and I could see wifi. Packet injection and monitor mode worked great.
    Maybe there is something wrong with me, but I literally followed that to the letter and the card still is not working...

  37. #87
    Join Date
    2018-Aug
    Posts
    6
    After your reboot did you try and do a second upgrade, just to make sure everything was installed? Also are you running on a live usb?

  38. #88
    Join Date
    2018-May
    Posts
    4
    Quote Originally Posted by bchuck View Post
    After your reboot did you try and do a second upgrade, just to make sure everything was installed? Also are you running on a live usb?
    I realised my error after posting but wasn't able to edit it as it hadn't been approved yet - I had the USB controller in VMWare set to 'USB 2.0' so of course it didn't work correctly.

    However, I cannot get airmon-ng to work on the card; I get the following output:

    Code:
    root@kali:~# airmon-ng start wlan0
    
    
    
    PHY    Interface    Driver        Chipset
    
    
    phy0    wlan0        8812au        Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter
    cat: /sys/class/ieee80211/phy0/device/net/wlan0mon/type: No such file or directory
    
    
    Newly created monitor mode interface wlan0mon is *NOT* in monitor mode.
    Removing non-monitor wlan0mon interface...
    
    
    WARNING: unable to start monitor mode, please run "airmon-ng check kill"
    Same thing happens if I run 'airmon-ng check kill' first...

    Does it work for you?

  39. #89
    Join Date
    2018-Aug
    Posts
    6
    Sorry I am not the biggest help with Kali. Just now getting back into it. It is currently working for me. However, went ahead and did a full GUI install on a spare HDD I had in my computer. Have you tried this?

    ip link set wlan1 down
    iwconfig wlan1 mode monitor
    ip link set wlan1 up
    iwconfig wlan1 txpower 30
    iwconfig | grep wlan1

  40. #90
    Join Date
    2018-Sep
    Posts
    1
    . Using Kali linux 64bit vmware
    . Updated to latest version with
    Apt update
    apt dist-upgrade
    reboot

    Airmon-ng not working returns with msg /sys/.... file not found , permission denied
    Airdump-ng also not working gets stuck when i run command then i have to reboot.
    If enable monitoring mode on wlan0 , throught iwconfig , then i tried airdump-ng thats when it get stuck. Other then that i can see my wlan in iconfig and iwconfig and through GUI i can see networks as well
    Any fix out there?

  41. #91
    Join Date
    2018-Sep
    Posts
    1
    Quote Originally Posted by Trace View Post
    Hi dk89 ... it would appear this is quite a common problem with some hardware (including my own) ... I get terrible range from all drivers after 4.3.20.

    Check out this page on github where we've been discussing it with some driver developers and leave your hardware details as it may help towards a solution:

    https://github.com/aircrack-ng/rtl8812au/issues/77

    Also try out the new 5.2.20 drivers (didn't work for me) and let us know how you get on:

    https://github.com/kimocoder/rtl8812au-1

    Thanks for putting up the new 5.2.20 drivers link. The steps given by re4son and others worked for getting Kali to see the alfa card, but it couldn't see any traffic. After uninstalling the previous drivers and installing the new ones, it all works.

  42. #92
    Join Date
    2015-Apr
    Posts
    2
    If there is a kind soul who would post step-by-step instructions on how to get these drivers up on a clean 2018.3 Kali install, I would be very very grateful. And I am certain there are many others for whom such a guide would be helpful. I have been trying to get this adapter up for 3 weeks now. Call me a dumb noob, but statements like ""Installed the dkms files / installed the github files / Uninstalled the dkms files and reinstalled" are not helpful to me.
    Thank you very much
    RadioGirl

  43. #93
    Join Date
    2018-Sep
    Posts
    1
    Quote Originally Posted by radiogirl View Post
    If there is a kind soul who would post step-by-step instructions on how to get these drivers up on a clean 2018.3 Kali install, I would be very very grateful. And I am certain there are many others for whom such a guide would be helpful. I have been trying to get this adapter up for 3 weeks now. Call me a dumb noob, but statements like ""Installed the dkms files / installed the github files / Uninstalled the dkms files and reinstalled" are not helpful to me.
    Thank you very much
    RadioGirl

    Here's what I did to finally get it working:


    • Clean install Kali 2018.3 - If not clean, run: apt remove realtek-rtl88xxau-dkms && apt purge realtek-rtl88xxau-dkms


    • apt update && apt upgrade
    • apt autoremove && apt autoclean
    • reboot


    • apt-get dist-upgrade
    • reboot


    • git clone https://github.com/kimocoder/rtl8812au
    • cd rtl8812au
    • make && make install


    • poweroff
    • Plug in AWUS036ACH into a USB2 port - Ensure that USB 2.0(EHCI) Controller is used in machine settings.
    • Power up, after logging in confirm with iwconfig - If still not working, reset the machine via VBox.


    For some reason USB3 wouldn't work for me, VBox wouldn't connect the NIC at all, or I was getting descriptor errors in dmesg. USB2 is working perfectly fine. Packet injection working. 5ghz deauth and handshake captured.

Similar Threads

  1. New Alfa awus036ach help
    By fatfarm5 in forum TroubleShooting Archive
    Replies: 47
    Last Post: 2017-12-14, 10:47
  2. What tablet is capable of running a full Kali install?
    By nemes in forum General Archive
    Replies: 7
    Last Post: 2017-06-27, 11:06
  3. New install running slow
    By smorris in forum General Archive
    Replies: 0
    Last Post: 2017-03-07, 06:13
  4. Replies: 3
    Last Post: 2014-01-09, 14:54

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •