Hello and welcome. My name is Keith Barker. And most of the time in our
internal networks,
we're going to be running private IP address spaces, stuff like the 10 network
or 1.72,
16 through 31 or 192.168. Anything. And if we are, that's great. However,
those clients are not going to be able to get out to the internet because when
internet service
providers see those source IP addresses, they're going to say, "Ain't sorry,
you shall not pass."
Or if we have somebody trying to send a packet to a destination, that's a
private RFC-19.8
address. Once again, the service provider network is going to say, "No, but we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
address. Once again, the service provider network is going to say, "No, but we
don't have any clue
where exactly that lives and it's going to go ahead and drop it." So how do we
solve that? The
answer is we lie. We take IP addresses, whether source or destination, and we
modify them so that
we replace them with the appropriate IP address. When we swap out the source IP
address on the
initial flow of traffic, it's called source NAT. If we're swapping out on the
initial flow of
traffic, the destination address is called destination NAT. So here's what you
and I get to do in these WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000
and I get to do in these
videos. We're going to take a look at the basic concepts of NAT, including some
of that terminology
to make sure we're clear why we would use one type of NAT over another, and
then we'll put a game
plan together for the implementation of address translation. And then third, we
'll actually configure
and verify address translation, both source and destination address translation
. So if you're
ready. I'm ready. I'll see you in the very next video.