{
    "id": "22ca5cac-0fa5-40ef-b3f8-60c046fc98ed",
    "name": "Security with Standard Access Lists",
    "slug": "security-with-standard-access-lists",
    "status": "published",
    "lab_type": "pta",
    "is_sample": false,
    "duration_in_seconds": 1800,
    "metadata": {
        "courses": [
            "efd8a55d-28c5-4fcd-8b42-cfdafb1f085f",
            "4e6a6dc7-e791-4a8e-a598-2acfd5d458c7",
            "48cff3d1-732c-4ce2-8169-6c7b0329fc34"
        ],
        "pta_sdn": "357",
        "collections": [],
        "pta_namespace": "my.ine",
        "learning_paths": [],
        "has_published_parent": true
    },
    "session": null,
    "company": "a491bc32-c056-4946-9169-cc053387bada",
    "created": "2022-08-29T16:02:58.225552Z",
    "modified": "2024-05-08T14:11:21.087024Z",
    "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": "5096db22-96a7-4e6d-b677-889bd9facb9d",
    "explanation_video": null,
    "description": "![description](https://assets.ine.com/content/labs/networking-labs/Lab-4297/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-4297/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-4297/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-4297/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: Security with Standard Access Control Lists**\n\n***NOTE:*** The enable password on all IOS devices is \"**INE**\"\n\n\n1. Login to routers R3 and R4 and confirm that, from both of these routers, you can establish an SSH session to router R2 (ssh credentials are **admin/ine**).\n\n2. Configure a numbered, standard Access Control List **on router R2** and apply it in such a way that meets the following criteria:\n\n    - This ACL (combined with how it is applied) must prevent R3 from establishing an SSH session with R2\n    - This ACL may not be applied to interfaces Gig0/0, Gig0/2 or Gig0/3.\n    - This ACL should still allow R3 to ping R2.\n    - This ACL should still allow any other router in your topology to SSH into R2.\n\n3. Verify that your ACL configuration and application on R2 is working per the requirements above.\n\n4. From **PC4**, issue the command, \"**ip dhcp -d**\". Once the PC has obtained an IP address, verify that you can ping the IP address of **222.222.222.2**\n\n5. Configure a **named, standard Access Control list** on any router you wish that meets the following criteria:\n\n    - You may name your ACL anything you wish\n    - The ACL should prevent PC4 from pinging the address of 222.222.222.2 (even if PC4 obtains a different IPv4 address via DHCP in the future).\n    - The ACL should allow PC4 to ping any address in the 180.50.x.x or 20.1.x.x networks.\n    - The ACL should allow router R3 to ping the address of 222.222.222.2, even if this router uses interface Gig0/0 as the source of those pings.\n\n6. Verify that your ACL configuration and application is working per the requirements above.",
    "tasks_html": "<p><strong>Task: Security with Standard Access Control Lists</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 routers R3 and R4 and confirm that, from both of these routers, you can establish an SSH session to router R2 (ssh credentials are <strong>admin/ine</strong>).</p>\n</li>\n<li>\n<p>Configure a numbered, standard Access Control List <strong>on router R2</strong> and apply it in such a way that meets the following criteria:</p>\n<ul>\n<li>This ACL (combined with how it is applied) must prevent R3 from establishing an SSH session with R2</li>\n<li>This ACL may not be applied to interfaces Gig0/0, Gig0/2 or Gig0/3.</li>\n<li>This ACL should still allow R3 to ping R2.</li>\n<li>This ACL should still allow any other router in your topology to SSH into R2.</li>\n</ul>\n</li>\n<li>\n<p>Verify that your ACL configuration and application on R2 is working per the requirements above.</p>\n</li>\n<li>\n<p>From <strong>PC4</strong>, issue the command, \"<strong>ip dhcp -d</strong>\". Once the PC has obtained an IP address, verify that you can ping the IP address of <strong>222.222.222.2</strong></p>\n</li>\n<li>\n<p>Configure a <strong>named, standard Access Control list</strong> on any router you wish that meets the following criteria:</p>\n<ul>\n<li>You may name your ACL anything you wish</li>\n<li>The ACL should prevent PC4 from pinging the address of 222.222.222.2 (even if PC4 obtains a different IPv4 address via DHCP in the future).</li>\n<li>The ACL should allow PC4 to ping any address in the 180.50.x.x or 20.1.x.x networks.</li>\n<li>The ACL should allow router R3 to ping the address of 222.222.222.2, even if this router uses interface Gig0/0 as the source of those pings.</li>\n</ul>\n</li>\n<li>\n<p>Verify that your ACL configuration and application is working per the requirements above.</p>\n</li>\n</ol>",
    "published_date": "2022-11-01T13:57:33Z",
    "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
}