Installing Aircrack-ng 1.2 rc2

[mmusket33]

Thinking to install Aircrack-ng 1.2 rc2

We began getting e-mails for help with scripts like linset and programs using airmon-ng text output so we installed the newer version and tried it. A Big Mistake!!!

Before you type apt-get install aircrack-ng pause and consider the following!!!!

We installed the newer version and because of airmon-ng problems we had to spend time ripping it out. We could only make one(1) monitor against the wifi device so the program was a step backwards and too limiting. Furthermore the newer airmon-ng text output is different from the older airmon-ng and airmon-zc which then killed many many programs that will all have to be rewritten. We doubt most scripts calling up airmon-ng will run if you install the newer version.

We suggest you avoid this version until you have no other choice.

If you already installed the program and want to revert to the older version.

Go to the main aircrack-ng downloads and download the previous version. Then go here and follow their advice. You have to rewrite one single line in a file and the reinstall went fine.

http://pharic.blogspot.com/2013/08/i...rcrack-ng.html

We may do some tests trying to replace the newer airmon-ng with the older one after installing the newer Aircrack-ng 1.2 rc2 Will advise

MTeams

[g0tmi1k]

We could only make one(1) monitor against the wifi device so the program was a step backwards and too limiting.

Can't say I've had this issue (or heard of anyone during testing having it).
I was able to make two interfaces without a single issue (on my first try).

Example:

root@kali:~# airmon-ng start wlan0
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 kill (some of) them!

   PID Name
  3541 NetworkManager
  3555 dhclient
  4016 wpa_supplicant

PHY	Interface	Driver		Chipset

phy0	wlan0		rtl8187		Realtek Semiconductor Corp. RTL8187
		(mac80211 monitor mode vif enabled for [phy0]wlan0 on [phy0]wlan0mon)
		(mac80211 station mode vif disabled for [phy0]wlan0)

phy1	wlan1		rt2800usb	Edimax Technology Co., Ltd EW-7711UTn nLite [Ralink RT2870]

root@kali:~# 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 kill (some of) them!

   PID Name
  3541 NetworkManager
  3555 dhclient
  4016 wpa_supplicant

PHY	Interface	Driver		Chipset

phy0	wlan0mon	rtl8187		Realtek Semiconductor Corp. RTL8187
phy1	wlan1		rt2800usb	Edimax Technology Co., Ltd EW-7711UTn nLite [Ralink RT2870]
		(mac80211 monitor mode vif enabled for [phy1]wlan1 on [phy1]wlan1mon)
		(mac80211 station mode vif disabled for [phy1]wlan1)


root@kali:~# airmon-ng 
PHY	Interface	Driver		Chipset

phy0	wlan0mon	rtl8187		Realtek Semiconductor Corp. RTL8187
phy1	wlan1mon	rt2800usb	Edimax Technology Co., Ltd EW-7711UTn nLite [Ralink RT2870]

root@kali:~#

...Two different cards in monitor mode (without any issues).
Notice how it has also hidden the interfaces that you shouldn't be using since monitor mode is enabled (new useful feature!).

---

Furthermore the newer airmon-ng text output is different from the older airmon-ng and airmon-zc which then killed many many programs that will all have to be rewritten. We doubt most scripts calling up airmon-ng will run if you install the newer version.

Yup - output is different (as it has a ton more useful and meaningful information than before).
Good chance any old (/discontinued?) scripts that were written, will either need to be updated (or written from scratch).
....Its not much work to fix old ones (Example: https://github.com/derv82/wifite/pull/41/files).
Think of it as a fresh start (and its about time in my eyes) - or time to do a code review (not a bad thing todo!).

This change shouldn't come as a shock.
airmong-zc itself had been in the repos since March 2012 (three years ago!) ~ https://github.com/aircrack-ng/aircr...ipts/airmon-zc.
Then airmong-zc replaced airmon-ng by default 6 months ago in the 'bleeding edge' code ~ https://github.com/aircrack-ng/aircr...5b674d87e528aa!



---

We suggest you avoid this version until you have no other choice.

If you already installed the program and want to revert to the older version.

Go to the main aircrack-ng downloads and download the previous version. Then go here and follow their advice. You have to rewrite one single line in a file and the reinstall went fine.

http://pharic.blogspot.com/2013/08/i...rcrack-ng.html

We may do some tests trying to replace the newer airmon-ng with the older one after installing the newer Aircrack-ng 1.2 rc2 Will advise

.
In short, this is completely bad advice if you wish to keep using Kali as a (long term) platform..

Even if its just altering the current airmon-ng to use the same naming conventions as before (rather than trying to 'restore' to the older version). Just a few reasons why:

• Forking/altering a package (and having the same name & version number) like this (changing the output of a program in a dramatic and then being dependent on it) - will cause a 'split'.
  
  • e.g. theres two end users - one has a 'modified' aircrack-ng - the other doesn't (how do you tell who has what version?).
  • The both try and do the same thing (either running a command or a script) It will work for one - and not the other.
  • This is unfair - as both have aircrack-ng v1.2 rc2 - yet it will only work for one of them - regardless of their OS.
• ...expanding on my last point - its then makes end users do another extra step - patching 'aircrack-ng' (which people to new to Linux will struggle to compile from source)
• Long term - keeping the program up-to-date - becomes a pain. As this patch would need to be applied manually each time (and you would have to remember to do so). Kali dev team will not be doing it for you.
• Manually installing a program, when its in a repos (and also part of a meta packages) isn't smart.
  
  • If you uninstall it the correct way, you will remove/break the meta package with it (so then you need to manually install all tools & keep an eye on it).
  • If you uninstall it/replace it the incorrect way - you will will cause long term issues when upgrading later on (you are breaking the package). More information on replacing programs: https://www.kali.org/news/bleeding-e...-repositories/
• Trying to restore to an older airmon-ng version in the current/latest version: You will lose so many new features & reintroduce so many older bugs (and properly new ones).

...If you think your getting emails now - wait 6 months .



If you really want to fight the change - contact the author & submit a bug ticket on their website. Get the 'issue' fixed up stream (Kali dev team do not see this as a issue/problem (as it will only course issues & splits for the reasons mentioned above) rather than 'fixing' anything).
Another reason why - the OSes that you can 'support' will be limited (only the ones that will apply your patch/fix).
...and then getting people to manually match/alter it themselves isn't a clever thing todo when you want to 'help' the masses.



I for one, am welcoming the change.
Aircrack-ng itself - New features. Fixed a few bugs which I was having. Better output. Its quicker too.
Regarding it 'breaking tools' - it helps to filter out/spot the tools which have been discontinued. So you only get tools which are up-to-date and are still being developed. Which in my eyes, are the tools I want to be using - as do most people using Kali (else we all would be using backtrack still! ).

[mmusket33]

Thanks for responding,

Reference making monitors. We probably did not explain it well. We were unable to make a mon0 and mon1 linked to the same device wlan0.
If you are able to do this please advise.

Our interest here was helping members recode their scripts. When we started getting e-mails for help we explored the matter.

MTeams

[g0tmi1k]

Reference making monitors. We probably did not explain it well. We were unable to make a mon0 and mon1 linked to the same device wlan0.
If you are able to do this please advise.

I believe what your wanting to-do (share the device & create multiple interfaces) is technically a bug in the old (<= v1.2 rc1) airmon-ng - you shouldn't of been doing this.
This has been patched in v1.2 rc2/airmon-zc - which is why you cannot do it any more (you shouldn't of been doing it to being with).

#check if $1 already has a mon interface on the same phy and bail if it does
if [ -d /sys/class/ieee80211/${PHYDEV}/device/net ]
then
	for i in $(ls /sys/class/ieee80211/${PHYDEV}/device/net/)
	do
		if [ "$(cat /sys/class/ieee80211/${PHYDEV}/device/net/${i}/type)" = "803" ]
		then
			setChannelMac80211 ${1}
			printf "\n\t\t(mac80211 monitor mode already enabled for [${PHYDEV}]${1} on [${PHYDEV}]${i})\n"
			exit
		fi
	done
fi

Source: https://github.com/aircrack-ng/aircr...airmon-ng#L213


If you wish for another interface for whatever reason - don't use airmon-ng (it wasn't designed/meant for this).
There are other ways in Linux to-do just this:
+ http://www.cyberciti.biz/faq/linux-c...work-card-nic/
+ http://www.question-defense.com/2012...rnet-interface
+ http://www.lazysystemadmin.com/2010/...nux-quick.html