WEBVTT

00:01.460 --> 00:05.920
Section 3 troubleshooting issues with network scanning.

00:06.020 --> 00:14.060
Welcome to the video monitoring and map scans using verbose logging in this video we will troubleshoot

00:14.090 --> 00:20.240
issues that may arise from scanning in a dual home environment where both are wired and wireless interfaces

00:20.240 --> 00:21.150
are active.

00:21.860 --> 00:27.110
We'll also turn up the verbosity of logging on our unmap scans so we can see what's happening in real

00:27.110 --> 00:27.800
time.

00:28.480 --> 00:34.080
And we'll also learn about debugging the output of our scans for extreme situations such as.

00:34.090 --> 00:40.500
If you think you've discovered a bug and map itself when you start scanning your own corporate network

00:40.950 --> 00:46.470
or networks for other customers you probably aren't going to be scanning just a single subnet like we've

00:46.470 --> 00:48.260
been doing in some of our examples.

00:48.480 --> 00:51.660
You might be scanning hundreds or thousands of systems.

00:52.020 --> 00:57.510
So it's important to be able to monitor and troubleshoot scans and figure out if issues reside on the

00:57.510 --> 01:00.560
end points you're scanning or on your local system.

01:00.750 --> 01:04.570
So you can identify potential issues.

01:04.590 --> 01:09.210
Let's start with an example and say that you've been hired to do some network scanning for a client

01:09.660 --> 01:16.650
and they want an inventory of all systems across their land as far as IPs open ports software versions

01:16.650 --> 01:17.600
etc..

01:18.000 --> 01:23.680
So they give us a list of class C subnets which we save into a file called subnets sticks.

01:25.360 --> 01:26.400
Great.

01:26.450 --> 01:34.820
Now before we conduct our scan let's look at our interface list using and map space tak tak I-F list.

01:34.820 --> 01:39.920
This command came in handy a few years ago where I was connected to the customer's network on my wired

01:39.920 --> 01:40.820
interface.

01:41.210 --> 01:47.840
But a Wi-Fi hotspot on my wireless interface so to make sure I was doing all my scanning sourced out

01:47.840 --> 01:59.720
of the ether zero or wired interface I ran my scans like this and map space tak e E-3 0 and then my

01:59.730 --> 02:02.890
target's.

02:02.940 --> 02:08.250
So this is a handy command syntax to know if you find yourself in a similar situation in the future

02:09.310 --> 02:09.600
OK.

02:09.620 --> 02:15.470
Let's get back to the task at hand and start scanning these sediments now to get the most thorough results

02:15.470 --> 02:16.090
possible.

02:16.100 --> 02:25.280
Let's do a full scan of all 65000 plus TCAP ports which will specify by using TAC P Plus the port range

02:25.280 --> 02:32.640
we want to scan know that there is not a space between Ptak P and the first number of our port range

02:33.600 --> 02:37.170
and then finally we'll use the TAC lowercase i.

02:37.170 --> 02:45.550
Capital L Flegg and specify our list of subnets in the subnets at textfile.

02:45.560 --> 02:46.620
OK so great.

02:46.640 --> 02:49.990
The scan is running at least we think it is.

02:50.030 --> 02:51.100
Right.

02:51.230 --> 02:58.540
Without any output it's difficult to say if the scan will finish in 10 minutes 10 hours or even 10 days.

02:58.550 --> 03:05.420
So let's cancel out of this scan with control plus see and turn up logging so we have a better idea

03:05.420 --> 03:07.370
of what's going on behind the scenes.

03:08.450 --> 03:15.200
I'm going to run the exact same command again but add a space TAC V flag at the end.

03:15.500 --> 03:17.700
The V stands for verbosity.

03:17.780 --> 03:24.920
There are nine levels of verbosity which you can turn up by adding additional vees or you can use the

03:24.930 --> 03:29.510
plus a number like V-2 to call the level directly.

03:29.570 --> 03:34.730
It's good to know that the map reference guides says verbosity levels greater than two really aren't

03:34.730 --> 03:35.790
that useful.

03:36.170 --> 03:40.940
But let's turn verbosity up to two so to speak and see what happens.

03:46.520 --> 03:51.140
Now we get a much more lively status showing us what system is being scanned.

03:51.140 --> 03:57.320
The ports identified as being opened and a rough approximation as to how long our scan will take to

03:57.320 --> 03:58.670
finish.

03:58.670 --> 04:03.350
I wouldn't plan your day around this time estimation necessarily but it should at least give you an

04:03.350 --> 04:08.900
idea of whether or not the scan will finish in your lifetime.

04:08.910 --> 04:14.340
Now if for some reason verbose mode doesn't provide sufficient information for you debugging mode is

04:14.340 --> 04:20.340
available to floody with even more data just like the tech v option for verbosity.

04:20.430 --> 04:27.390
Debugging is enabled with a command line Flegg TAC D and can also be called directly by calling the

04:27.390 --> 04:28.050
TAC D.

04:28.080 --> 04:29.910
Multiple times.

04:29.910 --> 04:35.040
Note that the folks at end maps say debugging output is useful when you suspect you found a bug in and

04:35.040 --> 04:39.840
map or if you're just confused about what and map is doing and why.

04:39.840 --> 04:45.450
So be warned that the debugging feature is mostly intended for developers and the debug lines aren't

04:45.450 --> 04:47.560
always self-explanatory.

04:47.730 --> 04:53.040
If you don't understand align your best options really are to look it up in the source code or request

04:53.040 --> 04:53.630
help.

04:53.640 --> 04:57.390
The end maps mailing list.

04:57.590 --> 05:02.930
Since we're talking about getting help if you're having an issue with a map or a specific scan it's

05:02.930 --> 05:10.050
a good idea to periodically run and map space TAC V to see what version of end map is installed.

05:10.780 --> 05:18.120
I've got 7.6 0 installed here and if we do a quick spot check on and mapped out.

05:18.670 --> 05:23.170
It appears that indeed the latest version is 7.6 0.

05:23.330 --> 05:26.680
Or if you're just not sure if the version you have is the latest.

05:26.690 --> 05:34.130
It doesn't hurt to run an apt get update an apt get upgrade to pull down all the latest package updates

05:34.310 --> 05:41.250
from the Kalli repositories because and map updates will be included in that action in our next video.

05:41.250 --> 05:46.770
We need the latest version because you can acquire permissions from your clients and cloud vendors to

05:46.770 --> 05:52.600
ensure the scanning work you do is properly documented and approved by the necessary parties.
