Aircrack-ng

Please login or register.

Login with username, password and session length
Pages: [1] 2 3 ... 10
 1 
 on: February 20, 2019, 09:29:09 AM 
Started by qt1h00 - Last post by misterx
You don't need to specify the PID when killing with 'airmon-ng check kill'. It gets them then kill them all.

 2 
 on: February 19, 2019, 10:14:46 PM 
Started by qt1h00 - Last post by Nickelz34
make sure the port you have it plugged into is a usb 3.0 port. If you look at the port with nothing plugged into it they are usually blue colored usb ports. if i recall correctly that adapter is power hungry and some users tried to use it on a usb 2.0 port but needed to use a powered usb hub .

if that is not the case for you then make sure you run

Code: [Select]
airmon-ng check
You may get something similar to this

Code: [Select]
Found 3 processes that could cause trouble.
Kill them using 'airmon-ng check kill' before putting
the card in monitor mode, they will interfere by changing channels
and sometimes putting the interface back in managed mode

  PID Name
  670 NetworkManager
  744 wpa_supplicant
 2404 dhclient

Then run

Code: [Select]
airmon-ng check kill 670
Code: [Select]
airmon-ng check kill 744
Code: [Select]
airmon-ng check kill 2404
That should make sure nothing is interfering from those processes

Then you should be able to put that card into monitor using

Code: [Select]
ifconfig wlan1 down
iwconfig wlan1 mode monitor
ifconfig wlan1 up


Now try and see if traffic shown is better

 3 
 on: February 19, 2019, 09:33:49 PM 
Started by Nickelz34 - Last post by Nickelz34
Ok so i understand this driver is a frankenstein ( correct me if im wrong ) . If I read correctly, there is parts of other drivers that were taken and worked together to form what we have now over time, in order to get monitor mode and packet injection etc?

So like some of you have probably seen, searching here and on the web, it seems that there is definitely no shortage of users with issues relating to this driver as well . Some are legitimate issues and others are vast amounts of user errors during driver installs etc.


I originally ordered the bigger brother that has 4 antennas : https://www.amazon.com/Alfa-AC1900-WiFi-Adapter-Long-Range/dp/B01MZD7Z76

BUT LOL, of course (story of my life)..... Instead of getting that adapter the seller sent me this:

ALPHA AWUS036ACH wifi adapter : https://www.amazon.com/Alfa-Long-Range-Dual-Band-Wireless-External/dp/B00VEEBOPG

Now this sucker took over a week to get to me from canada, so i decided to keep it instead of waiting forever to get the other one. I started to look over the info to install it on kali and believe i originally used this repo ( https://github.com/kimocoder/rtl8812au ) . I thought the card was working fine and think i ran into trouble when i updated my kali linux distro (maybe something changed?).

So i searched and tried to find the driver again but i think i installed a differant repo (fork) of the rtl8812au . After i ran into more problems and more searching and different driver installs . I am now scratching my head wondering did these problems happen on the original driver repo i used ( https://github.com/kimocoder/rtl8812au) ?

Maybe because i had not used certain functions, i just didnt notice something that wasnt right ?


So my questions are:

What is the recommended install method for this driver?

Which driver should we be using ?

What is the current working functions and what does not work ?

What is the best way to totally remove the past remnants of installs for this driver ? I tried dkms installs and also manually compiled the driver different times . After removing everything i can find if i run
Code: [Select]
modprobe -c i can still find several lines that say 8812au or 88xxau . they dont appear to actually be loaded or in use .


--------------------
Things I ran into
--------------------

- Ran into problems where i would try to host a fake access point but also set aireplay-ng to deauth in a different terminal

- Had issues when airodump-ng was ran it would take forever to populate wireless networks or signals would be horrible or lots of clients would not be associated

- Tried to use fluxion instead since it was automated but if i was trying to deauth/jam clients on same adapter that i also chose to be the fake access point it would just sit there and never start the access point. If i chose my laptops internal card for jamming and set the awus036ach for the access point it seemed to work. The access point showed up on my phone and if i clicked connect i did get the option to goto fake login page (did not try to enter password) .

- Before fluxion i also tried airgeddon which i thought worked with the original driver using the evil twin access point, but im not sure bc i loaded it other day and noticed in the yellow text terminal on top left it said AP-Disabled or Not enabled i believe . So i may have thought it was working at first and overlooked that area .




 4 
 on: February 19, 2019, 08:24:16 PM 
Started by Nickelz34 - Last post by Nickelz34
Well i guess my post got approved to be here lol so maybe we should sticky the announcements my post just bumped over or make announcements their own child forum of rtl8812au?

 5 
 on: February 19, 2019, 06:23:08 PM 
Started by Nickelz34 - Last post by Nickelz34
Is this subforum just for announcements regarding this driver / chipset ?

 6 
 on: February 17, 2019, 03:15:02 PM 
Started by tqk_ac - Last post by tqk_ac
Quote
But as i have gone through the other options in the GUI it seems you also have hardcoded paths for the other available selections. This is my terminal output if i select  any of the options available to me in the gui.


Code: [Select]
root@Chromecast:/opt/aircrackgui/aircrack-ng-gui# python3 aircrack-ng-gui.py
aircrack-ng-gui.py:17: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  self.add(Gtk.Label(data))

This is a label related error, it shouldn't have affected functionality, it's fixed and shouldn't show up in the most recent push to the repo.

Quote
The interface does indeed load upon start but clicking (airmon-ng) and then trying to click on any of the buttons to (start NetworkManager.service) or (stop NetworkManager.service) yields this in terminal:

Code: [Select]
/bin/sh: 1: gksudo: not found

I'm not sure why this is happening, but I couldn't reproduce it. I guess it has to do with the gksudo command that I put for early stage debugging. Replaced it with sudo, try to see if it will work.

Thanks a lot for the input, will update the instructions as well.


EDIT: I have added an installation method, haven't tried it on other machines yet, planning to do by the next weekend, so it could be buggy, feedback on it would help!

 7 
 on: February 17, 2019, 02:44:52 PM 
Started by tqk_ac - Last post by Nickelz34
Ok finally got to retry with the GUI on the recloned update

no more error when first loading and now the GUI shows perfectly and allows me to see a selection of wifi interfaces (wlan0-internal laptop card) & (wlan1-external awus036ach alpha card)

But as i have gone through the other options in the GUI it seems you also have hardcoded paths for the other available selections. This is my terminal output if i select  any of the options available to me in the gui.


Code: [Select]
root@Chromecast:/opt/aircrackgui/aircrack-ng-gui# python3 aircrack-ng-gui.py
aircrack-ng-gui.py:17: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "label" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  self.add(Gtk.Label(data))

The interface does indeed load upon start but clicking (airmon-ng) and then trying to click on any of the buttons to (start NetworkManager.service) or (stop NetworkManager.service) yields this in terminal:

Code: [Select]
/bin/sh: 1: gksudo: not found

the same terminal output is given for any of the airmon-ng buttons clicked

I am thinking this is once again linked to having hardcoded paths linked to these buttons options ( but than again i know nothing about python and am a mere n00b to most of this lol)


on a side note


The additional install instructions are a big help and im sure it will further help others who want to try this out as well . Although I do think more specific instructions could be given, such as:

    (choose/create install directory for repo)
    (cd /dir.choosen.or.created)
    clone the repo
    (git clone https://github.com/tqk-gh/aircrack-ng-gui.git)
    (cd aircrack-ng-gui-master)
    install dependencies by pip install -r requirements.txt
    make sure aircrack-ng is installed
    (cd aircrack-ng-gui)
    run aircrack-ng-gui by sudo python3 aircrack-ng-gui.py     | or if root / Kali Users |     python3 aircrack-ng-gui.py



These are just my opinions as to what i have found that may make things harder for beginners  ^^^^^

I also have a knack for constructive criticism and left out steps for anything sometimes makes me :facepalm:

LAWLZ

all in all keep up the good work loving how this is comming along
 






 8 
 on: February 14, 2019, 09:36:32 AM 
Started by pedropt - Last post by misterx
Solved: https://forums.kali.org/showthread.php?43422-Looking-for-injection-drivers-for-old-rtl8187L-amp-RA2870-working-for-kernel-4-19

 9 
 on: February 14, 2019, 12:08:52 AM 
Started by tqk_ac - Last post by tqk_ac
Ok I will try to reclone, will get some time before the weekend I hope. I will get back to you .

Oh and you should include needed prerequisites and some short install instructions. This GUI looks awesome in pix but I was kinda guessing by looking at the code as to what I would need to install for this to work as I was missing some things.

If it helps I'm on the latest Kali build all up to date as well :)

Again, thanks for the feedback. I have updated the repo with a better dependencies management and usage instructions. I'm planning to also tarball it into a package that can be installed. Currently busy so the progress is quite slow. So try it whenever you have time. More feedback is much appreciated.

 10 
 on: February 13, 2019, 06:14:00 PM 
Started by Drahcore - Last post by misterx
You probably meant airmon-ng start wlan0 and when running airodump-ng wlan0mon.

Try the current dedup-function branch in our GitHub, it fixes the issue (it will be merged to master fairly soon).

Pages: [1] 2 3 ... 10