This post is mainly from posts released by forum customer @Death_Metal, and I would like to thank @Death_Metal and others for the quality and professional Guide sharing you have contributed to the TP-Link forum for such a long time.

 

For some Forum users who have questions about Advanced features, such as VPN, VLAN, ACL, etc., if you need a detailed configuration video, here are some high-quality posts of Configuration and Installation Guide videos for many typical Topologies/Scenarios summarised for reference only.

 

 

1. Guide: Connect Omada as an OpenVPN Client with OpenVPN Access Server on Raspberry Pi4

Use Case:

Some use case for this scenario includes accessing another LAN across the internet, say a PLEX server. Also good for accessing LAN resources such as storage (private Cloud/NAS), across the public Internet

 

 

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

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 the flexibility and power of Omada SDN without compromising security 

 

 

3. How To Block Internet Traffic

Use Case:

Blocking specific VLAN from accessing the Internet.

 

 

4. Replace router from ER605 to ER7206

Use Case:

• Upgrade / Replace ER-605 with ER-7206 with Default IP
• Upgrade / Replace ER-7206 with ER-8411 with non-Default IP

 

 

5. Secured Admin, Home, IoT, Cameras and Guest VLAN using Gateway ACL

Use Case:

• Admin - this is the Native/Default VLAN 1. Access to all VLANs
• Home - Access to all except Admin VLAN
• Guest - Access to Internet only, no access to same-VLAN devices. Wireless ONLY
• Cameras - Access to same-VLAN devices only, no Internet
• IoT - Access to same-VLAN devices with Internet

 

 

6. Isolated VLAN Configuration for Omada

Use Case:

This Isolated VLAN is to complement the limitation of the "Guest" feature for Wireless, specifically, the end-device isolation (i.e. all wireless clients connected to Guest WiFi can't see each other). The Guest feature only works for Wireless Clients only so this Isolated VLAN do a similar thing: prevent other Wired Clients in the same VLAN to see each other (and also not see other Clients in other VLANs). The Isolated VLAN end devices must still be able to access the Internet.

 

 

7. Secluded Wireless VLAN Configuration for Omada

Use Case:

The Secluded Wireless VLAN is to prevent wireless clients to see each peers/neighbors in the same VLAN but still have Internet Access and Granular Access to clients. For users that have implemented the Isolated VLAN design, they found out that using the same/similar ACLs and applying it to EAP didn't work as they expected it to be: the WiFi clients always sees each other in the same VLAN. In this revision, the solution is to simply "poke" a h0le to the Guest Feature functionality. 

 

 

If you want to learn more about Omada-Related configuration videos, please check out here.