WEBVTT

00:00:00.000 --> 00:00:03.200 align:middle line:90%


00:00:03.200 --> 00:00:04.940 align:middle line:90%
Welcome to Mapping a Network.

00:00:04.940 --> 00:00:07.115 align:middle line:84%
I'm Josh Mason, your
instructor for this section.

00:00:07.115 --> 00:00:10.500 align:middle line:90%


00:00:10.500 --> 00:00:13.530 align:middle line:84%
In this lesson, we're going to
cover the purpose, the process,

00:00:13.530 --> 00:00:16.474 align:middle line:84%
and then a few tools
for mapping a network.

00:00:16.474 --> 00:00:19.190 align:middle line:90%


00:00:19.190 --> 00:00:22.490 align:middle line:84%
So the purpose, we're going to
talk about scope and discovery.

00:00:22.490 --> 00:00:26.210 align:middle line:84%
So scope, when you
start a pen test,

00:00:26.210 --> 00:00:28.730 align:middle line:90%
you're going to actually begin--

00:00:28.730 --> 00:00:31.250 align:middle line:84%
before you touch anything,
before you actually

00:00:31.250 --> 00:00:33.500 align:middle line:84%
do any of the
research, you're going

00:00:33.500 --> 00:00:36.050 align:middle line:84%
to negotiate with your
client and determine,

00:00:36.050 --> 00:00:42.013 align:middle line:84%
what is the most useful use
of you for their organization?

00:00:42.013 --> 00:00:43.430 align:middle line:84%
You're running a
penetration test.

00:00:43.430 --> 00:00:45.680 align:middle line:84%
It might be you
as an individual.

00:00:45.680 --> 00:00:46.880 align:middle line:90%
It might be a team.

00:00:46.880 --> 00:00:50.570 align:middle line:84%
Either way, you need to run a
penetration test that actually

00:00:50.570 --> 00:00:53.420 align:middle line:84%
provides them value,
provides them something

00:00:53.420 --> 00:00:58.220 align:middle line:84%
that they can then turn around
and mitigate risk and harden

00:00:58.220 --> 00:01:02.390 align:middle line:84%
their systems,
become more secure.

00:01:02.390 --> 00:01:05.239 align:middle line:84%
Some clients might just
be looking to check a box.

00:01:05.239 --> 00:01:10.340 align:middle line:84%
Some clients might need a
no-kidding penetration test

00:01:10.340 --> 00:01:12.950 align:middle line:90%
on their system.

00:01:12.950 --> 00:01:14.840 align:middle line:84%
Let's give them the
benefit of the doubt.

00:01:14.840 --> 00:01:17.330 align:middle line:84%
Assume that they want a
good penetration test.

00:01:17.330 --> 00:01:20.180 align:middle line:84%
But you also need to understand
that if they're a company that

00:01:20.180 --> 00:01:22.970 align:middle line:84%
makes money, if they are an
organization that provides

00:01:22.970 --> 00:01:26.210 align:middle line:84%
something to somebody,
your penetration test,

00:01:26.210 --> 00:01:28.430 align:middle line:84%
if it goes the wrong
way, if you accidentally

00:01:28.430 --> 00:01:30.200 align:middle line:84%
DoS something or
knock something over,

00:01:30.200 --> 00:01:32.660 align:middle line:84%
you could take out
a production system.

00:01:32.660 --> 00:01:38.240 align:middle line:84%
And they might be SOL and
losing money or losing clients,

00:01:38.240 --> 00:01:42.110 align:middle line:84%
or if it's a hospital,
worse things.

00:01:42.110 --> 00:01:44.280 align:middle line:84%
And we don't want
that to happen.

00:01:44.280 --> 00:01:47.420 align:middle line:84%
So you need to figure
out the scope of what

00:01:47.420 --> 00:01:50.330 align:middle line:84%
will provide them value
while not interfering

00:01:50.330 --> 00:01:53.250 align:middle line:90%
with their business.

00:01:53.250 --> 00:01:57.030 align:middle line:84%
Once you have that all
sorted, then it becomes, well,

00:01:57.030 --> 00:01:58.460 align:middle line:84%
what do you have
available to you?

00:01:58.460 --> 00:02:01.640 align:middle line:84%
Are you going to be given
physical access to maybe plug

00:02:01.640 --> 00:02:02.540 align:middle line:90%
into their network?

00:02:02.540 --> 00:02:05.450 align:middle line:84%
Are you going to be given a
VPN connection to start out?

00:02:05.450 --> 00:02:11.030 align:middle line:84%
Or will they say, hey, come at
me bro, and you have to figure

00:02:11.030 --> 00:02:12.230 align:middle line:90%
it all out for yourself?

00:02:12.230 --> 00:02:16.370 align:middle line:84%
Hopefully it's
not that last one.

00:02:16.370 --> 00:02:18.913 align:middle line:84%
Without some give
and take in this,

00:02:18.913 --> 00:02:20.330 align:middle line:84%
they're not going
to get the value

00:02:20.330 --> 00:02:22.055 align:middle line:90%
that you can really provide.

00:02:22.055 --> 00:02:24.620 align:middle line:90%


00:02:24.620 --> 00:02:26.420 align:middle line:84%
In the end, though,
we're going to take

00:02:26.420 --> 00:02:30.380 align:middle line:84%
this, a cloud with
a bunch of unknowns,

00:02:30.380 --> 00:02:34.100 align:middle line:84%
and turn it into this,
a network that actually

00:02:34.100 --> 00:02:36.575 align:middle line:90%
shows you something useful.

00:02:36.575 --> 00:02:39.950 align:middle line:90%


00:02:39.950 --> 00:02:43.220 align:middle line:84%
Now, the process that
we're going to go through,

00:02:43.220 --> 00:02:47.750 align:middle line:84%
we'll look at physical access,
sniffing, ARP, and then ICMP.

00:02:47.750 --> 00:02:51.740 align:middle line:84%
That's a couple
techniques and a couple

00:02:51.740 --> 00:02:56.770 align:middle line:84%
of protocols that will
help us to kind of flesh

00:02:56.770 --> 00:03:02.620 align:middle line:84%
out this overall
mapping process.

00:03:02.620 --> 00:03:05.490 align:middle line:84%
So the physical
access, if you are

00:03:05.490 --> 00:03:09.030 align:middle line:84%
doing a penetration test that
includes physical security,

00:03:09.030 --> 00:03:13.440 align:middle line:84%
maybe testing their
guards or cameras,

00:03:13.440 --> 00:03:18.510 align:middle line:84%
their access controls,
then you can include that

00:03:18.510 --> 00:03:20.580 align:middle line:84%
as part of getting
network access.

00:03:20.580 --> 00:03:23.400 align:middle line:84%
Or in the process of
testing those things,

00:03:23.400 --> 00:03:28.020 align:middle line:84%
maybe you get access to
a console, to a desktop,

00:03:28.020 --> 00:03:32.280 align:middle line:84%
whatever, and find some
IP addresses that way.

00:03:32.280 --> 00:03:35.475 align:middle line:90%
Or through some OSINT--

00:03:35.475 --> 00:03:38.280 align:middle line:84%
we'll go through intelligence
gathering and information

00:03:38.280 --> 00:03:40.830 align:middle line:84%
gathering in another
lesson, in another section.

00:03:40.830 --> 00:03:44.460 align:middle line:84%
But through DNS records,
through websites,

00:03:44.460 --> 00:03:49.500 align:middle line:84%
there's ways of finding IP
addresses without even having

00:03:49.500 --> 00:03:51.840 align:middle line:90%
to touch the network itself.

00:03:51.840 --> 00:03:54.090 align:middle line:84%
Or we can get into some
social engineering.

00:03:54.090 --> 00:03:58.530 align:middle line:84%
Could you get someone to
tell you all the things

00:03:58.530 --> 00:04:00.030 align:middle line:90%
that you want to know?

00:04:00.030 --> 00:04:02.410 align:middle line:90%
Perhaps.

00:04:02.410 --> 00:04:04.600 align:middle line:90%
Creativity is your limit there.

00:04:04.600 --> 00:04:05.285 align:middle line:90%
And skip.

00:04:05.285 --> 00:04:08.090 align:middle line:90%


00:04:08.090 --> 00:04:11.390 align:middle line:84%
If we do have access, once we
do have access to the network,

00:04:11.390 --> 00:04:14.930 align:middle line:84%
either through that VPN, that
physical connection or you work

00:04:14.930 --> 00:04:16.940 align:middle line:84%
your way to a
physical connection,

00:04:16.940 --> 00:04:23.060 align:middle line:84%
then the easiest way of finding
out what hosts are out there,

00:04:23.060 --> 00:04:26.840 align:middle line:84%
what IP addresses, what MAC
addresses are on this network

00:04:26.840 --> 00:04:28.490 align:middle line:84%
is through some
passive reconnaissance,

00:04:28.490 --> 00:04:29.600 align:middle line:90%
through sniffing.

00:04:29.600 --> 00:04:33.320 align:middle line:84%
We can run tcpdump or Wireshark,
or there's several other tools

00:04:33.320 --> 00:04:36.420 align:middle line:90%
for packet capture.

00:04:36.420 --> 00:04:38.900 align:middle line:84%
You could just watch the
normal network traffic,

00:04:38.900 --> 00:04:40.880 align:middle line:84%
see what emails,
see what websites,

00:04:40.880 --> 00:04:44.870 align:middle line:84%
see what they're
uploading to file servers.

00:04:44.870 --> 00:04:49.460 align:middle line:84%
And in that, you do some
information gathering

00:04:49.460 --> 00:04:53.270 align:middle line:84%
but also collect IP
addresses and MAC addresses

00:04:53.270 --> 00:04:55.070 align:middle line:90%
for further enumeration.

00:04:55.070 --> 00:04:58.960 align:middle line:90%


00:04:58.960 --> 00:05:01.300 align:middle line:84%
We're going to take
advantage of ARP.

00:05:01.300 --> 00:05:04.030 align:middle line:84%
ARP is Address
Resolution Protocol.

00:05:04.030 --> 00:05:07.210 align:middle line:84%
It maps IP addresses
to MAC addresses.

00:05:07.210 --> 00:05:10.510 align:middle line:84%
And the way it does that is
sends out these messages.

00:05:10.510 --> 00:05:13.240 align:middle line:90%
Who has 10.10.1.5?

00:05:13.240 --> 00:05:15.640 align:middle line:90%
Tell 10.10.1.7, tell me.

00:05:15.640 --> 00:05:19.210 align:middle line:84%
And it'll send that
out in a broadcast.

00:05:19.210 --> 00:05:22.990 align:middle line:84%
And if anyone has 10.10.1.5,
they'll be like, hey,

00:05:22.990 --> 00:05:28.570 align:middle line:90%
10.10.1.5 is 00:0c:29:af:ea:d2.

00:05:28.570 --> 00:05:33.790 align:middle line:84%
And then my machine, 10.10.1.7,
will add that to its ARP table.

00:05:33.790 --> 00:05:38.380 align:middle line:84%
Now if it needs to send
something to 10.10.1.7 for some

00:05:38.380 --> 00:05:43.660 align:middle line:84%
reason, it knows, I need to
tack on the 00:d2 MAC address

00:05:43.660 --> 00:05:45.910 align:middle line:84%
for any packets
that are going out.

00:05:45.910 --> 00:05:49.570 align:middle line:84%
Well, we can do
an ARP scan where

00:05:49.570 --> 00:05:51.820 align:middle line:84%
we send out all of these
requests for everything

00:05:51.820 --> 00:05:52.630 align:middle line:90%
on our subnet.

00:05:52.630 --> 00:05:56.560 align:middle line:84%
It goes really fast and you
get replies if ARP is enabled.

00:05:56.560 --> 00:05:58.810 align:middle line:84%
And it usually
is, because that's

00:05:58.810 --> 00:06:01.000 align:middle line:90%
kind of how networks work.

00:06:01.000 --> 00:06:03.520 align:middle line:90%
Now, ARP can be turned off.

00:06:03.520 --> 00:06:06.220 align:middle line:84%
And everything can be
manually configured

00:06:06.220 --> 00:06:08.260 align:middle line:84%
and everything manually
added to ARP tables

00:06:08.260 --> 00:06:11.020 align:middle line:90%
but might still work.

00:06:11.020 --> 00:06:13.208 align:middle line:84%
And it might be kind of
quiet, depends on what

00:06:13.208 --> 00:06:14.500 align:middle line:90%
you have running on the system.

00:06:14.500 --> 00:06:17.120 align:middle line:90%


00:06:17.120 --> 00:06:19.910 align:middle line:84%
The next thing we'll talk
about is ICMP, Internet Control

00:06:19.910 --> 00:06:21.440 align:middle line:90%
Message Protocol.

00:06:21.440 --> 00:06:25.580 align:middle line:84%
Now, this protocol is used for
diagnosing network connectivity

00:06:25.580 --> 00:06:27.360 align:middle line:90%
issues.

00:06:27.360 --> 00:06:29.810 align:middle line:84%
So if packets aren't
making it somewhere,

00:06:29.810 --> 00:06:35.780 align:middle line:84%
if there's dropped packets,
ICMP is kind of the answer.

00:06:35.780 --> 00:06:38.360 align:middle line:84%
Usually, you get a reply
back of some sort of--

00:06:38.360 --> 00:06:41.000 align:middle line:90%
why things are going wrong.

00:06:41.000 --> 00:06:43.940 align:middle line:84%
There's a couple of tools
that we'll use with ICMP.

00:06:43.940 --> 00:06:45.560 align:middle line:90%
One is Traceroute.

00:06:45.560 --> 00:06:48.230 align:middle line:84%
And that will show
you all of the points

00:06:48.230 --> 00:06:54.610 align:middle line:84%
in between the destination
and source for packets

00:06:54.610 --> 00:06:56.380 align:middle line:84%
and where things
might be dropping off.

00:06:56.380 --> 00:06:58.900 align:middle line:90%
And then Ping, Ping works great.

00:06:58.900 --> 00:07:00.280 align:middle line:90%
It says, hey, are you there?

00:07:00.280 --> 00:07:03.145 align:middle line:90%
It asks for a reply.

00:07:03.145 --> 00:07:05.710 align:middle line:90%


00:07:05.710 --> 00:07:09.940 align:middle line:84%
It sends what's called
a type 8 echo request.

00:07:09.940 --> 00:07:13.120 align:middle line:84%
And I think of it either
like a radar ping,

00:07:13.120 --> 00:07:15.730 align:middle line:84%
like, ping, waiting
for a ping back.

00:07:15.730 --> 00:07:21.650 align:middle line:84%
Or I like the analogy of someone
in a dark room with a ping pong

00:07:21.650 --> 00:07:22.150 align:middle line:90%
ball.

00:07:22.150 --> 00:07:23.380 align:middle line:90%
You don't know what's out there.

00:07:23.380 --> 00:07:25.850 align:middle line:84%
If you throw the ping pong
ball and it comes back at you,

00:07:25.850 --> 00:07:27.433 align:middle line:84%
then you know there's
something there.

00:07:27.433 --> 00:07:32.110 align:middle line:84%
If it doesn't, then there's
not something right there.

00:07:32.110 --> 00:07:34.040 align:middle line:84%
Now we're going to do
that with IP addresses.

00:07:34.040 --> 00:07:38.000 align:middle line:84%
We'll throw a ping pong ball
or Ping that IP address.

00:07:38.000 --> 00:07:40.630 align:middle line:84%
And if it sends a reply
back, we can be like, hey,

00:07:40.630 --> 00:07:41.680 align:middle line:90%
there is something there.

00:07:41.680 --> 00:07:44.740 align:middle line:84%
If it doesn't send a reply
back, there's other things.

00:07:44.740 --> 00:07:49.195 align:middle line:84%
It might still be there, but
maybe reply is turned off.

00:07:49.195 --> 00:07:51.070 align:middle line:84%
Network administrators
will do that sometimes

00:07:51.070 --> 00:07:52.870 align:middle line:90%
for security reasons.

00:07:52.870 --> 00:07:54.870 align:middle line:84%
Because they don't want
people doing Ping scans.

00:07:54.870 --> 00:07:58.770 align:middle line:90%


00:07:58.770 --> 00:08:02.640 align:middle line:84%
Well, we're going to utilize
some tools to practice

00:08:02.640 --> 00:08:04.330 align:middle line:90%
some of these things.

00:08:04.330 --> 00:08:05.910 align:middle line:90%
So we'll look at Wireshark.

00:08:05.910 --> 00:08:09.450 align:middle line:84%
We'll run Arp-scan,
Ping and FPing.

00:08:09.450 --> 00:08:12.690 align:middle line:84%
And also, Nmap has
a Ping function.

00:08:12.690 --> 00:08:17.228 align:middle line:84%
But we'll finish it off with
the GUI version of Zenmap.

00:08:17.228 --> 00:08:19.520 align:middle line:84%
And that's what we'll cover
for the rest of the lesson.

00:08:19.520 --> 00:08:28.990 align:middle line:90%


00:08:28.990 --> 00:08:31.030 align:middle line:90%
We had started out in Wireshark.

00:08:31.030 --> 00:08:34.726 align:middle line:90%


00:08:34.726 --> 00:08:38.460 align:middle line:84%
And I'm in a parent VM, but
I'll bring up Wireshark.

00:08:38.460 --> 00:08:41.360 align:middle line:90%


00:08:41.360 --> 00:08:45.180 align:middle line:90%
And needs sudo privileges.

00:08:45.180 --> 00:08:46.410 align:middle line:90%
We want to look on our tap0.

00:08:46.410 --> 00:08:49.500 align:middle line:90%


00:08:49.500 --> 00:08:52.550 align:middle line:90%
We'll start a packet capture.

00:08:52.550 --> 00:08:55.940 align:middle line:84%
Now, we might not get
anything initially.

00:08:55.940 --> 00:09:05.475 align:middle line:90%
So let's run a little arp-scan.

00:09:05.475 --> 00:09:20.530 align:middle line:90%


00:09:20.530 --> 00:09:23.180 align:middle line:84%
We'll come back and look
at that in a minute.

00:09:23.180 --> 00:09:27.460 align:middle line:84%
But what we have is we
have all these ARP commands

00:09:27.460 --> 00:09:32.290 align:middle line:84%
that went out asking, hey,
who has this IP address?

00:09:32.290 --> 00:09:35.770 align:middle line:90%
Tell us, we're at 240.

00:09:35.770 --> 00:09:38.770 align:middle line:84%
Now, the neat thing we
can do with Wireshark

00:09:38.770 --> 00:09:43.720 align:middle line:84%
is go up to Statistics
and then Endpoints

00:09:43.720 --> 00:09:47.500 align:middle line:84%
and see all of our
Ethernet endpoints.

00:09:47.500 --> 00:09:52.940 align:middle line:90%


00:09:52.940 --> 00:09:55.010 align:middle line:84%
And this gives us all
the MAC addresses.

00:09:55.010 --> 00:09:56.515 align:middle line:90%
So that could be useful.

00:09:56.515 --> 00:10:05.330 align:middle line:90%


00:10:05.330 --> 00:10:07.525 align:middle line:84%
But somewhere in here,
there's got to be replies.

00:10:07.525 --> 00:10:10.930 align:middle line:90%


00:10:10.930 --> 00:10:13.280 align:middle line:90%
There we go.

00:10:13.280 --> 00:10:17.800 align:middle line:84%
So 213 is at these
MAC addresses.

00:10:17.800 --> 00:10:22.780 align:middle line:90%


00:10:22.780 --> 00:10:28.560 align:middle line:84%
We've got a 96, a 100, looks
like they're multi-hosted.

00:10:28.560 --> 00:10:36.162 align:middle line:90%
We've got a 48, 1 and dot 6.

00:10:36.162 --> 00:10:37.120 align:middle line:90%
So that's kind of neat.

00:10:37.120 --> 00:10:39.802 align:middle line:90%


00:10:39.802 --> 00:10:41.135 align:middle line:90%
Now let's look at that arp-scan.

00:10:41.135 --> 00:10:44.840 align:middle line:90%


00:10:44.840 --> 00:10:47.120 align:middle line:90%
I just run that command.

00:10:47.120 --> 00:10:53.640 align:middle line:84%
Because ARP is sending stuff
out over that layer too,

00:10:53.640 --> 00:10:56.100 align:middle line:90%
it needs sudo privileges.

00:10:56.100 --> 00:11:02.220 align:middle line:84%
And we're running it on our
interface of tap0 for our VPN.

00:11:02.220 --> 00:11:06.840 align:middle line:84%
And then we're going to generate
based off of our subnet.

00:11:06.840 --> 00:11:10.830 align:middle line:84%
And we could look at
that subnet within ip a.

00:11:10.830 --> 00:11:13.670 align:middle line:90%


00:11:13.670 --> 00:11:16.190 align:middle line:90%
We see our tap0.

00:11:16.190 --> 00:11:21.310 align:middle line:90%
We have 10.142.111 dot--

00:11:21.310 --> 00:11:23.965 align:middle line:84%
[? we're ?] 240 on
a CIDR 24 network.

00:11:23.965 --> 00:11:27.520 align:middle line:90%


00:11:27.520 --> 00:11:30.070 align:middle line:84%
So again, we could
run that scan.

00:11:30.070 --> 00:11:33.404 align:middle line:84%
And we see we've got
a dot 6, a dot 1,

00:11:33.404 --> 00:11:39.930 align:middle line:84%
dot 48, dot 96, dot 99,
dot 100, and dot 213.

00:11:39.930 --> 00:11:45.450 align:middle line:84%
And we're not showing
you, but we are dot 240.

00:11:45.450 --> 00:11:46.600 align:middle line:90%
And that's perfectly fine.

00:11:46.600 --> 00:11:49.467 align:middle line:84%
ARP's broadcasts
from us, so we're not

00:11:49.467 --> 00:11:50.800 align:middle line:90%
going to send ourselves a reply.

00:11:50.800 --> 00:11:54.297 align:middle line:90%


00:11:54.297 --> 00:11:55.255 align:middle line:90%
Now we'll look at Ping.

00:11:55.255 --> 00:11:58.130 align:middle line:90%


00:11:58.130 --> 00:12:07.910 align:middle line:84%
If we were to run ping on
our 10.142.111.6, which

00:12:07.910 --> 00:12:14.760 align:middle line:84%
we discovered with arp-scan, we
see what we get a return back.

00:12:14.760 --> 00:12:16.230 align:middle line:90%
And we stop it.

00:12:16.230 --> 00:12:20.250 align:middle line:84%
We sent seven packets
transmitted and seven received,

00:12:20.250 --> 00:12:22.500 align:middle line:90%
0% packet loss.

00:12:22.500 --> 00:12:25.590 align:middle line:84%
We can assume that dot
6 is working and it's up

00:12:25.590 --> 00:12:27.690 align:middle line:90%
and we can connect to it.

00:12:27.690 --> 00:12:33.050 align:middle line:84%
Now let's run that
again with a dot 5 just

00:12:33.050 --> 00:12:35.150 align:middle line:84%
to see what the
difference would be.

00:12:35.150 --> 00:12:38.690 align:middle line:84%
And we get destination
host unreachable.

00:12:38.690 --> 00:12:41.750 align:middle line:84%
And if we stop it, we see
seven packets transmitted,

00:12:41.750 --> 00:12:47.040 align:middle line:84%
zero received, some errors,
and 100% packet loss.

00:12:47.040 --> 00:12:49.925 align:middle line:84%
So dot 5 we are not able
to connect to with ICMP.

00:12:49.925 --> 00:12:53.358 align:middle line:90%


00:12:53.358 --> 00:12:54.650 align:middle line:90%
We'll now take a look at FPing.

00:12:54.650 --> 00:12:59.360 align:middle line:90%


00:12:59.360 --> 00:13:00.920 align:middle line:90%
Ping on its own is neat.

00:13:00.920 --> 00:13:03.710 align:middle line:84%
We could create
a script and send

00:13:03.710 --> 00:13:06.830 align:middle line:90%
Ping out to multiple hosts.

00:13:06.830 --> 00:13:10.580 align:middle line:84%
But on its own, Ping is
for one host at a time.

00:13:10.580 --> 00:13:13.160 align:middle line:84%
Fortunately, there's
a tool fping.

00:13:13.160 --> 00:13:20.840 align:middle line:84%
And fping will send out pings
to multiple hosts at one time

00:13:20.840 --> 00:13:24.870 align:middle line:84%
and give you a little
cleaner return back.

00:13:24.870 --> 00:13:27.380 align:middle line:84%
So we want to send
this out on our tap0.

00:13:27.380 --> 00:13:35.660 align:middle line:84%
We want to generate from
10.142.111.0 CIDR 24.

00:13:35.660 --> 00:13:38.660 align:middle line:84%
And we want to know all
the things that are alive.

00:13:38.660 --> 00:13:40.370 align:middle line:90%
And let's go.

00:13:40.370 --> 00:13:42.430 align:middle line:90%
It's finding stuff, 1, 6--

00:13:42.430 --> 00:13:42.930 align:middle line:90%
whoa.

00:13:42.930 --> 00:13:47.992 align:middle line:90%


00:13:47.992 --> 00:13:50.200 align:middle line:84%
We're getting host unreachable
from all those things.

00:13:50.200 --> 00:13:55.180 align:middle line:84%
Well, that started off well
and then got a little crazy.

00:13:55.180 --> 00:13:56.950 align:middle line:84%
There's a lot of
errors in there.

00:13:56.950 --> 00:14:01.000 align:middle line:90%
Errors are number 2.

00:14:01.000 --> 00:14:05.650 align:middle line:84%
So standard in is 0, standard
out is 1, standard error is 2.

00:14:05.650 --> 00:14:10.840 align:middle line:84%
So we do 2 redirected
to /dev/null.

00:14:10.840 --> 00:14:13.405 align:middle line:84%
We'll get the same output
without any of the errors.

00:14:13.405 --> 00:14:23.850 align:middle line:90%


00:14:23.850 --> 00:14:24.930 align:middle line:90%
And there it is.

00:14:24.930 --> 00:14:32.310 align:middle line:84%
We have 1, 6, 48,
96, 99, 100, and 240.

00:14:32.310 --> 00:14:34.205 align:middle line:84%
Now, that's actually
a little different

00:14:34.205 --> 00:14:35.205 align:middle line:90%
than what we had before.

00:14:35.205 --> 00:14:39.580 align:middle line:90%


00:14:39.580 --> 00:14:44.065 align:middle line:84%
I'm going to run this arp-scan
real fast just to compare.

00:14:44.065 --> 00:14:46.750 align:middle line:90%


00:14:46.750 --> 00:14:51.990 align:middle line:84%
So we showed up on
this ping scan for 240.

00:14:51.990 --> 00:14:56.460 align:middle line:90%
But 213 didn't show up with me.

00:14:56.460 --> 00:15:01.587 align:middle line:84%
There's a chance 213 doesn't
reply to ping messages.

00:15:01.587 --> 00:15:02.670 align:middle line:90%
Let's take a look at that.

00:15:02.670 --> 00:15:17.140 align:middle line:90%
So we'll ping 10.142.111.213.

00:15:17.140 --> 00:15:21.010 align:middle line:84%
And yeah, seven packets
transmitted, zero received.

00:15:21.010 --> 00:15:25.240 align:middle line:90%
So ping didn't find it.

00:15:25.240 --> 00:15:28.730 align:middle line:84%
And that can be
kind of confusing.

00:15:28.730 --> 00:15:34.510 align:middle line:84%
So we used ARP, and ARP did
find the host but ping did not.

00:15:34.510 --> 00:15:37.780 align:middle line:84%
That's why I showed you
two different tools.

00:15:37.780 --> 00:15:41.370 align:middle line:84%
Because sometimes one works,
sometimes the other one works.

00:15:41.370 --> 00:15:45.010 align:middle line:84%
I highly suggest you
use both or multiples.

00:15:45.010 --> 00:15:48.160 align:middle line:90%


00:15:48.160 --> 00:15:50.250 align:middle line:84%
Now we'll take a look
at doing this with Nmap.

00:15:50.250 --> 00:15:55.600 align:middle line:90%


00:15:55.600 --> 00:15:58.700 align:middle line:90%
So Nmap is a very powerful tool.

00:15:58.700 --> 00:16:01.720 align:middle line:84%
It's open source and
available on all operating

00:16:01.720 --> 00:16:04.300 align:middle line:90%
systems, including Windows.

00:16:04.300 --> 00:16:08.110 align:middle line:84%
And the way you run Nmap is
just with the command nmap.

00:16:08.110 --> 00:16:12.880 align:middle line:84%
And for our scan, we're
just going to use tack sn.

00:16:12.880 --> 00:16:16.270 align:middle line:90%


00:16:16.270 --> 00:16:19.600 align:middle line:84%
This little guy right there,
that's a dash or, in my case,

00:16:19.600 --> 00:16:21.370 align:middle line:90%
a tack.

00:16:21.370 --> 00:16:24.310 align:middle line:84%
Military background,
sorry about that.

00:16:24.310 --> 00:16:27.620 align:middle line:84%
If you haven't heard it
called the tack before,

00:16:27.620 --> 00:16:29.360 align:middle line:84%
that's what I'm
going to keep saying.

00:16:29.360 --> 00:16:31.810 align:middle line:90%
Can't help it.

00:16:31.810 --> 00:16:44.100 align:middle line:84%
And then our subnet
10.142.111.0 CIDR 24.

00:16:44.100 --> 00:16:45.525 align:middle line:90%
And Nmap will do its thing.

00:16:45.525 --> 00:16:48.510 align:middle line:90%


00:16:48.510 --> 00:16:59.890 align:middle line:84%
And here we get 1, 6, 48,
96, 99, 100, 213, and 240.

00:16:59.890 --> 00:17:01.990 align:middle line:84%
And what's kind
of crazy about all

00:17:01.990 --> 00:17:13.410 align:middle line:84%
that is that Nmap did some
interesting stuff near the end.

00:17:13.410 --> 00:17:16.470 align:middle line:90%


00:17:16.470 --> 00:17:17.609 align:middle line:90%
We're still capturing.

00:17:17.609 --> 00:17:20.240 align:middle line:90%


00:17:20.240 --> 00:17:24.020 align:middle line:90%
So there was ARP that went out.

00:17:24.020 --> 00:17:32.115 align:middle line:84%
There was some TCP traffic
that went out from us to 99.

00:17:32.115 --> 00:17:38.250 align:middle line:90%


00:17:38.250 --> 00:17:41.190 align:middle line:84%
Wanted to double check
to see if there was any

00:17:41.190 --> 00:17:43.170 align:middle line:90%
ICMP that Nmap used.

00:17:43.170 --> 00:17:46.380 align:middle line:90%


00:17:46.380 --> 00:17:47.380 align:middle line:90%
But it's pretty neat.

00:17:47.380 --> 00:17:49.830 align:middle line:84%
Now that we've done
these scans though,

00:17:49.830 --> 00:17:52.950 align:middle line:84%
if we look at our
endpoints in our IPv4,

00:17:52.950 --> 00:17:53.970 align:middle line:90%
we also get this list.

00:17:53.970 --> 00:17:56.610 align:middle line:90%


00:17:56.610 --> 00:18:00.240 align:middle line:84%
And I wouldn't worry too
much about these broadcasts.

00:18:00.240 --> 00:18:02.862 align:middle line:84%
Though these 169s
are interesting.

00:18:02.862 --> 00:18:04.320 align:middle line:84%
We won't worry too
much about that.

00:18:04.320 --> 00:18:06.840 align:middle line:90%


00:18:06.840 --> 00:18:14.210 align:middle line:84%
But again, 1, 6, 48, 96,
99, 100, 213, and 240, and a

00:18:14.210 --> 00:18:17.440 align:middle line:90%
broadcast.

00:18:17.440 --> 00:18:23.850 align:middle line:84%
So we've now identified those
same IPs multiple times.

00:18:23.850 --> 00:18:26.850 align:middle line:90%


00:18:26.850 --> 00:18:29.010 align:middle line:84%
The last tool I want to
introduce you to is Zenmap.

00:18:29.010 --> 00:18:35.050 align:middle line:90%


00:18:35.050 --> 00:18:39.280 align:middle line:84%
And Zenmap is a GUI
version of Nmap.

00:18:39.280 --> 00:18:43.250 align:middle line:84%
It is available on
all operating systems.

00:18:43.250 --> 00:18:44.785 align:middle line:90%
It's open source, also free.

00:18:44.785 --> 00:18:47.325 align:middle line:90%


00:18:47.325 --> 00:18:49.865 align:middle line:90%
All right, here is Nmap.

00:18:49.865 --> 00:18:51.115 align:middle line:90%
So we can throw in our subnet.

00:18:51.115 --> 00:18:54.410 align:middle line:90%


00:18:54.410 --> 00:18:57.350 align:middle line:84%
That's what I get,
opened it multiple times.

00:18:57.350 --> 00:19:02.480 align:middle line:90%
10.142.111.0 CIDR 24.

00:19:02.480 --> 00:19:06.080 align:middle line:84%
Then over here, we'll just
choose in our dropdown

00:19:06.080 --> 00:19:08.390 align:middle line:90%
the Ping skin.

00:19:08.390 --> 00:19:10.130 align:middle line:90%
Then we say Scan.

00:19:10.130 --> 00:19:14.720 align:middle line:84%
And we can see what the command
is, nmap -sn on our subnet.

00:19:14.720 --> 00:19:16.820 align:middle line:90%
And we get back the same reply.

00:19:16.820 --> 00:19:21.470 align:middle line:84%
What's neat though is
we can go to Topology--

00:19:21.470 --> 00:19:24.720 align:middle line:84%
and also, we get it
listed over here.

00:19:24.720 --> 00:19:28.820 align:middle line:84%
But we can go into Topology
and see it visually.

00:19:28.820 --> 00:19:31.370 align:middle line:84%
If we do further
scans, some discovery

00:19:31.370 --> 00:19:35.855 align:middle line:84%
scans, perhaps, we
might learn even more.

00:19:35.855 --> 00:19:38.995 align:middle line:84%
We'll get into that in
the following sections.

00:19:38.995 --> 00:19:42.230 align:middle line:90%


00:19:42.230 --> 00:19:44.360 align:middle line:84%
And with that, we will
close out this section

00:19:44.360 --> 00:19:48.500 align:middle line:90%
and move on to port scanning.

00:19:48.500 --> 00:19:49.000 align:middle line:90%