Guide: Set Up An All TP Link Omada Pseudo-One-Way (Unidirectional) Stateful ACL for your Network

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Guide: Set Up An All TP Link Omada Pseudo-One-Way (Unidirectional) Stateful ACL for your Network

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Guide: Set Up An All TP Link Omada Pseudo-One-Way (Unidirectional) Stateful ACL for your Network
Guide: Set Up An All TP Link Omada Pseudo-One-Way (Unidirectional) Stateful ACL for your Network
2022-10-20 21:40:22 - last edited 2022-10-28 02:56:09

Guide: Set Up An All TP Link Omada Pseudo-Perimeter Network, with Pseudo-One-Way (Unidirectional) Stateful ACL for Secured IoT Network and Home Computing without explicit ACL definition

 

Short Version Videos:

  • Part1 - https://youtu.be/VTrg2ecGetA
  • Part 2 - https://youtu.be/gQW0kvN_too

 

Hardware Used for this Guide:

  • 1x OC-200
  • 1x ER-7206 (SDN Router A)
  • 1x ER-605
  • 2x SG-2210P

 

Optional Hardware:

  • 2x EAP-610

 

Alternative Hardware/Software Requirement:

  • 2x ER-605 Gateway or 2x ER-7206
  • TP Link Omada Controller (Hardware, Software, Cloud)
  • 1x Any TP Link Omada Managed Switch

 

Note:

A similar set up can be done using non-TP Link Omada devices, or mixed network manufacturer, or a combination of routers only, but that will be out of the scope for this guide.

 

Use Case:

  • Add a pseudo-perimeter network, which adds a layer of network security for Home Computing
  • Fully isolate IoT network from Home VLAN
  • Allow one-way full access to IoT devices without opening ports or creating elaborate ACLs
  • Enjoy flexibility and power of Omada SDN without compromising security 

 

Diagram 1: Current LAN Design

 

  1. Part 1 - Preparing the Perimeter / Outer LAN (Refer to Diagram 1 for connection)

    1. Launch Omada Web Console, Login as an Administrator. It is recommended to do this step locally and have the configuration PC directly connected to one of the OC-200 LAN ports. If desired, backup current configuration and save it to a USB Flash Storage

    2. On ER-7206, modify LAN VLAN IP from Default. If the default IP address of 192.168.0.1 has been changed from default before, skip this step.

      1. Settings > Wired Networks > LAN > <Under Action Column, “Edit” the LAN Profile>

      2. Gateway/Subnet > 192.168.10.1 / 24 > Update DHCP Range

      3. Make sure all LAN interfaces are checked

      4. Save

    3. Inter-connect Gateway, Controller and Switch A SG-2210P

      1. Connect SG-2210P Port 1 to ER-7206 Port LAN2

      2. Connect SG-2210P Port 2 to OC-200 Port 1

      3. Connect your configuration PC to OC-200 Port 2

      4. Optional: Connect your EAP-610 to SG-2210P Port 7

    4. At this time, it is important to follow the network IP as per the diagram, or make sure all SDN network devices have a reserved or static IP. 

      1. 192.168.10.1 - ER-7206

      2. 192.168.10.2 - SG-2210P

      3. 192.168.10.3 - EAP-610

      4. 192.168.10.4 - OC-200

    5. Create IoT VLAN on ER-7206

      1. Settings > Wired Networks > LAN > + Create New LAN

        1. Name: IoT

        2. LAN Interfaces: Checked all LAN ports

        3. VLAN: 107

        4. Gateway/Subnet > 192.168.107.1 / 24 > Update DHCP Range

        5. Save

    6. Assign VLAN 107 on SG-2210P

      1. Devices > <Click on SG-2210P> > Ports > 

        1. Port 3 > <Under Action Column: Click Edit> Profile > IoT

        2. Port 4 > <Under Action Column: Click Edit> Profile > IoT

      2. Apply

    7. Connect all the IoT Devices on Ports 3 and 4 to be assigned to VLAN 107 directly to the switch

    8. Assign VLAN 1 on SG-2210P

      1. Devices > <Click on SG-2210P> > Ports > 

        1. Port 8 > <Under Action Column: Click Edit> Profile > LAN

      2. Apply

 

Diagram 2: New LAN Design

 

 

  1. Part 2 - Preparing Inner LAN Router/Gateway (Refer to Diagram 2).

    1. Connect this Switch A SG-2210P Port 8 to WAN port of Gateway B ER-605

    2. Connect a PC directly to the WAN/LAN3 port of Gateway B ER-605, the right-most LAN port usually works.

    3. Launch a Web browser, and enter 192.168.0.1 to access the web console of Gateway B ER-605

      1. Create Username and Password

      2. Login

    4. Prepare Gateway B ER-605 to be discovered and adopted by OC-200 at Perimeter site

      1. System Tools > Controller Settings > Inform URL/IP address > 192.168.10.4 (this is the Controller’s IP address)

      2. Save

  2. Part 3 - Creating Perimeter and Inner LAN Sites

    1. On the Omada Web Console, create / modify site

      1. Click Sites > + Add New Site

        1. Site Name: Inner

        2. Country/Region: 

        3. Time Zone:

        4. Application Scenario:

        5. Username:

        6. Password:

        7. Apply

      2. Rename and/or Modify the other Omada site to Perimeter (or Outer)

  3. Part 4 - Building the Inner LAN

    1. Make sure the Inner LAN is selected. The new Gateway can not be adopted to the current site with the existing ER-7206 Gateway.

      1. Sites > Inner LAN

    2. Adopt Gateway B ER-605. You may need to “Retry” a couple of times to get this new Gateway adopted. Make sure to use the username/password you created on Steps 2.3. If the Gateway does not appear after more than 5min, check your cable and/or check the Controller Inform URL/IP Address (refer to Step 2.4).

      1. Devices >  <Under Action Column, Click the “Adopt” Checkmark>

      2. Enter user name and password created on Step 2.3

    3. Configure Gateway B ER-605 to make it fully Omada-SDN compliant

      1. Settings > Wired Networks > LAN > <Under Action Column, “Edit” the LAN Profile>

        1. Gateway/Subnet > 172.16.0.1 / 24 > Update DHCP Range

        2. Advanced DHCP Options > Option 138 > 192.168.10.4 (this is the Controller’s IP address)

        3. Save

    4. Connect Switch B SG-2210P to Gateway B ER-605

      1. Transfer your PC’s connection from Gateway B ER-605 WAN/LAN3 Port to Switch B SG-2210P Port 2

      2. Connect Switch B SG-2210P Port 1 to Gateway B ER-605 right most WAN/LAN3 port

      3. Wait and keep refreshing the Devices tab of the Omada web console, until the new switch shows up for adoption. If the switch does not appear after more than 5min, check your cable and/or check the DHCP Option 138 (refer to Step 4.3). 

        1. Devices >  <Under Action Column, Click the “Adopt” Checkmark>

      4. Connect any other Omada network Devices (i.e. EAPs) to the new switch and adopt all devices.  At this time, it is important to follow the network IP as per the diagram, or make sure all SDN network devices have a reserved or static IP for the Inner site.

      5. Create Home VLAN on Gateway B ER-605

        1. Settings > Wired Networks > LAN > + Create New LAN

          1. Name: Home

          2. LAN Interfaces: Checked all LAN ports

          3. VLAN: 10

          4. Gateway/Subnet > 172.16.10.1 / 24 > Update DHCP Range

          5. Save

      6. Using Omada Web Console, find an available Port from Switch B SG-2210P, configure it to “Home” Profile. 

        1. Devices > Select SG-2210P > Ports > <Under Action Column: Click Edit> Profile > Home

        2. Apply

      7. Connect all your clients to this “Home” port. It should have an IP from 172.16.10.x range

  4. Part 5 - Testing

    1. From your PC connected at Switch B SG-2210P at the Inner LAN site, ping any IP on the IoT network i.e. 192.168.107.1. Note, if you have a Windows PC as a test device connected to IoT VLAN, you may need to turn off the Firewall to have ICMP working. The expected result is that all devices at the Outer LAN are reachable unless an ACL is in place to prevent such from happening.

    2. From your PC connected to IoT VLAN, ping any devices that are behind the Gateway B ER-605 Gateway i.e. 172.16.0.x, or 172.16.10.x. It should time out

 

Short Version Videos:

  • Part1 - https://youtu.be/VTrg2ecGetA

  • Part 2 - https://youtu.be/gQW0kvN_too

 

  6      
  6      
#1
Options

Information

Helpful: 6

Views: 1290

Replies: 0