• Overview
• Objectives
• Completing the lab
  • Hardware
  • Part 01 - Configuring the end devices
  • Part 02 - Setting up PAT on CC Border Router
  • Part 03 - Configuring Static NAT
• Deliverables

In this lab, we used Champlain and the CNCS labs as an example for implementing NAT within a Packet Tracer environment.

• Configuring all endpoints using a provided subnet information table.
• Configuring PAT on a border router
• Configuring static NAT on a border router

• 4x PC-PTs
• 3x Server PTs
• 3x 2960-24TT switches
• 1x Switch-PT-Empty
• 3x 2911 Routers
• 2x 2811 Routers
• 13x Copper straight-through cables
• 1x Copper cross-over cable

To start this lab I had to configure each end device with an IP address, subnet mask, and default gateway. I did this by making use of the provided subnet info:

After ensuring that all of this was configured, I moved on to setting up port address translation on the CC Border Router so that the Foster and Skiff end devices would be able to communicate with the Burlington Telecom Server.

To set up PAT on the CC Border Router, I ran the following commands:

# Elevate and enter the configuration terminal
enable
configuration terminal

# Permit the Foster network (192.168.3.0/24)
access-list 1 permit 192.168.3.0 0.0.0.255

# Permit the Skiff network (192.168.1.0/24)
access-list 1 permit 192.168.1.0 0.0.0.255

# Define FastEthernet0/0 (192.168.100.1) as the inside interface
interface FastEthernet0/0
ip nat inside

# Define FastEthernet0/1 (219.93.144.1) as the outside interface
interface FastEthernet0/1
ip nat outside

# Configure NAT overload (PAT) using the public IP on FastEthernet0/1
ip nat inside source list 1 interface FastEthernet0/1 overload

With my port address translation set up, I ensured that it was working. I did this by first pinging the Burlington Telecom Server from the Skiff and Foster PCs.

I then moved on to setting up a static NAT so that PCs would be able to communicate with the public web server on the Ireland network.

For this next part, I needed to set up a static NAT to map the private IP of the Ireland Pub Web Server to a public IP. I did this by running the following command:

# Static NAT mapping: Map private IP 192.168.7.2 to public IP 219.93.144.2
ip nat inside source static 192.168.7.2 219.93.144.2

I then tested this by pinging the public web server from the Foster and Skiff PCs.

Finally, I ran the following command to view the NAT mappings:

# Show NAT translations
show ip nat translations

My submission can be found at this link here. The packet tracer file was the only deliverable required for this lab.