6.8.2 Lab - Configure NAT for IPv4

hi friends welcome to world in this video we are going to solve this lab activity configure a nat for ipv4 before coming to it friends if you like to get any ccna support you can contact our team using our website link you will get from the description below and also if you like to get these type of technical videos in future consider subscribing and don't forget to enable that bell icon so that you will get notification message whenever we upload a new video okay now coming back to this activity here we can see the topology we will design this topology in a cisco packet tracer we have a two routers r1 r2 two switches s1 h2 and these are two pcs here we can see addressing table so in short we can say configure net for ipv4 we will go through the scenario network address translation that is nat is the process where a network device such as a cisco router ascends a public address to host devices inside a private network the main reason to use nat is to reduce the number of public ip addresses that an organization uses because the number of available ipv for public addresses is limited and isp has allocated the public iep address space of 209.165.200.224.29 to a company this network is used to address the link between the isp router that is r2 and the company gateway uh in r1 the first address that is a dot 225 is assigned to the g 0 0 0 interface on r2 and the last address that is the dot 230 is assigned to the g 0 0 0 interface on r1 so coming to our topology here we can see those interfaces g 0 0 0 in r 1 and g 0 0 0 in r2 the remaining addresses that means from 226 till 229 will be used to provide internet access to the company host a default route is used from r1 to r2 the internet is simulated by a loopback address on r1 in this lab we will configure various types of nat we will test view and verify that the translations are taking place and we will uh interpret the nat or path statistics to monitor the process and here they given the note about the routers and switches what we have to use okay we will go to the required resources we need two routers two switches then two pcs then cables like console or ethernet cables etc we will go through the instructions part one build the network and configure basic device settings in part one we will set up the network topology and configure basic settings on the pc host and switches okay step one cable the network as shown in the topology attach the devices as shown in the topology diagram and the cable as necessary so coming to our topology here we can see we will design this topology in this cisco packet traction we will add two routers let me choose 431 router just to press ctrl and click on this router so that we can add multiple routers here we need only two routers then click on switches 296 euro series then two computers we will rename these devices here is r2 this is r1 here we have s1 and this is s2 and here we have pc-a and this is pc-b we will connect these devices coming to connections we will choose copper straight through from r2 g 0 0 0 to r 1 g 0 0 0. then from r 1 g 0 0 1 to this s 1 f s 0 5 then we will connect these pieces to a switches f fa 0 6 to this pc dash a and here fs0 18 to this pc b now let me choose this copper crossover to connect these switches s1 and s2 fs01 fa 0 1 coming to step 2 configure basic settings for each router okay we have to assign the device name to the routers uh r1 and r2 also we have to disable dns lookup to prevent the router from attempting to translate incorrectly enter the commands as though they were host names first of all we will do it in r1 here we will give no enable conf t we will set the host name as r1 also we will give no ip domain lookup coming to r2 cli no enable county hostname r2 no iep domain lookup coming to the password settings as in class as the privileged exit encrypted password then we have to assign cisco as the console password and enable login and as in cisco as the vty password and enable login okay we will do these three passwords in each routers coming to r1 enable secret class coming to line console 0 password cisco login exit and go to line vty we'll go to 0 to 4 under set the password as cisco then login coming to r2 we will give enable secret class line console 0 password cisco login exit and go to line bty 024 set the password at cisco then login command these are all basic settings and we have done this many times in different lab activities so that's why i'm going little faster okay now we have to encrypt the plain text passwords and we have to create a banner that wants anyone accessing the device that unauthorized access is prohibited okay let me copy this text coming to r1 and here we will give a service password encryption service password encryption and we will set this banner motd then here is the message coming to r2 we will repeat in this r2 first of all we will give a service password dash encryption then banner motd here is the message next is configure interface ip addressing as specified in the table above coming to our trusting table we will configure these routers r1 and r2 with this ip address and test to mask first of all coming to r1 here we can see uh we have two interfaces g 0 0 0 which is connecting to r 2 and a g 0 0 1 which is connecting to this switch s1 so first of all we will configure this interface g 0 0 0 let me copy its ip address it's a public ip address and here we can see it's the center mask coming to r1 we will go to that interface that is g 0 0 underset the ip address with the mask and let me verify its 248 then activate it no shutdown next we will go to interface g 0 0 1 and we will get its ip address copy also we can see it's a sub to mask ip address and here is the mask activate this interface okay next we will go to this router r2 we have this physical interface g 0 0 0 and also we have this loopback interface one first of all we'll configure this interface let me copy this ip coming to r2 interface g 0 0 0 ip address it's here because we already copied it then to mask no shutdown exit and go to interface loopback 1 we will set the ip address and here we can see it's the center mask okay perfect next is configure a default route to r2 from r1 okay so we have to go to r1 and we will create this default static route towards r2 so let me get the ip address of this uh it's an x2 hope address the ip address of this interface g 0 0 0 in r2 we can get that from addressing table let me copy that coming to r1 exit and here we will give ip root zero dot zero dot zero dot zero space zero dot zero dot zero dot zero space then we can specify either exit interface or even we can specify a next hop ip address here we will give an x two of ip address already copied it okay save the running configuration to the startup configuration file okay we can do that exit copy run space start or even we can give right w r end copy run space start now coming to step three configure basic settings for each switch that means s1 and s2 assign a device name to the switch then disable dns lookup to prevent the router from attempting to translate incorrectly enter the commands as though they were host names we will do that coming to s1 cli enable confit set the hostname as s1 no ip domain lookup next we will go to s2 cli enable county hostname s2 no ip domain lookup next is a same class as the privileged encrypted password then assign cisco as the console and vty password then we have to enable login okay we will do that coming to s1 here we will give enable secret as class then we will go to line console 0 password cisco login exit and go to line vty 024 password cisco login coming to s2 enable secret as class line console 0 password cisco then login exit and go to line vty 024 password cisco login is encrypt the plain text passwords then create a banner that wants anyone accessing the device that an authorized access is prohibited okay we will give this message let me copy this text so coming to s1 service password dash encryption also we will set banner m or td here is the message coming to s2 service password encryption then we can set banner mrtd shut down all interfaces that will not be used in these switches okay here we can see in s1 we used three interfaces uh they are f fa05 0 6 and f s 0 slash 1 so other than these ports we will shut down we will go to interface as a range fa zero slash one already used so we will start from two till four then five and six already used face zero slash seven till twenty four and also we have a two gigabit ethernet interfaces g0 1-2 and we have to shut down all these parts shutdown perfect you can verify it end show ip interface brief yeah that's fine so we can see it's all these unused interfaces are administratively down now we will go to s2 and here we can see we used only two interfaces in this uh switch s2 that is fs 0 slash 1 and fs 0 18. you will go to interface as a range fs0 slash 2 because 1 we already used till 17 fs 0 19 till 24 also we got g 0 1 2 shutdown okay configure interface ip addressing as specified in that table above coming to our addressing table here we can see s1 and s2 we have to configure ip address to mask for this uh interface virtual interface vlan 1 okay no need to set any default gateway that's fine so first of all we'll go to s1 config we will go to interface vlan 1 then we will let's set the iep address let me copy its ip address and here we can see it's a certain to mask then activate this virtual lan now shutdown then we will go to s2 before that let me copy its ip address and to mask exit and go to interface vlan 1 set the iep address with the submit to mask activate it finally here save the running configuration to the startup configuration file okay we will do that that is very important end copy run space start coming to s2 and copy run space start now coming to party 2 configure and to verify nat for ipv4 in part two you will configure and verify nat for ipv4 step one configure nat on r1 using a pool of three addresses uh here they given those addresses from 226 till 2 28 that means 2 26 2 27 and 2 28 i mentioned only the last i mean the fourth octart okay don't confuse with that now configure a simple access list that defines what hosts are going to be allowed for translation in this case all devices on the r1 lan are eligible for translation so we are going to create this access list a standard access list permit 192.168.1.0 then it's a wild regard mask we will create this access list in this router r1 password cisco enable password class conft and here we will create that access list one and we are going to permit this network 192.168.1.0 and we have to specify it's a multi card mask 0.0.0.255 here we did not uh verify the connectivity right and even we did not set ip address for this pc dash a and pc dash b so let me set ip address for these two devices pc dash a disturb ipconfiguration okay no default gateway then coming to pc b we have to give a 1.3 i will change it to 1.3 now just we can attach to the connectivity now here i will choose this add symbol pdu option then from pc b to pc a here we can see it's successful then from pc dash b to r1 okay it's successful then from pc dash a2 r1 even we can test from r1 to r2 so let me try once more successful you will try from pc dash b to r2 so we can see it will fail we configure the default static route in this router r1 towards r2 but this r2 is unaware of this remote network that is the reason why we are able to ping from these ng devices to this router r2 now in configuring that create the net pool and give it a name and a range of addresses to use so in r1 we will create this iep nat pool with this full name public underscore access and then we have to give those three addresses they specified from my 226 till 228 then we have to specify the net mask in this router r1 we will create that nat pool here ipnat pool name they given public underscore access then we have to give the address 209 dot 165 dot 200 dot 226 space i will copy this ip address copy and paste and here we will change it to 228 then we have to give the net mask it's a 255.255.255.248 perfect press enter we will go through this note the net mask parameter is not an ip a truss delimiter it should be the correct mask for the addresses being ascend even if you are not using all the sub addresses in the pool okay configure the translation associating the acl and the pool to the translation process i p nat inside source list then we have to specify that standard acl number one what we created then pool then we have to specify the full name we will do that coming to r1 and here we will give that ip nat inside source list is one full then we have to specify the pool name just i can copy from here public underscore access and paste press enter again a note three very important points first the word inside is critical to the operation of this kind of nat if you omit it that will not work yeah that's fine second the listing number is the acl number configured in a previous step yes we already told here we can see that uh access list to be created with the number one then third the pool name is case sensitive so whatever name we given we created the same we have to give here also and they specified it it's a case sensitive define the inside interface interface g 0 0 1 which is connecting to s 1 then we have to define the outside interface also that is a g 0 0 0 which is pointing towards r2 we will do that coming to r1 uh first of all we will give a high p net inside interface is g 0 0 slash 1 which is connecting to uh switch s1 right and we have to give iep nat inside then we will go to interface you can exit and you can go to interface otherwise you can go from this mode itself interface g 0 0 0 which is connecting to r 2 here we have to give i p nat outside coming to step two test and verify the configuration from pc dash b ping the loopback one interface so here is the address let me copy that on r2 if the ping was unsuccessful troubleshoot and correct the issues on r1 display the nad table on r1 with the command show ipnat translations uh then we have to give his command right show iep net translations after uh pinging to this loopback interface one so we will go to this pc b command prompt and ping to loop back and we are waiting for the replies request timed out so we are not getting the reply so it's a request timed out so we have to troubleshoot it here we already uh configured these pcs pc dash a and pc dash b and here we can see we given only this ipv4 address and the mask we did not give the default gateway uh here we are communicating to the other network so we must give this a default gateway so let me verify in the addressing table g 0 0 1 here we can see that address let me copy it and we will set the default gateway here okay same way we will go to pc b pc dash b is also in the same network so here is the default gateway one nine two one six eight to one dot one again we will test the connectivity from pc dash b to this uh r2 loopback you go to command prompt press up arrow from the keyboard ping 201 165 200.1 and we will wait for the replies if still it's not working yeah it's working so no need to do any more troubleshooting that means we configured everything perfectly now we will give this show command to show ipnet translations so that we can see the translations here let me give a show ip nat translations so here we can see the translations they use this inside global 226 then we can see inside the local address the private ip address then we can see outside local and outside global what was the inside local address of pc-b translated to okay just now we have seen that here uh here we can see inside global that is a 209.165.200.226 so this is the uh you know translated public ip address what type of net address is that translated address it's uh inside the global right yeah we have seen that inside global inside the global inside local will show the uh you know private iphones from pc a ping the loopback interface 1 that is the ip address of the loopback okay just i will copy that on r2 if the ping was unsuccessful troubleshoot and correct the issues on r1 display the table on r1 with the command show ipnet translations so now we are going to ping from this pc dash a to this loopback one will go to pc dash a command prompt and let me ping to that loopback one and here we can see we get the replies now we will go to r1 and we will give that show command again show ipnet translations just we can press up arrow from the keyboard so that we will get the previous command we ended show ipnet translations then press enter okay now we can see inside local address changed here we can see inside the global address the same two zero nine one six five two zero zero to twenty six and also we can see the port number coming to this inside local we can see the iep address of pc-a then here we can see outside local and outside global notice that the previous translation for pc-bs are still in the table but it was not there uh anyways we will try once more from s1 ping the low back one interface okay on r2 if the ping was unsuccessful troubleshoot and correct the issues it will not ping because we did not set the default gateway in these switches okay we will do that then we will ping to the loop loopback one okay on r1 display the net table on r1 with the command show ipnet translations so before coming to this ping and this is a default gateway so let me maximize this there they told that both entries the net entries for pc dash a and pc dash b should be there in the router 1 right but we did not see that so just i will go to simulation mode here let me close this then from pc dash a let me go to command prompt uh press up arrow and press enter here we can see ping command then minimize it then let me go to pc b command prompt press up arrow so that we will get the previous command we entered we are going to ping to the loopback okay that's fine so we can see this uh packets here in pc dash a and pc dash b now just i am going to switch it to real time i want to test it okay so just i switched it to real time and now let me go to r1 and let me verify this show iep in a translations and here we can see more translations this is from pc dash b 1.2 this is from pc dash a correct i think so let me verify this yeah 2 is from pc dash a this is from pc dash a yeah that's perfect here we can see now this address is changed 226 here they used here they used 227 perfect now we can see all the entries next we have to ping from s1 to a loopback one interface before that we have to set the default gateway for these two switches so let me close this and i will copy this a default gateway coming to s1 cisco enable class confit ip default gateway i already copied it just paste and press enter i will copy this entire line copy coming to s2 password is cisco enable class conf t and we will paste that command and press enter so now we can ping from s1 to the loop back let me copy the ip address of a loop back then coming to s1 exit ping to the loopback and the success rate is 80 percent that's fine now we will give a show ipnat translations show ipnet translations you can press up arrow so that will get that previous command we entered but here we can see we got a only the ip address of this switch 1.11 so in the real time you may get all these addresses uh pc dash a pc b and there is a switch address in this net translations but here i can show that like a previous step we have to go to simulation then we have to go to pc a command prompt press up arrow then press enter go to pc b command prompt press up r1 press enter also we will go to s1 then give that a ping command press upper one press enter perfect then we will click on real time then we will go to r1 then give that a show ipnat translations so that we can see all the translations we can see this is from but still we get only pc dash b and switch okay that's fine oh here we can see one nine two one six eight to one dot two okay this is from pc dash a uh this is a pc uh pc dash b and uh switch that's fine now try and ping r2 a low back one from s2 also this time the translations fail and you get these messages or similar on the r1 console okay address location failed pool one may be exhausted because i'll be given only three addresses right okay that's fine okay we will try it again we will go to simulation mode and we will try it but before that let me ping from s2 and we will check it so i will copy this command coming to s2 then exit give that command and we are waiting for the reply yeah success is 80 percent so it's working right even we can go to r1 we can view these translations only from 12 we will try using simulation and i am not sure we will succeed with that but still we will have ping from pc dash a we will ping from pc dash b also will ping from s1 [Music] okay then coming to s2 just we will go to r1 and we will see any message is coming or not just i will keep side by side so here we will click on real time and we will see any message comes here so here we can see successful and here we will see so it's successful oh here we can see we got the request timed out in this pc-b okay that's fine but we did not receive any message show ipna translations we can see from 192.168.1.2 1.11 and 1.12 and we can see um this thing is failed the pc b this pc did not get any uh public iep address from the poor even we can test it without going to this simulation mode but uh we have to do little faster right uh we have to do in pc dash a then pc dash b then s1 then s2 so we can see pc dash a pc dash b and s1 will get the public ip address from the pool and s2 will not get the public ip address from the poor so this is 2 ping will fail so uh let me test that so i will try a little faster click here then go command prompt yeah click here and coming to these click here and here also we will try yeah so here we can see we are not getting the reply so it's failed in s2 because s2 is not getting the public ip address from the pool we created we given only three ip address uh maybe for starters taken for the pc dash a we can verify that using uh show command show ipnet translations sorry let me sorry we have to go to router right yeah perfect here we will give a show ipnet translations and here we can see this address one nine two one six eight two one dot two this is pc dash a uh see uh they're taken to 27 then the switch is taken to 26 that means the s1 is taken 226 pc dash a is taken to 227 then pc b is taken to 28 public ip address but no more public ip address available for ies 2. that's why that thing is failed success rate is zero percent even when you do in the real time you will get this message in the router so a trusted location failed a pool one may be exhausted yeah this is an expected result because only three addresses are allocated yes and we try to ping a loopback one uh from four devices recall that that is a one to one translation so how long are the translations allocated issue the command show iep net translations verbose and you will see that the answer is for 24 hours i don't think so this command is going to work in this packet tracer but still let me try that show ipnet translations we'll put a question mark and we cannot see this verbose command here we have only carriage return that means press enter it won't work workforce uh using the show iep net translations verbose we can see this timeout so it's 24 hours next is given that the pull is limited to three addresses not to a pool of addresses is not adequate for our application clear the net translations and statistics and we will move on to pat that is port address translation so we have to clear ipnet translations star also we have to clear ipnet statistics we will go to urban and here we will give that so let us clear ipnat let me put a question mark and here we have a translation i will copy and paste it then start then we have to clear ipnet statistics but here we cannot see this uh statistics let me put a question mark and we have only translation here okay in real mode we get this option statistics also now we will go to part three configure and to verify pat for ipv4 in part 3 we will configure replace nat with the path to a pool of addresses and then with the pad using an interface so here we are going to configure this support address translations for ipv4 step 1 remove the translation command on r1 the components of an address translation configuration are basically the same something an access list to identify addresses eligible to be translated and optionally configured pool of addresses to translate them to and the commands necessary to identify the inside and outside interfaces from part one our access list that is access list one what we created is still correct for the network scenario so there is no need to recreate it we are going to use the same pool of addresses so there is no need to recreate that configuration either also the inside and outside interfaces are not changing that's correct this interface g 0 0 slash one is not an ipin at inside and this interface g 0 0 0 is ip nat outside to get started in part 3 remove the command that ties the acl and pull together so here we are going to remove this uh iep net inside the source list one pull public underscore access okay we will remove that nat country and here we will give a no ip nat inside source list one police public underscore access step 2 add the pat command on r1 now configure for pat translation to a pool of addresses remember the acl and pool are already configured yes so this is the only command we need to change from nat to pat so here we can see that command ip nat inside source list 1 pool public underscore access we have to give overload we will create that coming to r1 and here we will give this ip nat inside source list 1 4 so we can copy this then we have to give overload let me put a question mark and here we can see overload then press enter coming to step three test and verify the configuration let's verify path is working from pc dash b bring the loop back one interface here we can see its ip address i will copy that on r2 if the ping was unsuccessful troubleshoot and correct the issues on r1 display the net table on r1 with the command show ipnat translations we copy the ip address of value back one we will go to pc b command prompt desktop command prompt and here we will bring to that loop back and make sure that you get the replies so here we are waiting for the replies and here we can see we get the replies even once more we can try it okay now we will give this a show ipnet translations command coming to r1 okay here we will give that command show ipnet translations and here we can see the details inside global inside the local and here we can see the port number used with this address 226 here is the private ip address also we can see outside local and outside global what was the inside local address of pc-b translated to okay we will verify that already we have seen that here inside global here we can see the address 209.165.200.226 what type of net address is the translated address yeah it's inside global here we can see that inside global what is different about the output of the show iep net translations command from the nat exercise okay there is no dedicated translation between an inside and outside address are listed from pc dash a ping the loopback one interface on r2 if the ping was unsuccessful troubleshoot and correct the issues on r1 display the net table on r1 with the command show ip nat translations okay we are going to ping from pc a to this low back interface ping to the loop back and here we can see we get the replies then now we will give this a show iep net translation command again we can press up arrow from the keyboard show ipnet translation and here we can see now the inside local address changed from pc dash b to pc dash a here we can see the ip address of pc a 192.168.1.2 previously it was 192.168.1.3 notice that there is only one translation again send the ping once more and quickly go back to the router and issue the command show ipnet translations verbose and you will see what happened anyways here in this packet tracer it's not going to get the output for the show command show iep net translations verbose as you can see the translation timeout has been dropped from 24 hours to one minute generate traffic from multiple devices to observe port address translation on pc dash a and the pc dash b use the dash d parameter with the ping command to send a non-stop ping to r2's loopback one interface so we have to give this command ping space and dash d dash t then the iphone so for a loopback one just i will copy this command then go back to r1 and issue the show ipnet translations command notice that the incident global address is the same for both sessions yes so we will go to pc dash a and here we will give that command ping dash t then the iphones then coming to pc dash b here also we will give that ping command then we will go to r1 show ipnet translation and here we can see that they use this same inside global address and we can see only this port number is changing again we can test it here we can see for both pcs they use this same public ip address 209 165 226 1.3 here we can see 1.2 same public ip address but we can see the port number is changing here yeah how does the router keep track of what replies go where so here we can see they use this uh you know unique port numbers for each thing pad to a pool is a a very effective solution for small to medium sized organizations however there are unused ipv4 addresses involved in this scenario we will move to pat with interface overload to eliminate uh this waste of ipv4 addresses stop the pings on pc dash a and pc b with the control c key combination then clear translations and translation statistics coming to pc c you can press ctrl c okay then coming to pc b control c will go to r1 and here we will give that command clear ipnet translation start step four on r1 remove the net pull translation commands once again our access list that is success to one is still correct for the network scenario so there is no need to recreate it also the inside and outside interfaces are not changing to get started with the path to an interface clean up the configuration by removing the path pool and the command that ties the acl and pull together we have coming to r1 here we will give that no ip nat inside source list one who is a public underscore access overload so here yeah we are in a privileged exit mode we have to go to global configuration mode conf t and here we will give that command we'll give again or just i can copy and paste it press enter yeah also we have to give an oip net pool public underscore access add the patch overload command by specifying the outside interface at the path command that will cause overload to the outside interface uh using g 0 0 0 right which is connecting to this router r2 we have to give this command ip nat inside source list 1 interface that is g 0 0 0 overload we will give that command here ipnet source list one interface is g zero slash zero slash 0 overload so here i forgot to give ipnet inside right i p nat inside source list 1 interface is g 0 0 0 let me put a question mark and we have this command overload now it's perfect coming to step six test and verify the configuration let's verify pat to the interface is working from pc b ping the loop back one interface on r2 if the ping was unsuccessful troubleshoot and correct the issues one r1 display the net table on r1 with the command show ipnet translations we will go to pc-b and we will ping to loop back one coming to r1 exit show ipnet translation here we can see the change in inside global here we can see the iep address of that interface g 0 0 0. okay now generate traffic from multiple devices to observe pat on pc dash a and pc b use the dash t parameter with the ping command to send a non-stop ping to r2's loop by command interface okay previously we have done that on s1 and s2 issue the privileged exec command ping uh 209.165.20.1 um repeat 2 0 0 0 then go back to r1 and issue the show ipni translations command we have to do many things first of all we will go to pc dash a command prompt and already we use this command ping space dash t then ip address ip address of our loop back one then coming to pc b and here also we have that command press enter now we will give this command in switches s1 and s2 coming to s1 cli password enable password is class then we have to give a repeat we'll put a question mark and here we don't have that option repeat we only press enter okay okay just we will give only this ping here then coming 2s2 cli here also we'll give that then coming to r1 show ipnet translation and here we can see the details so here we can see that address inside global inside local here itself they given the sample output total number of translations for now all the inside global addresses are mapped to uh the g zero slash zero slash zero interface iep address yes here we can see that stop all the things on pc dash a and pc dash b using the control dash c key combination press ctrl c coming to pc b press control c now coming to part to four configure and to verify uh static net for ipv4 in part four we will configure static nat so that pc dash a is directly reachable from the internet pc dash a will be reachable from r2 via the address 209.165.200.229 they given a node the configuration you are about to complete it does not follow recommended practices for internet connected gateways this lab completely omits what would be standard security practices to focus on successful configuration of static match in a production environment careful coordination between the network infrastructure and the security teams would be a fundamental to supporting this equipment yes this is very important step one on r1 clear current translations and statistics coming to r1 and we will clear that player ip net translation you have to give star at the end space star step 2 on r1 configure the net command or k2 statically map and insert address to an outside address for this step configure a static mapping between 192.168.1.11 and 209.165.200.1 using the following command ip nat inside source static here we can see the address and we are mapping between i mean with this public ip address i will copy this command ip nat then coming to r1 we'll paste here or we can type it in the global configuration mode configure terminal and paste here ipnet inside source static then the address step 3 test and verify the configuration let's verify the static net is working on r1 display the net table on r1 with the command show ipnet translations and you should see the static mapping okay we will try that coming to r1 exit and we will give that command show command to show ipnet translation and here we can see that inside global then inside local the translation table shows the static translation is in effect verify this by pinging from r2 to 209.165.200.229 the pings should work okay we will go to r2 and we will ping to this address ping to the given address and here we can see success rate is hundred percent note you may have to disable the pc firewall for the pings to work anyways here no need to worry about the firewall on r1 display the net table on r1 with the command show ipnet translations and you should see the static mapping and the port level translation for the inbound things okay we will give that show command show ipnet translation and let me give you once more here and here we can see the details inside global and here is inside local outside local and outside global and this validates that the static net is working perfect that's all in this lab activity configure net for ipv4 now dear friends if you have any doubt any suggestions regarding this privatizer activity please comment below or even you can contact our team using our website link you will get from the description below and if you like your video give a thumb and share with all your friends and if you don't like we expect some suggestions for improvement stay tuned and we will meet again with the next video thank you

Channel: Tech Acad

Views: 5,306

Keywords: CISCO, CISCO Router, NAT, Packet Tracer, CCNA, IPv4, Network Address Translations, CCNAv7, Networking, CISCO Certification, Routing and Switching

Id: TOJ-oksqR-M

Length: 65min 44sec (3944 seconds)

Published: Mon Nov 23 2020