Refer to the following output:
R2# show ip nat translations
Pro Inside global Inside local Outside local
tcp 209.165.200.225:16642 192.168.10.10:16642 209.165.200.254:80
tcp 209.165.200.225:62452 192.168.11.10:62452 209.165.200.254:80
Outside global
209.165.200.254:80
209.165.200.254:80
R2# show ip nat translations verbose
Pro Inside global Inside local Outside local
tcp 209.165.200.225:16642 192.168.10.10:16642 209.165.200.254:80
Outside global
209.165.200.254:80
create 00:01:45, use 00:01:43 timeout:86400000, left 23:58:16, Map-Id(In): 1,
flags:
extended, use_count: 0, entry-id: 4, lc_entries: 0
tcp 209.165.200.225:62452 192.168.11.10:62452 209.165.200.254:80
209.165.200.254:80
create 00:00:37, use 00:00:35 timeout:86400000, left 23:59:24, Map-Id(In): 1,
flags:
extended, use_count: 0, entry-id: 5, lc_entries: 0
R2#Router R2 has been configured to provide NAT services. On the basis of the information provided, comment on the NAT translations in the output.
Router R2 was configured to provide NAT overload translation to hosts on the 192.168.10.0 and 192.168.11.0 networks.
The host with the inside local IP address 192.168.10.10 was translated into the overloaded inside global IP address 209.165.200.225 using the unique port number 16642 when accessing the web server located at 209.165.200.254.
The host with the inside local IP address 192.168.11.10 was translated into the overloaded inside global IP address 209.165.200.225 using the unique port number 62452 when accessing the web server located at 209.165.200.254.
Related exam: EWAN v4 Chapter 7 Check Your Understanding: IP Addressing Services
