Jump to content

JeroenV1982

Active Members
  • Posts

    27
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by JeroenV1982

  1. 13 hours ago, chrizree said:

    At about 19 minutes into the video where the deauth starts it shows another MAC address than the one that the actual AP has. You were commenting on channel hopping or channels at that point, but it's not hopping channels, it's still on channel 8. The thing is that you need to specify the BSSID of the AP as well with the parameter/option -B to only deauthenticate the specified station from the desired AP, for example:

    mdk4 wlan1mon d -c 8 -B <MAC address of the AP> -S <MAC address of the station/client>

    Then, at about 21 minutes where you run the mdk command from the Pineapple console, you are going berserk on all APs that uses channel 8, deauthenticating clients on networks where you probably don't have permission to deauthenticate client equipment.

    Good hint on the -B, I didn't know that. Unfortunately Youtube Editor has no way to make a comment on that afterwards.

    About the berserk, you are right, I thought I'd copied my original line with the -S and realized it didn't when I seen it all going bad. I will update the video once more with your suggestions in it, thanks for your support! 

  2. I used this guide to change my output power. It works perfect but after a power loss the MK7 boots at default values.

    Anyone know how to overcome this problem?

     

    Console output after power loss:

    root@mk7:/pineapple# iw dev
    phy#2
            Interface wlan2
                    ifindex 7
                    wdev 0x200000002
                    addr 0c:ef:af:ce:6e:03
                    type managed
                    txpower
    20.00 dBm
    phy#1
            Interface wlan1
                    ifindex 8
                    wdev 0x100000002
                    addr 0c:ef:af:ce:7e:08
                    type managed
                    txpower
    20.00 dBm
    phy#0
            Interface wlan0-1
                    ifindex 10
                    wdev 0x3
                    addr 02:13:37:a8:1c:fd
                    ssid Ziggo777
                    type AP
                    channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
                    txpower
    19.00 dBm (No need for change since this is my admin WiFi)
                    multicast TXQ:
                            qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes        tx-packets
                            0       0       289     0       0       0       0       102234          370
            Interface wlan0
                    ifindex 9
                    wdev 0x2
                    addr 00:13:37:a8:1c:fd
                    ssid Amadore Guest
                    type AP
                    channel 1 (2412 MHz), width: 20 MHz, center1: 2412 MHz
                    txpower
    19.00 dBm
                    multicast TXQ:
                            qsz-byt qsz-pkt flows   drops   marks   overlmt hashcol tx-bytes        tx-packets
                            0       0       0       0       0       0       0       0               0
    root@mk7:/pineapple# 

  3. My Alfa AWUS036ACS does show up under USB devices (Realtek Semiconducttor Corp) as Device 007.

    I know this is Realtek RTL8811AU but did anyone managed to make it work?

     

    root@mk7:/pineapple# lsusb
    Bus 001 Device 004: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
    Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
    Bus 001 Device 003: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless Adapter
    Bus 001 Device 007: ID 0bda:0811 Realtek Semiconductor Corp. 
    Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  4. 18 hours ago, chrizree said:

    -S is in the help text of MDK4, it's for attacking a station

    Thank you for your help. I updated my MDK4 on my MKVIII successful. I also tried mdk4 wlan1mon wlan1mon d -S 00:00:00:00:00:00 (Mac of my AP) and it works perfect.

    From a noob point of view, can you explain the difference between -B (BSSID) and -S (Station)? Aren't both the same since they both are MAC?

  5. On 4/2/2021 at 10:55 AM, chrizree said:

    -E, yes, but not -e and with -E you should use an ESSID, i.e. an AP name, not a MAC address

    Look at this thread on how to "upgrade" mdk4 on the Mk7, it may help
    https://forums.hak5.org/topic/54576-mdk4-on-mark-vii-from-terminal/

     

    There is also the -S (see picture above). Do you know the difference between -B and -S?

    I tried:

    mdk4 wlan1mon wlan1mon d -E SenS

    But it also throws away my iPhone connected to the Open Wifi of the MK7 and that SSID is "Amadore Guest" (not SenS with MAC 98:9B:CB:F0:39:0B)?

    (I can see this because my PineAP is in advanced mode (for monitor mode) and has Client Connected and Disconnected notifications enabled.

    Photo

     

  6. 8 hours ago, chrizree said:

    BSSID isn't -e, is it?! For attack mode "d" it should be -B. What version of mdk4 are you running?

    I’m running MDK4.0 v1. MDK4 —help d says -e is valid for mode “d”.

    0B3A9845-BB35-42C1-AEDA-AEF6432873A2.jpeg

  7. 8 hours ago, chrizree said:

    Enable PineAP to get a monitor mode interface. Set the attack mode (using "d" here). Specify input and output interface. The "d" attack mode shouldn't really need two interfaces to be specified, but the module won't start mdk4 unless both are set, use wlan1mon for both. Using a blacklist = just make sure it's in the Mk7 file system somewhere and that it contains relevant MAC addresses for AP(s) to "attack". Add the path to the blacklist on the line in the module GUI. Specify channels to operate on. The Command line in the module GUI "grows" as parameters are set, for example a "full" line could look like: mdk4 wlan1mon wlan1mon d -b /root/mdk4_temp/blacklist.lst -c 1

    Then hit "Start" and the "attack" should begin (the Output box at the bottom of the module page will update every 5 seconds). If running ps ax you can see that the mdk4 process has been started in the background.

    Adding multiple MACs? Not sure, just try different variants. One on each line perhaps... or comma, or semicolon... The SSID list files on the MDK4 GitHub are specified with one SSID per line at least, so perhaps a hint on how to handle MACs as well.

    Very well explained thank you!

    my Blacklist.txt only contains one Mac but the console output is very weird. Using bssid filtering (-e) the result looks better. Is this a bug?

    E958F1F6-CC7A-4F0B-B726-B573984E25A7.jpeg

    EE7E3D96-3411-4467-A581-8D5F70936F7D.png

  8. I’m also curious how to work with the webend of mdk4 on the pineapple. Any links to videos? 
     

    running MDK4 from the console works fine but the keyboard on a iPad lacks CTRL-X, arrow keys and more so sucks a bit. Does anybody know how to add multiple MAC addresses in the whitelist? Are these comma separated?

  9. FYI: I made this portal yesterday evening and this morning had 5 entries in my log and about 50 unique visitors. I guess most people came in the hotel at the beginning of the week and they never seen this portal so they disconnected or picked another SSID. My guess is that when I place my Mark7 next week Monday and run all week I have more luck.

    just to let you guys know, I delete all entires, this is just for learning purposes.

    • Like 1
  10. Hey guys, I own the MK7 and might have a dumb question; is there a way to make the open WiFi a password protected one that accepts any given password? The thing is to trick my clients, they always have to go into WiFi settings and select my open WiFi which has no keylock icon next to it. Most users won’t fall for this trick.

    • Upvote 1
  11. Hi all, I want to trick / pentest a corporate Access Point that has Microsoft OneX security. So these require you to login with your Microsoft 365 username and PW and are unique for every user. Since all members had access before, I need a way to trick their laptops to pick my WP by providing better wifi signal (which I can).

    Did anybody found a way to enable security on WP and accept any password given? In the end, the only thing matters is that the user will try to connect entering a Microsoft email and password. We don't care if the credentials are right or not and I intent to never ever give them access or something.

  12. Hi all, my name is Jeroen and I'm new.

    I have the Packet Squirrel and I want to redirect a specific website to a clone to harvest user/pwd. Did someone ever tried this and his willing to share his/her work?

    Br Jeroen

    P.S. the purpose is demonstrate the risks of an attack like this and if I can do it (with the community help), anyone can.

  13. Yes I did but thanks for pointing out.

    I also posted my issue on the Oracle forums. People say its not possible to share a USB between the host and the VM. The send me a link

     but I already created a filter. The filer is what is causing the issue. When I remove the filer my wifi adpater keeps working (blue led on), the moment I go to the top and select USB, Realink, the LED goes off again. As far as my english goes, these are the two steps (approaches) from the link right?

  14. Ok another clean install, this time full kali linux 2018.4 64-bit.

    The script worked, but my adapter still isn't. Here is the result:

    root@kali:~/Desktop# bash ./wlan.sh
    Hit:1 http://ftp2.nluug.nl/os/Linux/distr/kali kali-rolling InRelease
    Reading package lists... Done
    Reading package lists... Done
    Building dependency tree       
    Reading state information... Done
    dkms is already the newest version (2.6.1-1).
    The following packages were automatically installed and are no longer required:
      libbind9-160 libdns1102 libirs160 libisc169 libisccc160 libisccfg160
      liblwres160 libpoppler74 libprotobuf-lite10 libprotobuf10 libradare2-2.9
      libunbound2 python-anyjson python-backports.ssl-match-hostname
      python-couchdbkit python-http-parser python-jwt python-restkit
      python-socketpool
    Use 'apt autoremove' to remove them.
    0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
    rm: cannot remove 'rtl8812AU-4.3.22/': No such file or directory
    Cloning into 'rtl8812au'...
    remote: Enumerating objects: 829, done.
    remote: Total 829 (delta 0), reused 0 (delta 0), pack-reused 829
    Receiving objects: 100% (829/829), 2.76 MiB | 1.05 MiB/s, done.
    Resolving deltas: 100% (412/412), done.
    make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.18.0-kali2-amd64/build M=/usr/src/rtl8812au  modules
    make[1]: Entering directory '/usr/src/linux-headers-4.18.0-kali2-amd64'
      CC [M]  /usr/src/rtl8812au/core/rtw_cmd.o
      CC [M]  /usr/src/rtl8812au/core/rtw_security.o
      CC [M]  /usr/src/rtl8812au/core/rtw_debug.o
      CC [M]  /usr/src/rtl8812au/core/rtw_io.o
      CC [M]  /usr/src/rtl8812au/core/rtw_ioctl_query.o
      CC [M]  /usr/src/rtl8812au/core/rtw_ioctl_set.o
      CC [M]  /usr/src/rtl8812au/core/rtw_ieee80211.o
      CC [M]  /usr/src/rtl8812au/core/rtw_mlme.o
      CC [M]  /usr/src/rtl8812au/core/rtw_mlme_ext.o
      CC [M]  /usr/src/rtl8812au/core/rtw_mi.o
      CC [M]  /usr/src/rtl8812au/core/rtw_wlan_util.o
      CC [M]  /usr/src/rtl8812au/core/rtw_vht.o
      CC [M]  /usr/src/rtl8812au/core/rtw_pwrctrl.o
      CC [M]  /usr/src/rtl8812au/core/rtw_rf.o
      CC [M]  /usr/src/rtl8812au/core/rtw_recv.o
      CC [M]  /usr/src/rtl8812au/core/rtw_sta_mgt.o
      CC [M]  /usr/src/rtl8812au/core/rtw_ap.o
      CC [M]  /usr/src/rtl8812au/core/rtw_xmit.o
      CC [M]  /usr/src/rtl8812au/core/rtw_p2p.o
      CC [M]  /usr/src/rtl8812au/core/rtw_rson.o
      CC [M]  /usr/src/rtl8812au/core/rtw_tdls.o
      CC [M]  /usr/src/rtl8812au/core/rtw_br_ext.o
      CC [M]  /usr/src/rtl8812au/core/rtw_iol.o
      CC [M]  /usr/src/rtl8812au/core/rtw_sreset.o
      CC [M]  /usr/src/rtl8812au/core/rtw_btcoex_wifionly.o
      CC [M]  /usr/src/rtl8812au/core/rtw_btcoex.o
      CC [M]  /usr/src/rtl8812au/core/rtw_beamforming.o
      CC [M]  /usr/src/rtl8812au/core/rtw_odm.o
      CC [M]  /usr/src/rtl8812au/core/efuse/rtw_efuse.o
      CC [M]  /usr/src/rtl8812au/os_dep/osdep_service.o
      CC [M]  /usr/src/rtl8812au/os_dep/linux/os_intfs.o
      CC [M]  /usr/src/rtl8812au/os_dep/linux/usb_intf.o
      CC [M]  /usr/src/rtl8812au/os_dep/linux/usb_ops_linux.o
      CC [M]  /usr/src/rtl8812au/os_dep/linux/ioctl_linux.o
      CC [M]  /usr/src/rtl8812au/os_dep/linux/xmit_linux.o
      CC [M]  /usr/src/rtl8812au/os_dep/linux/mlme_linux.o
      CC [M]  /usr/src/rtl8812au/os_dep/linux/recv_linux.o
      CC [M]  /usr/src/rtl8812au/os_dep/linux/ioctl_cfg80211.o
      CC [M]  /usr/src/rtl8812au/os_dep/linux/rtw_cfgvendor.o
      CC [M]  /usr/src/rtl8812au/os_dep/linux/wifi_regd.o
      CC [M]  /usr/src/rtl8812au/os_dep/linux/rtw_android.o
      CC [M]  /usr/src/rtl8812au/os_dep/linux/rtw_proc.o
      CC [M]  /usr/src/rtl8812au/os_dep/linux/ioctl_mp.o
      CC [M]  /usr/src/rtl8812au/hal/hal_intf.o
      CC [M]  /usr/src/rtl8812au/hal/hal_com.o
      CC [M]  /usr/src/rtl8812au/hal/hal_com_phycfg.o
      CC [M]  /usr/src/rtl8812au/hal/hal_phy.o
      CC [M]  /usr/src/rtl8812au/hal/hal_dm.o
      CC [M]  /usr/src/rtl8812au/hal/hal_dm_acs.o
      CC [M]  /usr/src/rtl8812au/hal/hal_btcoex_wifionly.o
      CC [M]  /usr/src/rtl8812au/hal/hal_btcoex.o
      CC [M]  /usr/src/rtl8812au/hal/hal_mp.o
      CC [M]  /usr/src/rtl8812au/hal/hal_mcc.o
      CC [M]  /usr/src/rtl8812au/hal/hal_hci/hal_usb.o
      CC [M]  /usr/src/rtl8812au/hal/led/hal_usb_led.o
      CC [M]  /usr/src/rtl8812au/hal/HalPwrSeqCmd.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/Hal8812PwrSeq.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/Hal8821APwrSeq.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/rtl8812a_xmit.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/rtl8812a_sreset.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/rtl8812a_hal_init.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/rtl8812a_phycfg.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/rtl8812a_rf6052.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/rtl8812a_dm.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/rtl8812a_rxdesc.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/rtl8812a_cmd.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/usb/usb_halinit.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/usb/rtl8812au_led.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/usb/rtl8812au_xmit.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/usb/rtl8812au_recv.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/usb/usb_ops_linux.o
      CC [M]  /usr/src/rtl8812au/hal/efuse/rtl8812a/HalEfuseMask8812A_USB.o
      CC [M]  /usr/src/rtl8812au/hal/rtl8812a/hal8812a_fw.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_debug.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_antdiv.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_soml.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_smt_ant.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_antdect.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_interface.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_phystatus.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_hwconfig.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_dig.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_pathdiv.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_rainfo.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_dynamictxpower.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_adaptivity.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_cfotracking.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_noisemonitor.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_acs.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_beamforming.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_dfs.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/txbf/halcomtxbf.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/txbf/haltxbfinterface.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/txbf/phydm_hal_txbf_api.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_adc_sampling.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_ccx.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_psd.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_primary_cca.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_cck_pd.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_rssi_monitor.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_auto_dbg.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_math_lib.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_api.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/phydm_pow_train.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/halrf/halrf.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/halrf/halphyrf_ce.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/halrf/halrf_powertracking_ce.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/halrf/halrf_powertracking.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/halrf/halrf_kfree.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_mac.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_bb.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/rtl8812a/halhwimg8812a_rf.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/halrf/rtl8812a/halrf_8812a_ce.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/rtl8812a/phydm_regconfig8812a.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/rtl8812a/phydm_rtl8812a.o
      CC [M]  /usr/src/rtl8812au/hal/phydm/txbf/haltxbfjaguar.o
      CC [M]  /usr/src/rtl8812au/hal/btc/halbtc8723bwifionly.o
      CC [M]  /usr/src/rtl8812au/hal/btc/halbtc8822bwifionly.o
      CC [M]  /usr/src/rtl8812au/hal/btc/halbtc8821cwifionly.o
      CC [M]  /usr/src/rtl8812au/platform/platform_ops.o
      CC [M]  /usr/src/rtl8812au/core/rtw_mp.o
      LD [M]  /usr/src/rtl8812au/8812au.o
      Building modules, stage 2.
      MODPOST 1 modules
      CC      /usr/src/rtl8812au/8812au.mod.o
      LD [M]  /usr/src/rtl8812au/8812au.ko
    make[1]: Leaving directory '/usr/src/linux-headers-4.18.0-kali2-amd64'
    realtek-rtl88xxau, 5.2.20.2~20180812, 4.18.0-kali2-amd64, x86_64: installed
    rtl8812au, 5.2.20, 4.18.0-kali2-amd64, x86_64: installed
    Error! DKMS tree already contains: rtl8812au-5.2.20
    You cannot add the same module/version combo more than once.
    Module rtl8812au/5.2.20 already built for kernel 4.18.0-kali2-amd64/4
    Module rtl8812au/5.2.20 already installed on kernel 4.18.0-kali2-amd64/x86_64
    Module                  Size  Used by
    8812au               1622016  0
    cfg80211              778240  1 8812au
    rfkill                 28672  2 cfg80211
    fuse                  122880  5
    intel_powerclamp       16384  0
    intel_rapl_perf        16384  0
    binfmt_misc            20480  1
    joydev                 24576  0
    snd_intel8x0           45056  4
    vboxvideo              45056  3
    snd_ac97_codec        143360  1 snd_intel8x0
    ac97_bus               16384  1 snd_ac97_codec
    evdev                  28672  17
    snd_pcm               118784  2 snd_intel8x0,snd_ac97_codec
    snd_timer              36864  1 snd_pcm
    ttm                   131072  1 vboxvideo
    drm_kms_helper        196608  1 vboxvideo
    pcspkr                 16384  0
    serio_raw              16384  0
    snd                    94208  12 snd_intel8x0,snd_timer,snd_ac97_codec,snd_pcm
    soundcore              16384  1 snd
    vboxguest              45056  0
    drm                   471040  6 drm_kms_helper,vboxvideo,ttm
    sg                     36864  0
    ac                     16384  0
    video                  45056  0
    button                 16384  0
    ip_tables              28672  0
    x_tables               45056  1 ip_tables
    autofs4                49152  2
    ext4                  741376  1
    crc16                  16384  1 ext4
    mbcache                16384  1 ext4
    jbd2                  118784  1 ext4
    crc32c_generic         16384  0
    fscrypto               32768  1 ext4
    ecb                    16384  0
    hid_generic            16384  0
    usbhid                 57344  0
    hid                   135168  2 usbhid,hid_generic
    sd_mod                 53248  3
    sr_mod                 28672  0
    cdrom                  69632  1 sr_mod
    ata_generic            16384  0
    crct10dif_pclmul       16384  0
    crc32_pclmul           16384  0
    crc32c_intel           24576  2
    ghash_clmulni_intel    16384  0
    pcbc                   16384  0
    aesni_intel           200704  0
    ata_piix               36864  2
    xhci_pci               16384  0
    aes_x86_64             20480  1 aesni_intel
    crypto_simd            16384  1 aesni_intel
    cryptd                 28672  3 crypto_simd,ghash_clmulni_intel,aesni_intel
    glue_helper            16384  1 aesni_intel
    xhci_hcd              270336  1 xhci_pci
    psmouse               172032  0
    usbcore               290816  4 xhci_hcd,usbhid,8812au,xhci_pci
    usb_common             16384  1 usbcore
    i2c_piix4              24576  0
    e1000                 155648  0
    libata                278528  2 ata_piix,ata_generic
    scsi_mod              253952  4 sd_mod,libata,sg,sr_mod
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
        link/ether 08:00:27:1b:24:6e brd ff:ff:ff:ff:ff:ff
    root@kali:~/Desktop# 
    

    If I go to the top bar of my Vitrual Machine, I see my Devices, USB, Realtek 802.11n NIC but it hasnt got a blue check mark which it should have. Id I click it I get;

    "Het is niet gelukt USB-apparaat Realtek 802.11n NIC te koppelen aan virtuale machine Kali Linux" (which says "failed to connect Realtek bla bla bla).

    In Windows10 Pro 64 the adapter works fine, the moment I start my VM the adapters Blue LED turns off and the device shows no longer hotspots in Windows.

    Please help guys, I`m desperate and Alfa stopped supporting.

     

  15. Ok I dis a clean install, followed this video and now my AWUS036ACH is working (blue led on).

    Unfortunately my Airgeddon isnt working so I opened an issue at the Github repo for this.

    I do have another strange issue when I do:

    root@kali:~# airmon-ng
    
    PHY	Interface	Driver		Chipset
    
    phy0	wlan0		8812au		Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac WLAN Adapter
    
    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
    
    		(mac80211 monitor mode already enabled for [phy0]wlan0 on [phy0]10)
    root@kali:~# 

    See, my wlan0 wont rename to wlan0mon which it did with my old AWUS036H. i think this is also causing Airgeddon not to work since it relies on wlan0mon etc. Any hints?

×
×
  • Create New...