So in this video, we're going to put a game plan together.
It's going to drive our actions for the rest of these videos in this set of
videos.
So for our game plan, let's go ahead and let's use SourceNet across the board.
And as a reminder, SourceNet or SourcePat as a case may be depending on the
configuration
means that on the initial flow of traffic or swapping out the source IP address
information,
so our four is going to play our edge router and its IP address here at the
edge is 23.1.2.4.
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
And also for this demonstration, we're just going to assume that the entire
block of 23.1.2 is available to us.
And we have .100 here acting as a little representation of a web server out on
the public internet.
Again, this is all just in our lab environment.
AmphorstaticNet, let's go ahead and take PC30 right here and map its inside
address of 10.30.0.51.
And we'll map that to the outside address of 23.1.2.51.
So up here at the router doing that, this interface right here at FAA4/1 would
be labeled as an inside interface. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
For the purpose of NAT and gig 1.0 would be an inside interface.
For the purposes of NAT and then gig 2.0 would be an outside interface.
So traffic is being routed from an inside interface to an outside interface
based on the routing table here on our four.
We're going to have SourceNet implemented on it.
So our first example of SourceNet will be a static NAT translation between PC30
's address and the IP address of 23.1.2.51.
So for DynamicNet with 101 mapping for the pool, let's use the pool of
addresses of 23.1.2.
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
And let's go ahead and use the 64 subnet with a slash 26.
So that'll be our pool that will specify as part of our configuration for NAT
on our four.
And as far as who can be translated, now we could do it at 24 bit boundaries,
but let's go ahead and be a little more creative.
Let's go ahead and as far as who may be translated with DynamicNet, let's go
ahead and specify the 10.10.
And let's use the 32 subnet with a slash 27.
And that'll encompass this address right here of our client.
Now Windows computer, let's also go ahead and include 10.12.0. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Now Windows computer, let's also go ahead and include 10.12.0.
And again, we could use a slash 24 here, but let's get a little bit creative to
make it more interesting.
Let's go ahead and use the 48 subnet with a slash 29 bit mask.
And that will include PC12.
So I'm going to make a little note here.
This is our Windows 11. We'll match that in that range. And PC12 will match
here because this IP address is 10.12.0.0.51.
So we've got our static NAT game plan, dynamic NAT.
And let's also go ahead and do a dynamic pat option for everything else that
begins with 10.10. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
begins with 10.10.
Anything if they're trying to route traffic out to the internet.
So we'll go ahead and call that dynamic pat.
We'll give a little underline there.
And as far as what to translate to, let's just go ahead and use the IP address
that's already assigned on gig 2.0, which is 23.1.2.4.
And I'll make a little note here that's gig 2 slash 0 on our 4.
That's its interface address that it currently has.
So we'll do overloading on that existing address.
And as far as who can be translated, let's go ahead and make a note there 10.10
.
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
So we haven't been matched with the static NAT for PC30 or dynamic NAT with PC
12.
Other traffic like PC20's traffic on the 10.20.0 network.
It'll be captured in the pat rule right here.
And then the cool thing is that we can then test every single one of these
implementations and the results here as we try to send traffic from those
devices out to the internet.
Or in this case, our little pseudo internet to our server here at 23.1.2.100.
And I also intentionally on the server, it does not have a default gateway
going back to R4.
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
So unless we get translation to the 23.1.2 address space, this server will not
be able to respond back to us.
Because it has no idea about 10 anything as far as this central network is
concerned.
And that'll be another great verification that our NAT and pat rules are set up
right here correctly on R4.
And if we need to modify our tweaks in these rules as we go along, we'll do
that.
But as far as a game plan, a big picture view, let's go ahead and use this as
our game plan.
So with this in mind, join me in the next video as we begin to implement
network address translation on R4.