Week013 Lab10
Week013 Lab10
Follow the task and steps given. Don’t forget to answer step 13. This Laboratory Exercise is 10pts .
We have now simple topology consisting of three routers. R3 will simply be used as a host on our “internal”
network and R2 will be used as our border router (the serial connection between R1 and R2 will represent our
connection to the Internet):
The goal is to NAT any traffic originating on our internal network (R3) as it leaves the serial 0/0 interface on
R2 on it’s way to the “Internet” (R1). Overloading (having multiple clients all NAT’d to the same IP address) is
probably the most common implementation (especially for those of us who run NAT on a Cisco box at home!).
NETWORK DIAGRAM:
Course Code IT212
Instructions:
Step 1: If you will use a live lab with all the cisco devices in place and connected to each other as
shown at the topology diagram above . Establish a HyperTerminal session to the devices.
Nevertheless, you can also use a Cisco Packet Tracer Simulation software to do this Lab. Take
note also the cable you will use broken line or dash means cross cable.
Use:
Router#configure terminal
Router(config)#
Example:
Router(config)#hostname R1
R1(config)#
Router(config)#hostname R2
R2(config)#
Router(config)#hostname R3
R3(config)#
Example:
R1(config)#no ip domain-lookup
R1(config)#
Configure the EXEC mode password using the enable secret password command. Use class for
thepassword.
Example:
R1(config)#
Example:
R1(config)#banner motd&
********************************
********************************
&
R1(config)#
Use cisco as the password. When you are finished, exit from line configuration mode.
Example:
R1(config)#line console 0
R1(config-line)#password cisco
R1(config-line)#login
R1(config-line)#exit
R1(config)#
Step 8: Do this in all routers. Configure the password for the virtual terminal lines.
Use cisco as the password. When you are finished, exit from line configuration mode.
Example:
R1(config)#line vty 0 4
R1(config-line)#password cisco
R1(config-line)#exec-timeout 0 0
R1(config-line)#logging syncronous
R1(config-line)#login
R1(config-line)#exit
R1(config)#
Step 8: Configure router fa0/0 and s0/0/0 with the ip address assigned. Don’t forget to enable
the ports configured using “no shutdown” command. Take note also the cable you will use
broken line or dash means cross cable.
Step 9: Do “show ipint brief” in R2. This confirms all interfaces and connections are up.
R2#
Now we can start with configuring NAT. First, let’s define our NAT inside and NAT outside interfaces (fastethernet 0/1 and
serial 0/0, respectively).
Next, we need to create an access-list to match the “internal” IP addresses (the ones we want to be NAT’d). In this case,
our internal network is 192.168.50.0/24. Our ACL to match that network is simple:
Last, we’ll use the “ipnat …” command to actually instruct the router on what we want to NAT:
This tells IOS that any packets coming in the “inside” interface (fastethernet 0/0) that are permitted by the
named access-list “NAT” will have their “source” address translated to the IP address assigned to “interface
serial 0/0/0″. In addition, NAT translations will be overloaded — that allows multiple devices inside to be
translated to the same IP address.
R3#ping 192.168.10.1
R3#
R1#
ICMP: echo reply sent, src 192.168.10.1, dst 192.168.10.2
R2#debug ipnat
IP NAT debugging is on
R2#
R3#ping 192.168.10.1
R3#
Observe R2 …
R2#
NAT: s=192.168.50.2->192.168.10.2, d=192.168.10.1 [684]
R3#