1 00:00:07,410 --> 00:00:11,050 - [Instructor] Let's go over airmon or airmon-ng. 2 00:00:11,050 --> 00:00:14,350 Airmon is a tool within the aircrack suite 3 00:00:14,350 --> 00:00:16,290 that can be used to enable monitor mode 4 00:00:16,290 --> 00:00:17,830 on wireless interfaces. 5 00:00:17,830 --> 00:00:20,180 You can also use it to go back 6 00:00:20,180 --> 00:00:22,743 from monitor mode to manage mode. 7 00:00:23,720 --> 00:00:26,250 When you use airmon to put a wireless adapter 8 00:00:26,250 --> 00:00:29,120 into monitor mode, it will automatically check 9 00:00:29,120 --> 00:00:32,687 for processes running on the systems that can interfere 10 00:00:32,687 --> 00:00:34,970 with the monitoring process. 11 00:00:34,970 --> 00:00:38,670 However, also you do, you can do this manually 12 00:00:38,670 --> 00:00:42,330 with the, you know, command airmon-ng check, right? 13 00:00:42,330 --> 00:00:44,660 So airmon-ng check command 14 00:00:44,660 --> 00:00:46,560 as I'm actually demonstrating here. 15 00:00:46,560 --> 00:00:49,570 Here you can see three processes that may actually 16 00:00:49,570 --> 00:00:50,780 cause some trouble: 17 00:00:50,780 --> 00:00:53,370 the network manager, the DHCP client, 18 00:00:53,370 --> 00:00:55,290 and the wpa_supplicant. 19 00:00:55,290 --> 00:00:56,410 You can kill them all 20 00:00:56,410 --> 00:00:59,833 with the airmon-NG check kill command. 21 00:01:00,910 --> 00:01:02,800 You can do a check again. 22 00:01:02,800 --> 00:01:05,860 Now you don't see any conflicting processes here. 23 00:01:05,860 --> 00:01:08,060 So let's start to put the wireless adapter 24 00:01:08,060 --> 00:01:13,060 in monitoring mode with the airmon-NG start command. 25 00:01:13,358 --> 00:01:15,840 And then you specify the wireless adapter 26 00:01:15,840 --> 00:01:17,803 which in my case is wlan0. 27 00:01:19,250 --> 00:01:20,450 Now to check the status 28 00:01:20,450 --> 00:01:24,790 you can just type airmon-ng by itself and press enter. 29 00:01:24,790 --> 00:01:29,040 Here you can see that wlan0 is in monitoring mode 30 00:01:29,040 --> 00:01:33,883 and that I'm using an adapter with a Atheros chip set. 31 00:01:35,040 --> 00:01:37,760 Now let me start the network manager again. 32 00:01:37,760 --> 00:01:39,700 And if you do an iconfig, 33 00:01:39,700 --> 00:01:44,313 you can see wlan0 mon as my monitoring interface.