WEBVTT

00:00:01.040 --> 00:00:04.660
In this demo, we're going to get started with Low Orbit Ion Cannon.

00:00:05.340 --> 00:00:06.470
In this introduction,

00:00:06.500 --> 00:00:09.060
we'll start with an overview of the lab environment that

00:00:09.060 --> 00:00:12.600
we're using in this course and then begin exploring the

00:00:12.600 --> 00:00:14.560
LOIC graphical user interface.

00:00:15.440 --> 00:00:18.690
This demo will prepare us for the rest of this course where we'll dive into

00:00:18.690 --> 00:00:21.560
the practical application and attack our lab targets.

00:00:22.140 --> 00:00:24.920
Let's head over to the lab and get started.

00:00:24.920 --> 00:00:29.260
For this lab, I'm using five different virtual machines.

00:00:29.260 --> 00:00:31.860
To make the environment easier to replicate,

00:00:31.980 --> 00:00:34.560
I created a Vagrantfile that will enable you to quickly

00:00:34.560 --> 00:00:36.660
create these bottom four machines here.

00:00:37.240 --> 00:00:39.460
You can obtain the Kali Linux machine separately.

00:00:40.540 --> 00:00:43.450
The Vagrantfile is found in the demo files for this course.

00:00:44.240 --> 00:00:46.880
These machines are hosted in the Vagrant cloud and

00:00:46.880 --> 00:00:48.730
are deployed using Vagrantfiles.

00:00:48.730 --> 00:00:52.460
You'll need Vagrant and VirtualBox installed to use these.

00:00:53.640 --> 00:00:55.800
Once you've installed Vagrant and VirtualBox,

00:00:56.050 --> 00:00:58.100
you just need to make a few modifications to the

00:00:58.100 --> 00:01:00.060
Vagrantfile to match your environment.

00:01:00.740 --> 00:01:03.920
This Vagrantfile deploys a small network with two targets,

00:01:03.930 --> 00:01:05.610
a host with LOIC installed,

00:01:05.690 --> 00:01:08.740
and a machine acting as a router between your home network

00:01:08.820 --> 00:01:11.250
and an internal LAN containing our targets.

00:01:11.250 --> 00:01:13.760
To deploy each machine individually,

00:01:14.240 --> 00:01:17.330
you add the hostname to the end of the vagrant up command.

00:01:17.330 --> 00:01:21.460
Within the file, you need to modify the VM network section here.

00:01:22.240 --> 00:01:25.260
Change the bridge value to reflect your local interface.

00:01:26.340 --> 00:01:26.920
Next,

00:01:26.930 --> 00:01:30.280
you need to modify these shell commands and configure this default

00:01:30.280 --> 00:01:33.860
gateway to be your local LANs default gateway IP address.

00:01:34.440 --> 00:01:37.760
This route delete removes the default gateway that Vagrant adds,

00:01:37.770 --> 00:01:40.590
which forces all traffic to flow through the interfaces

00:01:40.590 --> 00:01:42.900
we configured in the previous step.

00:01:42.900 --> 00:01:45.610
You can also change this section to provide the

00:01:45.610 --> 00:01:48.180
resources to the machines that you desire.

00:01:48.180 --> 00:01:52.960
For my internal testing, all the settings in this Vagrantfile worked just fine.

00:01:54.540 --> 00:01:57.260
I have the Ubuntu router set with an internal

00:01:57.260 --> 00:02:01.110
interface IP address of 10.0.0.251.

00:02:01.110 --> 00:02:04.400
For the Metasploitable machine,

00:02:04.400 --> 00:02:07.800
this script sets the default gateway to that IP and

00:02:07.800 --> 00:02:09.550
removes the route added by Vagrant,

00:02:09.940 --> 00:02:12.550
forcing its traffic to flow through the Ubuntu Server.

00:02:13.740 --> 00:02:17.150
I configure the Metasploitable 3 machine the same way.

00:02:17.150 --> 00:02:21.190
The LOIC host is added to your home network and uses a

00:02:21.190 --> 00:02:23.770
bridged interface like the Ubuntu router.

00:02:23.770 --> 00:02:27.770
This host has a desktop interface and already has LOIC

00:02:27.770 --> 00:02:30.680
installed along with the necessary tools to make it work

00:02:30.680 --> 00:02:32.350
with a Linux operating system.

00:02:33.340 --> 00:02:34.630
To deploy these machines,

00:02:34.650 --> 00:02:37.060
simply navigate to the directory on your computer

00:02:37.540 --> 00:02:39.760
and run the command vagrant up.

00:02:40.440 --> 00:02:42.610
Vagrant will download the machines from the cloud,

00:02:43.040 --> 00:02:47.150
install them on your system, and configure them according to the Vagrantfile.

00:02:48.240 --> 00:02:53.540
The LOIC host is a large file since it has a desktop installed on it. If you

00:02:53.540 --> 00:02:57.920
prefer to install LOIC on your local machine or an existing virtual machine,

00:02:57.920 --> 00:03:02.070
there are instructions available on the GitHub Pages, and if you're using Kali

00:03:02.070 --> 00:03:07.240
Linux, there's instructions available in the demo files. Installing this Kali

00:03:07.240 --> 00:03:08.520
Linux machine is optional.

00:03:08.660 --> 00:03:11.660
However, I'll be using it for the last two demos of this course.

00:03:12.240 --> 00:03:15.460
I'm only using it to run LOIC, so if you want to follow along,

00:03:15.470 --> 00:03:19.160
just install LOIC on any second machine and that will work just fine.

00:03:20.440 --> 00:03:23.300
Once your lab is built, we need to make a couple of configuration

00:03:23.300 --> 00:03:26.560
changes to ensure that traffic is routed properly.

00:03:27.640 --> 00:03:32.690
Start by logging into your Ubuntu machine. To do that, you can just run

00:03:32.780 --> 00:03:38.350
vagrant ssh ubuntu. The password for this machine is vagrant.

00:03:39.040 --> 00:03:42.870
Once you're logged in, use ifconfig to get the IP address

00:03:42.880 --> 00:03:48.220
of the external interface, which is enp0s8. In my case,

00:03:48.220 --> 00:03:52.650
this IP address is 192.168.2.15.

00:03:53.440 --> 00:03:56.070
Once you have the IP address, log into Host 1 from the

00:03:56.070 --> 00:03:59.890
desktop. The password for this machine is also vagrant, as

00:03:59.890 --> 00:04:01.550
it is with most Vagrant hosts.

00:04:02.740 --> 00:04:06.020
Once you've logged in, open a terminal and add a route using the following

00:04:06.020 --> 00:04:19.459
command, sudo route add ‑net 10.0.0.0 netmask 255.255.255.0.

00:04:20.140 --> 00:04:25.440
And for a gateway, use the IP address you found in the previous step. In

00:04:25.440 --> 00:04:28.090
my environment, I've already added this route, so this is just an

00:04:28.090 --> 00:04:30.460
example. Your output should be a little different.

00:04:31.440 --> 00:04:32.550
Once the route is added,

00:04:32.940 --> 00:04:36.480
verify that you can ping the internal network by sending a ping to

00:04:36.480 --> 00:04:40.950
10.0.0.100, which is our Metasploitable 2 host.

00:04:43.440 --> 00:04:46.310
You can check the connectivity to Metasploitable 3 by

00:04:46.310 --> 00:04:50.760
accessing 10.0.0.101 from your web browser.

00:04:52.240 --> 00:04:54.760
If you arrive at this page and your pings were successful,

00:04:55.140 --> 00:04:57.960
you can access the hosts and your lab is ready.

00:04:59.240 --> 00:05:02.070
If you use the Vagrantfiles to deploy your lab, then your

00:05:02.070 --> 00:05:06.130
LOIC host already has LOIC installed and the IRC programs

00:05:06.130 --> 00:05:07.460
we'll use in later demos.

00:05:08.040 --> 00:05:10.160
There are shortcuts for each of these on the desktop.

00:05:11.140 --> 00:05:15.340
Let's go ahead and open LOIC. All right, we have our LOIC

00:05:15.340 --> 00:05:17.950
interface and we're ready to start exploring the tool.

00:05:19.340 --> 00:05:23.280
The LOIC interface is very intuitive, and each section is numbered in

00:05:23.280 --> 00:05:27.340
the order that you enter the information before executing your attack.

00:05:27.340 --> 00:05:32.380
By default, the interface is in manual mode where you control LOIC's

00:05:32.380 --> 00:05:34.990
behavior. In this first section,

00:05:35.000 --> 00:05:38.590
you enter either the URL or the IP address for your target

00:05:38.590 --> 00:05:41.160
host and then select the Lock on button.

00:05:42.140 --> 00:05:42.890
Once entered,

00:05:42.900 --> 00:05:45.590
your selected target will appear in this section to

00:05:45.590 --> 00:05:48.630
confirm. In the second section,

00:05:48.810 --> 00:05:51.560
you determine the additional options used in your attack.

00:05:52.340 --> 00:05:54.130
After selecting the timeout value,

00:05:54.180 --> 00:05:58.360
you can add an HTTP subsite if you're using the HTTP protocol

00:05:58.740 --> 00:06:02.060
or a custom message if using TCP or UDP.

00:06:02.940 --> 00:06:07.350
You can also check these boxes to use Git or gZip if the selected protocol

00:06:07.350 --> 00:06:11.550
supports it. In this next section, you can set a different port,

00:06:11.940 --> 00:06:15.260
select your protocol, and determine the number of threads.

00:06:15.260 --> 00:06:19.140
Decide whether to wait for a reply with each packet and

00:06:19.150 --> 00:06:20.650
set the speed of your attack.

00:06:21.840 --> 00:06:25.170
We'll go over these options in more detail in the next demo when we

00:06:25.170 --> 00:06:27.660
run our first attack against one of our targets.

00:06:28.340 --> 00:06:30.130
Once you set the selected options,

00:06:30.200 --> 00:06:34.290
you push this button to start the attack. You can view the status

00:06:34.290 --> 00:06:36.660
as it progresses in this bottom section here.

00:06:37.540 --> 00:06:40.680
All right, we're ready to get started with the next demos where we'll run an

00:06:40.680 --> 00:06:44.360
attack. For a quick recap, after completing this demo,

00:06:44.500 --> 00:06:47.860
you should have a working lab environment with two potential targets.

00:06:48.640 --> 00:06:52.660
You should have a host with LOIC installed and access to the interface.

00:06:53.240 --> 00:06:56.190
You should be familiar with the LOIC interface and know

00:06:56.190 --> 00:06:57.960
what each field is used to configure.
