WEBVTT

1
00:00.000 --> 00:02.000
So in this video, we're going to put a game plan together.

2
00:02.000 --> 00:05.200
It's going to drive our actions for the rest of these videos in this set of

3
00:05.200 --> 00:06.000
videos.

4
00:06.000 --> 00:11.000
So for our game plan, let's go ahead and let's use SourceNet across the board.

5
00:11.000 --> 00:14.510
And as a reminder, SourceNet or SourcePat as a case may be depending on the

6
00:14.510 --> 00:15.000
configuration

7
00:15.000 --> 00:19.650
means that on the initial flow of traffic or swapping out the source IP address

8
00:19.650 --> 00:21.000
information,

9
00:21.000 --> 00:24.540
so our four is going to play our edge router and its IP address here at the

10
00:24.540 --> 00:27.000
edge is 23.1.2.4.

11
00:27.000 --> 00:30.710
And also for this demonstration, we're just going to assume that the entire
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:27.000 --> 00:30.710
And also for this demonstration, we're just going to assume that the entire

12
00:30.710 --> 00:33.000
block of 23.1.2 is available to us.

13
00:33.000 --> 00:38.320
And we have .100 here acting as a little representation of a web server out on

14
00:38.320 --> 00:39.000
the public internet.

15
00:39.000 --> 00:41.000
Again, this is all just in our lab environment.

16
00:41.000 --> 00:45.350
AmphorstaticNet, let's go ahead and take PC30 right here and map its inside

17
00:45.350 --> 00:48.000
address of 10.30.0.51.

18
00:48.000 --> 00:55.000
And we'll map that to the outside address of 23.1.2.51.

19
00:55.000 --> 00:58.350
So up here at the router doing that, this interface right here at FAA4/1 would

20
00:58.350 --> 01:00.000
be labeled as an inside interface.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
01:00.000 --> 01:03.000
For the purpose of NAT and gig 1.0 would be an inside interface.

22
01:03.000 --> 01:07.000
For the purposes of NAT and then gig 2.0 would be an outside interface.

23
01:07.000 --> 01:10.000
So traffic is being routed from an inside interface to an outside interface

24
01:10.000 --> 01:12.000
based on the routing table here on our four.

25
01:12.000 --> 01:14.000
We're going to have SourceNet implemented on it.

26
01:14.000 --> 01:19.240
So our first example of SourceNet will be a static NAT translation between PC30

27
01:19.240 --> 01:22.000
's address and the IP address of 23.1.2.51.

28
01:22.000 --> 01:26.620
So for DynamicNet with 101 mapping for the pool, let's use the pool of

29
01:26.620 --> 01:29.000
addresses of 23.1.2.

30
01:29.000 --> 01:34.000
And let's go ahead and use the 64 subnet with a slash 26.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

30
01:29.000 --> 01:34.000
And let's go ahead and use the 64 subnet with a slash 26.

31
01:34.000 --> 01:38.130
So that'll be our pool that will specify as part of our configuration for NAT

32
01:38.130 --> 01:39.000
on our four.

33
01:39.000 --> 01:42.180
And as far as who can be translated, now we could do it at 24 bit boundaries,

34
01:42.180 --> 01:44.000
but let's go ahead and be a little more creative.

35
01:44.000 --> 01:48.630
Let's go ahead and as far as who may be translated with DynamicNet, let's go

36
01:48.630 --> 01:51.000
ahead and specify the 10.10.

37
01:51.000 --> 01:57.000
And let's use the 32 subnet with a slash 27.

38
01:57.000 --> 01:59.000
And that'll encompass this address right here of our client.

39
01:59.000 --> 02:04.000
Now Windows computer, let's also go ahead and include 10.12.0.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

39
01:59.000 --> 02:04.000
Now Windows computer, let's also go ahead and include 10.12.0.

40
02:04.000 --> 02:07.190
And again, we could use a slash 24 here, but let's get a little bit creative to

41
02:07.190 --> 02:08.000
make it more interesting.

42
02:08.000 --> 02:13.000
Let's go ahead and use the 48 subnet with a slash 29 bit mask.

43
02:13.000 --> 02:14.000
And that will include PC12.

44
02:14.000 --> 02:15.000
So I'm going to make a little note here.

45
02:15.000 --> 02:22.370
This is our Windows 11. We'll match that in that range. And PC12 will match

46
02:22.370 --> 02:23.000
here because this IP address is 10.12.0.0.51.

47
02:23.000 --> 02:26.000
So we've got our static NAT game plan, dynamic NAT.

48
02:26.000 --> 02:29.390
And let's also go ahead and do a dynamic pat option for everything else that

49
02:29.390 --> 02:31.000
begins with 10.10.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

49
02:29.390 --> 02:31.000
begins with 10.10.

50
02:31.000 --> 02:34.000
Anything if they're trying to route traffic out to the internet.

51
02:34.000 --> 02:36.000
So we'll go ahead and call that dynamic pat.

52
02:36.000 --> 02:38.000
We'll give a little underline there.

53
02:38.000 --> 02:42.990
And as far as what to translate to, let's just go ahead and use the IP address

54
02:42.990 --> 02:46.000
that's already assigned on gig 2.0, which is 23.1.2.4.

55
02:46.000 --> 02:49.000
And I'll make a little note here that's gig 2 slash 0 on our 4.

56
02:49.000 --> 02:51.000
That's its interface address that it currently has.

57
02:51.000 --> 02:53.000
So we'll do overloading on that existing address.

58
02:53.000 --> 02:57.700
And as far as who can be translated, let's go ahead and make a note there 10.10

59
02:57.700 --> 02:58.000
.

60
02:58.000 --> 03:02.340
So we haven't been matched with the static NAT for PC30 or dynamic NAT with PC
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
02:58.000 --> 03:02.340
So we haven't been matched with the static NAT for PC30 or dynamic NAT with PC

61
03:02.340 --> 03:03.000
12.

62
03:03.000 --> 03:06.000
Other traffic like PC20's traffic on the 10.20.0 network.

63
03:06.000 --> 03:09.000
It'll be captured in the pat rule right here.

64
03:09.000 --> 03:11.380
And then the cool thing is that we can then test every single one of these

65
03:11.380 --> 03:15.560
implementations and the results here as we try to send traffic from those

66
03:15.560 --> 03:17.000
devices out to the internet.

67
03:17.000 --> 03:21.000
Or in this case, our little pseudo internet to our server here at 23.1.2.100.

68
03:21.000 --> 03:24.800
And I also intentionally on the server, it does not have a default gateway

69
03:24.800 --> 03:26.000
going back to R4.

70
03:26.000 --> 03:30.820
So unless we get translation to the 23.1.2 address space, this server will not
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

70
03:26.000 --> 03:30.820
So unless we get translation to the 23.1.2 address space, this server will not

71
03:30.820 --> 03:32.000
be able to respond back to us.

72
03:32.000 --> 03:36.160
Because it has no idea about 10 anything as far as this central network is

73
03:36.160 --> 03:37.000
concerned.

74
03:37.000 --> 03:41.170
And that'll be another great verification that our NAT and pat rules are set up

75
03:41.170 --> 03:43.000
right here correctly on R4.

76
03:43.000 --> 03:46.000
And if we need to modify our tweaks in these rules as we go along, we'll do

77
03:46.000 --> 03:46.000
that.

78
03:46.000 --> 03:49.220
But as far as a game plan, a big picture view, let's go ahead and use this as

79
03:49.220 --> 03:50.000
our game plan.

80
03:50.000 --> 03:54.400
So with this in mind, join me in the next video as we begin to implement

81
03:54.400 --> 03:57.000
network address translation on R4.