{
    "id": "559cce24-c029-449f-ade2-6c2fac6a6eeb",
    "name": "Address Conservation with NAT",
    "slug": "address-conservation-with-nat",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "48cff3d1-732c-4ce2-8169-6c7b0329fc34"
        ],
        "pta_sdn": "357",
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-08-29T16:05:52.196194Z",
    "modified": "2023-10-03T18:58:41.115199Z",
    "is_beta": false,
    "lab_objectives": [],
    "main_learning_area": "e73fd5a8-2ead-4159-9a25-38b50ad4ab20",
    "learning_areas": [
        {
            "id": "e73fd5a8-2ead-4159-9a25-38b50ad4ab20",
            "name": "Networking",
            "slug": "networking"
        }
    ],
    "categories": [],
    "tags": [],
    "difficulty": null,
    "is_web_access": false,
    "is_lab_experience": false,
    "is_featured": false,
    "cve": null,
    "severity": null,
    "year": null,
    "external_url": "",
    "solution_video": "565a3f9d-0fa8-4567-8772-99597daaa435",
    "explanation_video": null,
    "description": "![description](https://assets.ine.com/content/labs/networking-labs/Lab-4312/diagram.png)\n\n\n**Helpful Hints about INE\u2019s virtual lab environment:**\n\n- Most INE Networking Labs will timeout after 55-minutes (unless otherwise specified). If you haven't completed a lab within 45-minutes, save your configurations to an external text editor, restart the lab, and then paste in your saved configs to resume where you left off.\n- To access the CLI (command line interface) of any node, right-click that node and select the \"**console**\" option.\n- Save your configuration changes frequently in the event that you get locked out of a device or lose connectivity\n- If you are suddenly logged out of the GNS3 lab environment and log back in again, you may see the prompt, \u201cAnother GNS3 instance is running, continue? (Y/N)\u201d.  Select \u201cYes\u201d\n- If you ever lose console access to one (or more) of your devices you will need to reboot the Ubuntu Virtual Machine that is hosting your GNS3 lab environment.  To do this,\n    - Minimize your GNS3 window\n    - Open the \u201cTerminal\u201d app within the Ubuntu device\n\n    ![description](https://assets.ine.com/content/labs/networking-labs/Lab-4312/terminal.png)\n\n    - Type \u201creboot\u201d within the Terminal window\n    - Wait 20-30 seconds and then click the \u201cReconnect\u201d option to log back in.",
    "description_html": "<p><img alt=\"description\" src=\"https://assets.ine.com/content/labs/networking-labs/Lab-4312/diagram.png\" /></p>\n<p><strong>Helpful Hints about INE\u2019s virtual lab environment:</strong></p>\n<ul>\n<li>Most INE Networking Labs will timeout after 55-minutes (unless otherwise specified). If you haven't completed a lab within 45-minutes, save your configurations to an external text editor, restart the lab, and then paste in your saved configs to resume where you left off.</li>\n<li>To access the CLI (command line interface) of any node, right-click that node and select the \"<strong>console</strong>\" option.</li>\n<li>Save your configuration changes frequently in the event that you get locked out of a device or lose connectivity</li>\n<li>If you are suddenly logged out of the GNS3 lab environment and log back in again, you may see the prompt, \u201cAnother GNS3 instance is running, continue? (Y/N)\u201d.  Select \u201cYes\u201d</li>\n<li>\n<p>If you ever lose console access to one (or more) of your devices you will need to reboot the Ubuntu Virtual Machine that is hosting your GNS3 lab environment.  To do this,</p>\n<ul>\n<li>Minimize your GNS3 window</li>\n<li>Open the \u201cTerminal\u201d app within the Ubuntu device</li>\n</ul>\n<p><img alt=\"description\" src=\"https://assets.ine.com/content/labs/networking-labs/Lab-4312/terminal.png\" /></p>\n<ul>\n<li>Type \u201creboot\u201d within the Terminal window</li>\n<li>Wait 20-30 seconds and then click the \u201cReconnect\u201d option to log back in.</li>\n</ul>\n</li>\n</ul>",
    "tasks": "**Task: Address Conservation with NAT**\n\n***NOTE:*** The enable password on all IOS devices is \"**INE**\"\n\n\n1. Login to PC1, PC2 and PC4 and confirm that they can obtain IPv4 information via DHCP by issuing the command \"**ip dhcp -d**\":\n\n2. Verify that PC1 and PC2 can ping PC4.\n\n3. Right-click on the link connecting R3 to R4 and select the \"**Packet Capture**\" option. This should automatically start the Wireshark application. One again, ping from PC1 to PC4 and confirm that you can see those ICMP packets within Wireshark.\n\n    - **Helpful Hint**: Wireshark might show you a lot of stuff you aren't really interested in seeing (like OSPF Hello packets and CDP) that make it difficult finding the packets you DO want to see.\n    - You can filter out packets you're not interested in by:\n        - Selecting one of those packets (like an OSPF Hello)\n        - Selecting some field within that packet that makes it unique from other packets (like the OSPF multicast destination address, or the IP Protocol field of \"89\").\n        - After selecting that unique field, right click and select \"**Apply as Filter**\" followed by \"**Not Selected**\"\n        - If you want to filter out other types of packets repeat the same steps but select, \"**Apply as Filter**\" followed by \"**and not Selected**\"\n\n    ![description](https://assets.ine.com/content/labs/networking-labs/Lab-4312/wireshark-filters.png)\n\n4. Login to router R2 and disable (\"shutdown\") its link connecting to Switch-2. This will force all traffic from PC1 or PC2 going to PC4 to go through router R1.\n\n5. Preliminary Subnet-X configuration:\n\n    - Looking at your topology diagram, identify an unused subnet from the 180.50.0.x prefix that contains at least 6-host addresses. We'll called that \"**Subnet-X**\"\n    - On router R1, configure a Loopback-2 interface and address it with the first available host address from Subnet-X.\n    - On router R1, ensure that Subnet-X is advertised into your OSPF routing domain **and the OSPF network type is configured as \"point-to-point**\"\n    - From router R1 ping PC4 using Loopback-2 as your source address.\n\n    <pre><code>\n\n    R1#<b>ping 20.1.3.1 source loopback2</b>\n    Type escape sequence to abort.\n    Sending 5, 100-byte ICMP Echos to 20.1.3.1, timeout is 2 seconds:\n    Packet sent with a source address of xxx.xxx.xxx.xxx\n    !!!!!\n    <b>Success rate is 100 percent</b> (5/5), round-trip min/avg/max = 9/10/14 ms\n    R1#\n\n    </pre></code>\n\n6. Configure NAT on router R1 using the following criteria:\n\n    - Create a NAT pool called, \"INE\" that allocates addresses from Subnet-X\n    - NAT should translate any ICMP packets sourced from PC1 or PC2 destined to PC4.\n    - NAT should NOT translate if R1 pings PC4 **sourced from R1's Gig0/2 interface**.\n    - NAT should NOT translate if R2 pings PC4 **sourced from R2's Gig0/3 interface**.\n\n7. Using the \"Packet Capture\" tool as described above in Step-3, verify that NAT is correctly translating ping packets from PC1 or PC2 to PC4.\n\n8. Issue the command, \"**show ip nat translations**\" in R1 to view NAT translations.\n\n    - Why do you think each individual ping from from PC1 to PC4 (as an example) created is own unique translation entry?\n    - View the Wireshark entries for your pings to answer this question.\n\n9. Issue the command in R1, \"**show ip nat translations verbose**\". By default, what is the timeout value for a dynamic entry created by ICMP?",
    "tasks_html": "<p><strong>Task: Address Conservation with NAT</strong></p>\n<p><strong><em>NOTE:</em></strong> The enable password on all IOS devices is \"<strong>INE</strong>\"</p>\n<ol>\n<li>\n<p>Login to PC1, PC2 and PC4 and confirm that they can obtain IPv4 information via DHCP by issuing the command \"<strong>ip dhcp -d</strong>\":</p>\n</li>\n<li>\n<p>Verify that PC1 and PC2 can ping PC4.</p>\n</li>\n<li>\n<p>Right-click on the link connecting R3 to R4 and select the \"<strong>Packet Capture</strong>\" option. This should automatically start the Wireshark application. One again, ping from PC1 to PC4 and confirm that you can see those ICMP packets within Wireshark.</p>\n<ul>\n<li><strong>Helpful Hint</strong>: Wireshark might show you a lot of stuff you aren't really interested in seeing (like OSPF Hello packets and CDP) that make it difficult finding the packets you DO want to see.</li>\n<li>You can filter out packets you're not interested in by:<ul>\n<li>Selecting one of those packets (like an OSPF Hello)</li>\n<li>Selecting some field within that packet that makes it unique from other packets (like the OSPF multicast destination address, or the IP Protocol field of \"89\").</li>\n<li>After selecting that unique field, right click and select \"<strong>Apply as Filter</strong>\" followed by \"<strong>Not Selected</strong>\"</li>\n<li>If you want to filter out other types of packets repeat the same steps but select, \"<strong>Apply as Filter</strong>\" followed by \"<strong>and not Selected</strong>\"</li>\n</ul>\n</li>\n</ul>\n<p><img alt=\"description\" src=\"https://assets.ine.com/content/labs/networking-labs/Lab-4312/wireshark-filters.png\" /></p>\n</li>\n<li>\n<p>Login to router R2 and disable (\"shutdown\") its link connecting to Switch-2. This will force all traffic from PC1 or PC2 going to PC4 to go through router R1.</p>\n</li>\n<li>\n<p>Preliminary Subnet-X configuration:</p>\n<ul>\n<li>Looking at your topology diagram, identify an unused subnet from the 180.50.0.x prefix that contains at least 6-host addresses. We'll called that \"<strong>Subnet-X</strong>\"</li>\n<li>On router R1, configure a Loopback-2 interface and address it with the first available host address from Subnet-X.</li>\n<li>On router R1, ensure that Subnet-X is advertised into your OSPF routing domain <strong>and the OSPF network type is configured as \"point-to-point</strong>\"</li>\n<li>From router R1 ping PC4 using Loopback-2 as your source address.</li>\n</ul>\n<p><pre><code></p>\n<p>R1#<b>ping 20.1.3.1 source loopback2</b>\nType escape sequence to abort.\nSending 5, 100-byte ICMP Echos to 20.1.3.1, timeout is 2 seconds:\nPacket sent with a source address of xxx.xxx.xxx.xxx\n!!!!!\n<b>Success rate is 100 percent</b> (5/5), round-trip min/avg/max = 9/10/14 ms\nR1#</p>\n<p></pre></code></p>\n</li>\n<li>\n<p>Configure NAT on router R1 using the following criteria:</p>\n<ul>\n<li>Create a NAT pool called, \"INE\" that allocates addresses from Subnet-X</li>\n<li>NAT should translate any ICMP packets sourced from PC1 or PC2 destined to PC4.</li>\n<li>NAT should NOT translate if R1 pings PC4 <strong>sourced from R1's Gig0/2 interface</strong>.</li>\n<li>NAT should NOT translate if R2 pings PC4 <strong>sourced from R2's Gig0/3 interface</strong>.</li>\n</ul>\n</li>\n<li>\n<p>Using the \"Packet Capture\" tool as described above in Step-3, verify that NAT is correctly translating ping packets from PC1 or PC2 to PC4.</p>\n</li>\n<li>\n<p>Issue the command, \"<strong>show ip nat translations</strong>\" in R1 to view NAT translations.</p>\n<ul>\n<li>Why do you think each individual ping from from PC1 to PC4 (as an example) created is own unique translation entry?</li>\n<li>View the Wireshark entries for your pings to answer this question.</li>\n</ul>\n</li>\n<li>\n<p>Issue the command in R1, \"<strong>show ip nat translations verbose</strong>\". By default, what is the timeout value for a dynamic entry created by ICMP?</p>\n</li>\n</ol>",
    "published_date": "2022-09-16T21:23:58Z",
    "solutions": "***SOLUTIONS***\n\nView the Solution Video accompanying this lab for the lab solutions and walkthrough.",
    "solutions_html": "<p><strong><em>SOLUTIONS</em></strong></p>\n<p>View the Solution Video accompanying this lab for the lab solutions and walkthrough.</p>",
    "flags": [],
    "min_points_to_pass": null,
    "access_type": "default",
    "user_status": "unstarted",
    "user_lab_status": null,
    "user_status_modified": null,
    "user_flags": [],
    "global_running_session": null
}