Results 1 to 8 of 8

Thread: TPLink Archer 29-UH EU

  1. #1
    Join Date
    2019-Jul
    Posts
    5

    TPLink Archer 29-UH EU

    Hey Guys / Girls!

    I've recently moved back to Kali after using Parrot Sec for a few months and have come across a very strange issue.
    When I was using Kali before, I never had any issues with my TPLink Archer USB (this also worked fine on Parrot).

    But since coming back to Kali (after around 8 months away) my Archer will no longer allow monitor mode.

    Kali Version: 4.19.0-kali5-amd64

    USB Adapter: Archer T9UH AC1900 (EU/1.0)

    I've tried everything from reinstalling drivers (from TPLink's website using the documentation that they provide).
    I've also attempted to install from here (https://github.com/aircrack-ng/rtl8812au)

    When attempting to switch to monitor mode by running the following, the output of 'iwconfig' does not change
    Code:
    ifconfig wlan1 down & iwconfig wlan1 mode monitor
    Code:
    root@powerKali:~# iwconfig
    eth0      no wireless extensions.
    
    wlan1     unassociated  Nickname:"<WIFI@REALTEK>"
              Mode:Managed  Frequency=2.412 GHz  Access Point: Not-Associated   
              Sensitivity:0/0  
              Retry:off   RTS thr:off   Fragment thr:off
              Encryption key:off
              Power Management:off
              Link Quality=0/100  Signal level=0 dBm  Noise level=0 dBm
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:0   Missed beacon:0
    
    wlan0     IEEE 802.11  ESSID:off/any  
              Mode:Managed  Access Point: Not-Associated   Tx-Power=20 dBm   
              Retry short limit:7   RTS thr:off   Fragment thr:off
              Encryption key:off
              Power Management:on
    I'm pretty familiar with Kali now and this just seems to confuse me.

    EDIT: 'airmon-ng start wlan1' results in the below

    Code:
    root@powerKali:~# airmon-ng start wlan1
    
    
    PHY    Interface    Driver        Chipset
    
    phy0    wlan0        iwlwifi        Intel Corporation Wireless-AC 9560 [Jefferson Peak] (rev 10)
    phy3    wlan1        rtl8814au    TP-Link 802.11ac NIC
    
    
    ERROR adding monitor mode interface: command failed: Operation not supported (-95)
    Any help would be great!

  2. #2
    Join Date
    2016-Dec
    Posts
    647
    The drivers for rtl8812au should be done this way: apt install realtek-rtl88xxau-dkms

    Remove the drivers you've installed first (or reinstall Kali), then run this command.

  3. #3
    Join Date
    2019-Jul
    Posts
    5
    Now this is even stranger. As suggested, I removed the driver and ran 'apt install realtek-rtl88xxau-dkms' (result below)

    Code:
    root@powerKali~> apt install realtek-rtl88xxau-dkms
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    realtek-rtl88xxau-dkms is already the newest version (5.2.20.2~20190210-0kali1).
    The following packages were automatically installed and are no longer required:
      kali-desktop-common libclass-factory-util-perl libigdgmm5 libtexlua52 python-dicttoxml python-jsonrpclib python-mockito python-pypdf2 python-slowaes python-unicodecsv python-whoosh suckless-tools
    Use 'apt autoremove' to remove them.
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    IWCONFIG Result
    Code:
    root@powerKali~> iwconfig
    eth0      no wireless extensions.
    
    wlan0     IEEE 802.11  ESSID:"VM0760578"  
              Mode:Managed  Frequency:5.22 GHz  Access Point: 48:D3:43:40:B3:77   
              Bit Rate=433.3 Mb/s   Tx-Power=20 dBm   
              Retry short limit:7   RTS thr:off   Fragment thr:off
              Encryption key:off
              Power Management:on
              Link Quality=41/70  Signal level=-69 dBm  
              Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
              Tx excessive retries:0  Invalid misc:7   Missed beacon:0
    
    lo        no wireless extensions.

    NMCLI D Result
    Code:
    root@powerKali~> nmcli
    eth0: connected to Wired connection 1
            "Realtek RTL8111/8168/8411"
            ethernet (r8169), 94:C6:91:56:3A:44, hw, mtu 1500
            ip4 default
            inet4 192.168.0.75/24
            route4 192.168.0.0/24
            route4 0.0.0.0/0
            inet6 fe80::96c6:91ff:fe56:3a44/64
            route6 fe80::/64
            route6 ff00::/8
    
    wlan0: connected to VM0760578
            "Intel Wireless-AC 9560"
            wifi (iwlwifi), A0:A4:C5:6C:FB:EC, hw, mtu 1500
            inet4 192.168.0.55/24
            route4 0.0.0.0/0
            route4 192.168.0.0/24
            inet6 fe80::113d:e2f2:e091:19de/64
            route6 fe80::/64
            route6 ff00::/8
    
    p2p-dev-wlan0: disconnected
            "p2p-dev-wlan0"
            wifi-p2p, hw
    
    lo: unmanaged
            "lo"
            loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
    
    DNS configuration:
            servers: 1.1.1.1 1.0.0.1
            interface: eth0
    
            servers: 194.168.4.100 194.168.8.100
            interface: wlan0

    LSUSB Result
    Code:
    root@powerKali~> lsusb
    Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
    Bus 001 Device 004: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 (SD/SDHC/SDXC) Card Reader
    Bus 001 Device 003: ID 1532:005c Razer USA, Ltd Razer DeathAdder Elite
    Bus 001 Device 006: ID 8087:0aaa Intel Corp. 
    Bus 001 Device 005: ID 2357:0106 TP-Link 802.11ac NIC
    Bus 001 Device 002: ID 1532:021e Razer USA, Ltd Razer Ornata Chroma
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
    root@powerKali~>

  4. #4
    Join Date
    2016-Dec
    Posts
    647
    as I've been saying in other posts, lsusb (and lspci) information is just a mapping between the vendor id and device id to some text. In this case, you'll find a match for "2357:0106" (vendor/device ID) to "TP-Link 802.11ac NIC"

    There are commands to update those mapping files (but I believe it's also taken care of by packages): update-usbids and update-pciids

  5. #5
    Join Date
    2019-Jul
    Posts
    1
    Try to follow this video how to install rtl8812au driver https://www.***********************6Vs0GH9oxSs
    Last edited by xhack88; 3 Weeks Ago at 18:20.

  6. #6
    Join Date
    2019-Jul
    Posts
    5
    So, after some further research I think I may have found the root of the issue.

    See result of:
    Code:
    apt-get install realtek-rtl88xxau-dkms
    Result:
    Code:
    The following NEW packages will be installed:
      realtek-rtl88xxau-dkms
    0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
    Need to get 1,787 kB of archives.
    After this operation, 17.7 MB of additional disk space will be used.
    Get:1 http://ftp.hands.com/kali kali-rolling/contrib amd64 realtek-rtl88xxau-dkms all 5.2.20.2~20190210-0kali1 [1,787 kB]
    Fetched 1,787 kB in 1s (2,120 kB/s)              
    Selecting previously unselected package realtek-rtl88xxau-dkms.
    (Reading database ... 588705 files and directories currently installed.)
    Preparing to unpack .../realtek-rtl88xxau-dkms_5.2.20.2~20190210-0kali1_all.deb ...
    Unpacking realtek-rtl88xxau-dkms (5.2.20.2~20190210-0kali1) ...
    Setting up realtek-rtl88xxau-dkms (5.2.20.2~20190210-0kali1) ...
    Loading new realtek-rtl88xxau-5.2.20.2~20190210 DKMS files...
    Building for 4.19.0-kali5-amd64
    Building initial module for 4.19.0-kali5-amd64
    Done.
    
    88XXau.ko:
    Running module version sanity check.
    Error! Module version v5.2.20.2_28373.20180619 for 88XXau.ko
    is not newer than what is already found in kernel 4.19.0-kali5-amd64 (v5.2.20.2_28373.20180619).
    You may override by specifying --force.
    
    depmod...
    
    DKMS: install completed.
    
    Message from syslogd@powerKali at Jul 28 19:36:50 ...
     kernel:[72340.281520] do_IRQ: 2.33 No irq handler for vector
    Looks like a kernel issue to me, any more suggestions?

    Cheers!

  7. #7
    Join Date
    2019-Jul
    Posts
    5
    @xhack88

    If you read all of the comments, I've already done all this.

    After running
    Code:
    ./dkms-install.sh
    I get the error
    Code:
    Message from syslogd@powerKali at Jul 29 18:40:11 ...
     kernel:[ 5846.628562] do_IRQ: 1.34 No irq handler for vector
    Cheers!

  8. #8
    Join Date
    2019-Jul
    Posts
    5
    In addition to my last comment, see the result of
    Code:
    dmesg | grep -i irq
    Result

    Code:
    [    0.050123] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
    [    0.050124] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
    [    0.050125] ACPI: IRQ0 used by override.
    [    0.050126] ACPI: IRQ9 used by override.
    [    0.176325] NR_IRQS: 33024, nr_irqs: 1536, preallocated irqs: 16
    [    0.182617] DMAR-IR: Enabled IRQ remapping in x2apic mode
    [    0.343416] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 11 12 14 15) *0
    [    0.343489] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 10 11 12 14 15) *1
    [    0.343560] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 11 12 14 15) *0
    [    0.343631] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 11 12 14 15) *0
    [    0.343702] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) *0
    [    0.343773] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) *0
    [    0.343843] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 11 12 14 15) *0
    [    0.343914] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 11 12 14 15) *0
    [    0.345093] PCI: Using ACPI for IRQ routing
    [    0.389823] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0, 0, 0, 0, 0, 0
    [    1.517955] pcieport 0000:00:1c.0: AER enabled with IRQ 122
    [    1.517967] pcieport 0000:00:01.0: Signaling PME with IRQ 121
    [    1.517983] pcieport 0000:00:1c.0: Signaling PME with IRQ 122
    [    1.518984] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
    [    1.540148] serial8250: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A
    [    1.541982] rtc_cmos rtc_cmos: alarms up to one month, y3k, 114 bytes nvram, hpet irqs
    [    1.843580] r8169 0000:02:00.0 eth0: RTL8168h/8111h, 94:c6:91:56:3a:44, XID 54100880, IRQ 124
    [    1.843775] ata1: SATA max UDMA/133 abar m524288@0xa3300000 port 0xa3300100 irq 16
    [    1.843777] ata2: SATA max UDMA/133 abar m524288@0xa3300000 port 0xa3300180 irq 16
    [    1.843778] ata3: SATA max UDMA/133 abar m524288@0xa3300000 port 0xa3300200 irq 16
    [    1.843779] ata4: SATA max UDMA/133 abar m524288@0xa3300000 port 0xa3300280 irq 16
    [    1.843780] ata5: SATA max UDMA/133 abar m524288@0xa3300000 port 0xa3300300 irq 16
    [    1.843781] ata6: SATA max UDMA/133 abar m524288@0xa3300000 port 0xa3300380 irq 16
    [    4.188037] Generic PHY r8169-200:00: attached PHY driver [Generic PHY] (mii_bus:phy_addr=r8169-200:00, irq=IGNORE)
    [    7.517116] do_IRQ: 3.35 No irq handler for vector
    [   35.429776] do_IRQ: 1.34 No irq handler for vector
    [ 5846.628562] do_IRQ: 1.34 No irq handler for vector

Similar Threads

  1. Archer T4U / 8812au driver issues
    By orac12 in forum Kali Linux TroubleShooting
    Replies: 1
    Last Post: 2018-12-18, 02:03
  2. Tplink 821n use in rp3 b+
    By Betyar in forum ARM Archive
    Replies: 2
    Last Post: 2018-09-20, 06:27

Posting Permissions

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