So it is time for us to implement based on our plan,
SourceNet, which again is doing the initial translation
of the source address, again, on the initial flow of traffic.
So let's go ahead and take this VM here at 1010.0.10.
That's VM1.
And as his traffic goes out to the internet right here
at our gateway zero, we want to implement SourceNet
based on our plan.
And our plan is this, any traffic sourced from 1010.0,
anything, so the last octet could be 10 or 11, et cetera.
We want to map it to an IP address in the pool of 2312151 WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
We want to map it to an IP address in the pool of 2312151
through 250.
So prior to doing that, let's head over to this VM1
for a moment and just verify that prior to doing
network address translation, it cannot get out to the internet.
So we're at 1010.0.10 on VM1.
So first thing we're going to do is verify that that is true.
So we'll type in IF config for ethernet zero, press enter.
And sure enough, it's at 1010.0.10.
And we'll also type in route, just to make sure
we have a correct default gateway, which we do.
And let's do a ping, request to a trace out to 8.8.8.8.8. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
And let's do a ping, request to a trace out to 8.8.8.8.8.
Animated partway, so it made it at the first top of 1010.0.1.
And then it made it to 1064.0.0, which is the gateway connectivity
between gateway A and the tier zero gateway.
And then it didn't get past that.
And we have a little exclamation marks and ends implementing.
There was a problem, didn't make it.
So if we did a ping to 888, that's going to be no good as well.
So we'll do a control C there.
However, if we do a ping to our router up at 23.1.2.1, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
However, if we do a ping to our router up at 23.1.2.1,
and press enter, because it has routes back to us.
And we have a route to it.
We are able to do pings back and forth.
So so far, no internet access.
That's because we don't have correct NAT set up,
source NAT set up for this flow of traffic.
And so based on our plan, we are going to implement a NAT rule.
And we're going to do it on our gateway zero.
So to implement the NAT rules, we'll
go to networking here in NSX.
On the left, under network services, we'll click on NAT.
So for our NAT rules, here we have
options of where, first of all, do you want to have the NAT rules?
On which gateway?
So based on our plan, we want our NAT rules WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
So based on our plan, we want our NAT rules
to be on our tier zero gateway.
So with that selected first, then we'll
click right here on add NAT rule.
Let me collapse the left-hand side.
It gives a little more room.
And so for our NAT rule, our source NAT rule,
we want to match on traffic source, coming in from 10, 10,
zero, anything, and then swap it out with an IP address
from this pool right here.
And when we configure this NAT rule,
we have other options that we can specify.
We could also specify, for example,
that we only want the source NAT if the traffic is trying
to go to a certain destination and other considerations
or what porch are involved. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
or what porch are involved.
But for our plan, we just want any traffic source from 10, 10,
zero to be mapped to one of these IP addresses
in this range right here, as it goes through T0 on that initial
flow of traffic going out to the internet.
So I'm going to go ahead and call this 10.10,
SNAT.
And this little icon here is part of my password management
system, so it's not actually part of the NSX.
So there's the name for this new NAT rule,
and we want to use source NAT.
So if we want to do destination NAT,
which we will in the next video,
we choose that option right there.
Or if we had active edges, we'd go ahead and choose reflexive. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Or if we had active edges, we'd go ahead and choose reflexive.
Or if we want to set the specific rules to exempt
some traffic flows from NAT,
we'd go ahead and use the no options right here.
So now we want to do a source NAT rule.
And here it's asking us for the source IP.
So you don't have to put in a range or a specific source IP
address.
If you don't, it's going to consider any traffic based
on its routing tables that's going into the gateway.
It's going to consider that a valid candidate to be translated.
So in our lab environment, I want to go ahead and only
apply source NAT if the source is coming from the range 10.10.0.0. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
apply source NAT if the source is coming from the range 10.10.0.0.
And that's the 24-bit mask, meaning any IP addresses
that have the initial source address of 10.10.0,
they're going to qualify for NATting,
regardless of where they're going to.
So the internet's a big place.
I'm not going to make that conditional here.
And then what IP address or addresses
do we want to translate them into?
And that's right here, the translated IP in port.
So I'll go ahead for the IP address based on our plan.
It is 23.1.2.151 through 23.1.2.250.
Again, that's based on our plan. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
Again, that's based on our plan.
And then furthermore, we could also
do port address translation for that traffic.
And if we needed to or wanted to,
we could also specify the actual service, or AKA port,
that we want to use for that translation.
But in this case, I just want to do a layer three swap out
of the source address coming from 10.10.0 that are going
through the gateway based on the routing table.
And we're going to swap with that source address
with one of these addresses.
And everything else that layer four and above
with our one-to-one mapping will leave alone.
And as far as where we want to apply this to,
it's not required.
But if you want to granularly say, WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
But if you want to granularly say,
you know what?
I only want that applicable on this edge node or that edge node.
You could go ahead and somebody select the ones you want.
Or we could leave it blank and not set up a limit.
That way it's going to apply to both of the interfaces.
And then we'll scroll down and we'll click on Save.
And it says NAT rule 10.10 SNAT successfully.
So it successfully added our 10.10 source NAT rule.
If we expand it here, it'll show us the details.
Traffic from 10.10.0, as it's being routed through the gateway,
in this case, gateway zero, is going WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
in this case, gateway zero, is going
to be swapped out with a source address in this range.
So currently we have no active sessions, no packet counts,
no data.
And that's because we're not using that rule yet.