Hi, this is your host Habib. And we are moving on to our second lab, which is provisioning dynamic Nat. And it's also known as Nat pool. So let's say you're in an organization, as I said, or a manufacturing facility. And they have a lot of these terminals that need to be accessible to an outside company. That company gets its internet access to an ISP, similar to this type of environment.
And they need to access these terminals. So let's say you have more than one more than more than 10. I'm not sure maybe even 50 of these terminals. Basically, in that case, as a network engineer, what you need to do is create That pool. So as I mentioned, we have block of public IP addresses available to us. As you know, dot one is used for the interface for the outside world dot two is connected to the outside world to the ISP interface and then we are left with another four IP addresses that are available for us to use for our terminals.
So most of the work will be done in r1 because that's our, that's our router that's facing the internet. And the other thing that we will learn in this lab is how to create a pool and associate that pool with a with an access list. This is a very important skill that I'd like you to basically match And it will definitely help you down the road and you will be able to use the Cisco anytime. So what I did is that this is a continuation of the previous lab. So what I did is I cleared the the static Nat configuration from r1. And so let's talk I would bring the r1 configuration in front of us here.
And if I do show running config, I increase it here. You can see I only have defined the interfaces as the IP net outside and IP Nat inside similar to my previous lab and then there's a router rip protocol running And that's it. We haven't done anything else. Right. So I just wanted to start again from scratch. And and let's look at the topology here.
So it so it's clear for us. So first thing first what we will do is we know that from our network design we have four available IP addresses, right? So yeah, four available IP addresses. So let's configure that first. So IP Nat pool, as I said, we will create a pool and the pool name is going to be CCS. And I will give it the range, which is 100 dot 20 dot 190 dot three is the isn't the IP address.
That's available And the last IP that's available in our public range is six. And then I'll type netmask 25522552255 dot 248. That's our subnet mask for that range of the IP addresses. As you can see, it's slash 29 from our design. Now we will create IP Nat inside source list or called the list one, pool, CCS and now we will create the access lists. access list one permit And I want to permit 192 168 dot one dot 10.
That's the host IP address of my terminal here. And I don't need to put any wild mask. Here it was no. So let's say you have more than one terminal, then you will continue this access list by typing access list one permit 192 168 dot one dot 11 dot 12, or whatever your internal IP address is going to be. It doesn't matter. Let me save the configuration.
That's perfect. Now the only thing I need to make sure is can we ping this terminal from this remote user? That's the requirement in the task three. So let's bring the remote user terminal. Sometimes when you apply the NAT configuration, it depends on your routers capability, how fast it is, and how quickly it can, it can take that configuration. So, let me ping on hundred dot 20 dot 193.
As I said maybe it's not taking the configuration of the net pool quickly. Let's hold on for a few seconds for more and then let's come back to it. Alright, as you can see, we're back Back here and we gave it a little bit of time to see why it was not thinking dot 320 dot 190 dot three. And eventually it started pinging. I mean it should work right away in the real world. But because we are using these simulations, sometimes the image file is is not ready to take on the NAT protocol.
Actually, sometimes you may get even an error message saying that, that the ram may be small. So, but anyway, I didn't get this message. But just letting you know if you're going to do this lab in your own environment, make sure that you give the router at least 256 meg configuration for the ram so so it is pinging successfully and me now as I'm pinging, I want to show you that the translations are happening on the router. The message is coming from, from the remote user and it's trying to reach the terminal one and I could see the translations happening on the router as you can see. So with this, we have concluded the dinette pool lab. I hope you have enjoyed this lab.
It's very short. It's similar to the previous test Net one but this one is more practical as well because it does cover some real scenario and hopefully you can use it whenever you have a chance, thank you again and we will move on to the net of a load and from there on once we start the NAT overload First we will discuss the design of the How to provide Internet access to two offices and different designs of the internet. All right, thank you very much.