Greetings, and welcome to Seeseenayy.
Packet Tracer Details: This packet tracer asks us to configure Dynamic NAT with PAT, implement Static NAT, and verify implementation of both.
Below you will find a download of the completed packet tracer file. It is recommended that you read the tutorial or so.
R2>en
R2#conf t
Now, we're going to have to make an ACL for the NAT to configure throughput for NAT translations.
On R2, configure a standard ACL named R2NAT that uses three statements to permit, in order, the following private address spaces: 192.168.10.0/24, 192.168.20.0/24, and 192.168.30.0/24.
R2(config)#ip access-list standard R2NAT
R2(config-std-nacl)#permit 192.168.10.0 0.0.0.255
R2(config-std-nacl)#permit 192.168.20.0 0.0.0.255
R2(config-std-nacl)#permit 192.168.30.0 0.0.0.255
R2(config-std-nacl)#exit
Configure R2 with a NAT pool named R2POOL that uses the first three addresses in the 209.165.202.128/30 address space. The fourth address is used for static NAT later in Part 2.
R2(config)#ip nat pool R2POOL 209.165.202.128 209.165.202.130 netmask 255.255.255.252
R2(config)#ip nat inside source list R2NAT pool R2POOL overload
Configure R2 interfaces with the appropriate inside and outside NAT commands.
R2(config)#int f0/0
R2(config-if)#ip nat inside
R2(config-if)#int s0/1/0
R2(config-if)#ip nat outside
R2(config-if)#int s0/0/0
R2(config-if)#ip nat inside
R2(config-if)#int s0/0/1
R2(config-if)#ip nat inside
R2(config-if)#ex
Refer to the Topology. Create a static NAT translation to map the local.pka inside address to its outside address.
R2(config)#ip nat inside source static 192.168.20.254 209.165.202.131
Packet Tracer Details: This packet tracer asks us to configure Dynamic NAT with PAT, implement Static NAT, and verify implementation of both.
Below you will find a download of the completed packet tracer file. It is recommended that you read the tutorial or so.
Download(s)
Alternatively, you may use the commands from the tutorial to complete this PT.
Tutorial / Walk-through
Start off with your basic commands to enter configuration mode, etc.
R2#conf t
Now, we're going to have to make an ACL for the NAT to configure throughput for NAT translations.
On R2, configure a standard ACL named R2NAT that uses three statements to permit, in order, the following private address spaces: 192.168.10.0/24, 192.168.20.0/24, and 192.168.30.0/24.
R2(config)#ip access-list standard R2NAT
R2(config-std-nacl)#permit 192.168.10.0 0.0.0.255
R2(config-std-nacl)#permit 192.168.20.0 0.0.0.255
R2(config-std-nacl)#permit 192.168.30.0 0.0.0.255
R2(config-std-nacl)#exit
Configure R2 with a NAT pool named R2POOL that uses the first three addresses in the 209.165.202.128/30 address space. The fourth address is used for static NAT later in Part 2.
R2(config)#ip nat pool R2POOL 209.165.202.128 209.165.202.130 netmask 255.255.255.252
R2(config)#ip nat inside source list R2NAT pool R2POOL overload
Configure R2 interfaces with the appropriate inside and outside NAT commands.
R2(config)#int f0/0
R2(config-if)#ip nat inside
R2(config-if)#int s0/1/0
R2(config-if)#ip nat outside
R2(config-if)#int s0/0/0
R2(config-if)#ip nat inside
R2(config-if)#int s0/0/1
R2(config-if)#ip nat inside
R2(config-if)#ex
Refer to the Topology. Create a static NAT translation to map the local.pka inside address to its outside address.
R2(config)#ip nat inside source static 192.168.20.254 209.165.202.131
At this point you should be complete with the packet tracer. If you missed something, check your answers. You may have incorrectly configured an address for the ACL.
0 comments:
Post a Comment