How to create multi networks and manage network behavior with ACL on Omada Gateway in standalone mode

TL-ER7206 , TL-R605 , ER7206 , ER605
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device, and check either the Datasheet or the firmware section for the latest improvements added to your product. Please note that product availability varies by region, and certain models may not be available in your region.
You can create multi networks on the Omada Gateway and manage the access between networks via the Access Control Lists (ACL).
This article will share how to use these features. We focus on how to realize the settings on the Omada Gateway, refer to the simple network topology shown below, there are two departments connected to an Omada Gateway with unmanaged switches, the computers need access to the Internet, but not to the computers in different departments.
If you are using a managed switch supporting the VLAN feature, you can change the VLAN settings of the Omada Gateway and switch according to your network topology.
1. Create multi networks
Log in to the Omada Gateway page, go to Network – LAN, click Add button to create a new network, and fill in the configuration according to your network. Here we set the IP address/subnet mask as 192.168.1.1/255.255.255.0, assign VLAN 10 to the network, and enable the DHCP server.
After saving, the network settings on the Omada Gateway are shown below.
2. Change the VLAN settings
Go to Network – VLAN to change the VLAN settings.
Normally, after creating a new network, all LAN ports of Omada Gateway will remain UNTAG in the default network and will be automatically added to the TAG VLAN of the new network. You can change the VLAN settings of the LAN ports according to your network topology.
Here, since we are using an unmanaged switch, we need to change the Marketing LAN port (Port 5 in the figure below) to UNTAG VLAN 10 and set the PVID to VLAN 10.
At this point, we have finished setting up the networks. Connect all the network nodes, the computers will obtain IP addresses from its network and have access to the Internet, as well as to the computers in different departments.
3. Create ACL to block communication between networks
To block access between computers in different departments, ACL is introduced to manage the network behavior. Go to Firewall – Access Control, and click the Add button to create two new ACL entries. One strategy involves prohibiting the R&D department from accessing the marketing department, while the other involves preventing the marketing department from accessing the R&D department. Follow the settings shown below; Note that the "LAN -> LAN" interface signifies an inter-network traffic ACL entry. Finally, those two departments will be unable to communicate with each other.
The first rule is to prevent the marketing department from accessing the R&D department.
The second rule is to prevent the R&D department from accessing the Marketing department.
Related Video:
Omada SDN Video-How to configure Multi-Networks & Multi-SSIDs?
Related FAQs
Looking for More
Finden Sie diese FAQ hilfreich?
Mit Ihrer Rückmeldung tragen Sie dazu bei, dass wir unsere Webpräsenz verbessern.
Was ist Ihr Bedenken bei diesem Artikel?
- Mit Produkt unzufrieden
- Zu kompliziert
- Irreführende Titel
- Betrifft mich nicht
- Zu ungenau
- Was anderes
Vielen Dank.
Vielen Dank für Ihr Feedback.
Recommend Products
Von United States?
Erhalten Sie Produkte, Events und Leistungen speziell für Ihre Region
Diese Webseite verwendet Cookies, um die Websitenavigation zu verbessern, Online-Aktivitäten zu analysieren und die bestmögliche Nutzererfahrung auf unseren Webseiten zu haben. Sie können der Verwendung von Cookies jederzeit Widersprechen. Nähere Informationen finden Sie in unseren Datenschutzhinweisen.
Diese Webseite verwendet Cookies, um die Websitenavigation zu verbessern, Online-Aktivitäten zu analysieren und die bestmögliche Nutzererfahrung auf unseren Webseiten zu haben. Sie können der Verwendung von Cookies jederzeit Widersprechen. Nähere Informationen finden Sie in unseren Datenschutzhinweisen.
Notwendige Cookies
Diese Cookies sind zur Funktion der Website erforderlich und können in Ihren Systemen nicht deaktiviert werden.
TP-Link
SESSION, JSESSIONID, accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Zendesk
OptanonConsent, __cf_bm, __cfruid, _cfuvid, _help_center_session, _pendo___sg__.<container-id>, _pendo_meta.<container-id>, _pendo_visitorId.<container-id>, _zendesk_authenticated, _zendesk_cookie, _zendesk_session, _zendesk_shared_session, ajs_anonymous_id, cf_clearance
Analyse- und Marketing-Cookies
Analyse-Cookies ermöglichen es uns, Ihre Aktivitäten auf unserer Website zu analysieren, um die Funktionsweise unserer Website zu verbessern und anzupassen.
Die Marketing-Cookies können über unsere Website von unseren Werbepartnern gesetzt werden, um ein Profil Ihrer Interessen zu erstellen und Ihnen relevante Anzeigen auf anderen Websites zu zeigen.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au