Kali 2.0/Wireless Debugging - Revision history

Admin at 02:02, 18 August 2015

2015-08-18T02:02:44Z

← Older revision		Revision as of 02:02, 18 August 2015
Line 17:		Line 17:
	</pre>		</pre>

			In case of problems with rfkill: [[Rfkill]]

	[[Category:Security]]		[[Category:Security]]
	[[Category:Wireless]]		[[Category:Wireless]]
	[[Category:Kali]]		[[Category:Kali]]

Admin at 03:11, 16 August 2015

2015-08-16T03:11:10Z

← Older revision		Revision as of 03:11, 16 August 2015
Line 16:		Line 16:
	$ airodump-ng wlan0		$ airodump-ng wlan0
	</pre>		</pre>



			[[Category:Security]]
			[[Category:Wireless]]
			[[Category:Kali]]

Admin: Created page with "Previously, with Kali 1.0, I could put my USB wireless chips into monitor mode and start a pcap dump by running the following sequence of commands:

 $ airmon-ng $ airmon..."

2015-08-16T03:10:29Z

Created page with "Previously, with Kali 1.0, I could put my USB wireless chips into monitor mode and start a pcap dump by running the following sequence of commands: <pre> $ airmon-ng $ airmon..."

New page

Previously, with Kali 1.0, I could put my USB wireless chips into monitor mode and start a pcap dump by running the following sequence of commands:

<pre>
$ airmon-ng
$ airmon-ng start wlan0
$ airodump-ng wlan0
</pre>

However, after changing to Kali 2.0, I had to change the way I called the commands. I had to put the chip into monitor mode with the following commands (see https://taufanlubis.wordpress.com/2010/05/14/how-to-fix-ioctlsiocsiwmode-failed-device-or-resource-busy-problem/):

<pre>
$ iwconfig
$ ifconfig wlan0 down
$ iwconfig wlan0 mode monitor
$ ifconfig wlan0 up
$ airodump-ng wlan0
</pre>