Lab 8 1 NAT in Packet Tracer (Extra Credit) - jude-lindale/Wiki GitHub Wiki

Summary

In this lab we were tasked with observing a Layer 3 Header change as a packet crosses a NAT router and to Configure Cisco router for IP masquerading using PAT. First we had to go to the CLI tap on the cyber.local router and then write "enable" and then "config t" allowing for the following commands to be able to be run. then we had to create an Address Pool called "champ" for the Public IP addresses that 192.168 clients can use, to do that we had to type in "ip nat pool champ 216.93.144.10 216.93.144.10 netmask 255.255.255.0" which created that address pool. Then we had to create an access-list by typing "access-list 1 permit 192.168.0.0 0.0.255.255". Then we had to assign the pool and access rule to interfaces with a nat statement that translated to "that access-list 1 (192.168 addresses) can be translated to the PAT IP' from pool "champ" when going from the "inside" interfaces (Skiff and Foster) to "outside" interfaces (Internet)." to do so we had to write "ip nat inside source list 1 pool champ overload". Once that was done we had to exit that mode we were in by typing "exit if at Router(config)#". lastly we then put in the "sh ip nat translations" command to ouput a NAT Table and how TCP ports are used to track connections for the different Skiff and Foster Clients all using the same 216.93.144.10 address.

Commands

• sh ip nat translations: outputs NAT Table and how TCP ports are used to track connections for the different Clients all using the same address

• ip nat inside source list 1 pool champ overload: Overload states that the IP can be used by many (up to 64,000) clients.