Lab Assignment 5
Network Address Translation (NAT) in Cisco Packet
Tracer
September 9, 2025
Prepared by: Dheeraj Kumar
1 Objective
• Understand NAT (Network Address Translation) and PAT (Port Address Transla-
tion).
• Configure NAT on a Cisco router in Packet Tracer.
• Verify connectivity between LAN hosts and a public server.
2 Topology
The network topology used for this lab consists of two PCs in the LAN, connected via
a switch to a router (Router1). Router1 connects to another router (Router2), which
connects to a server on the public side.
Figure 1: Packet Tracer topology for NAT configuration
3 IP Addressing Table
4 Router Configuration
1 Router > enable
2 Router # configure terminal
1
Device Interface IP Address
PC0 NIC [Link] /24, GW [Link]
PC1 NIC [Link] /24, GW [Link]
Router1 Fa0/0 [Link] /24 (NAT inside)
Router1 S0/0/0 [Link] /24 (NAT outside)
Router2 S0/0/0 [Link] /24
Server0 NIC [Link] /24, GW [Link]
Table 1: IP addressing scheme for the network
3 ! - - Inside LAN interface
4 Router ( config ) # interface fastEthernet0 /0
5 Router ( config - if ) # ip address [Link] [Link]
6 Router ( config - if ) # no shutdown
7 Router ( config - if ) # ip nat inside
8 Router ( config - if ) # exit
9 ! - - Outside WAN interface
10 Router ( config ) # interface serial0 /0/0
11 Router ( config - if ) # ip address [Link] [Link]
12 Router ( config - if ) # no shutdown
13 Router ( config - if ) # ip nat outside
14 Router ( config - if ) # exit
15 ! - - Access list to match LAN subnet
16 Router ( config ) # access - list 1 permit [Link] [Link]
17 ! - - NAT overload ( PAT ) using WAN IP
18 Router ( config ) # ip nat inside source list 1 interface serial0 /0/0
overload
19 Router ( config ) # end
20 Router # write memory
Listing 1: Router1 NAT configuration
5 Verification
5.1 Ping from PC0 to Server
1 PC > ping [Link]
2 Pinging [Link] with 32 bytes of data :
3 Reply from [Link]: bytes =32 time <10 ms TTL =255
4 Reply from [Link]: bytes =32 time <10 ms TTL =255
5 Reply from [Link]: bytes =32 time <10 ms TTL =255
6 Reply from [Link]: bytes =32 time <10 ms TTL =255
7 Ping statistics for [Link]:
8 Packets : Sent = 4 , Received = 4 , Lost = 0 (0% loss )
Listing 2: Ping result from PC0 ([Link]) to Server0 ([Link])
5.2 Ping from PC1 to Server
2
1 PC > ping [Link]
2 Pinging [Link] with 32 bytes of data :
3 Reply from [Link]: bytes =32 time <10 ms TTL =255
4 Reply from [Link]: bytes =32 time <10 ms TTL =255
5 Reply from [Link]: bytes =32 time <10 ms TTL =255
6 Reply from [Link]: bytes =32 time <10 ms TTL =255
7 Ping statistics for [Link]:
8 Packets : Sent = 4 , Received = 4 , Lost = 0 (0% loss )
Listing 3: Ping result from PC1 ([Link]) to Server0 ([Link])
5.3 NAT Translations on Router1
1 Router # show ip nat translations
2 Pro Inside global Inside local Outside local Outside
global
3 icmp [Link]:3 [Link]:3 [Link]:3
[Link]:3
4 icmp [Link]:4 [Link]:4 [Link]:4
[Link]:4
Listing 4: Output of ”show ip nat translations”
5.4 NAT Statistics
1 Router # show ip nat statistics
2 Total active translations : 2 (0 static , 2 dynamic ; 2 extended )
3 Outside interfaces : Serial0 /0/0
4 Inside interfaces : FastEthernet0 /0
5 Hits : 20 Misses : 0
6 Expired translations : 0
Listing 5: Output of ”show ip nat statistics”
6 Conclusion
• NAT (PAT overload) was configured successfully on Router1.
• Private IPs ([Link] and [Link]) were translated to Router1’s public IP
([Link]).
• Both PCs could ping the external server ([Link]) successfully.
• NAT translation and statistics confirmed correct operation.
