How to Configure Management VLANs for Omada Switches and APs (for SOHO / Home Networking Scenario)
SG3452XMPP , EAP680 HD , TL-SG2218P , TL-SG2016P , EAP245 , SG3428XPP-M2 , SG3428XMPP , TL-SG2210P , EAP230-Wall , ER7206 , ER8411 , EAP115 , TL-SL2428P , EAP235 , TL-SX3016F , SG2218 , SG3428 , TL-SG3428X , ER605 , EAP650-Outdoor , SG3218XP-M2 , TL-SG3428X-M2 , EAP610 HD , SG3210X-M2 , EAP660 HD , EAP625-Outdoor HD , TL-SG3428XF , ER707-M2 , ER7412-M2 , EAP110 , SG3452X , SG3210XHP-M2 , ER8411C-M2 , EAP225 , EAP215-Bridge , EAP115-Wall , ER7212PC , SG3428XF , SG6428XHP , EAP683 UR , EAP225-Wall , EAP223 , SG3428MP , SG3428X , SX3016F , TL-SG3428X-UPS , SX6632YF , EAP115-Bridge KIT , SG2218P , EAP620 HD , SG3452XP , EAP613 , EAP615-WE , SG2452LP , EAP610 , SG2210P , SG2016P , SG6428X , EAP615-Wall , TL-ER7206 , EAP683 LR , ER706W-4G , TL-SG3210 , TL-SG3452 , EAP690E HD , ER605W , EAP615GP-Wall , EAP723 , EAP623-Outdoor HD , EAP110-Outdoor , EAP650-Wall , SG3428XMP , TL-SG3428XMP , TL-SG2008P , TL-SG3452X , TL-SG3452XP , SG2210XMP-M2 , EAP683 , EAP673-Extender , ER7406 , EAP680 , EAP113-Outdoor , SG6654XHP , EAP215-Bridge KIT , SG2210MP , TL-SX3008F , TL-SG3452P , SL2428P , EAP653 UR , EAP670-Outdoor , EAP673 , EAP670 , EAP115-Bridge , EAP235-Wall , TL-SG2210MP , SG3428X-M2 , SG3210 , SG3452 , TL-SG3428XPP-M2 , SX3032F , TL-SG3210XHP-M2 , SG2008 , TL-SG2428P , EAP610-Outdoor , SG2005P-PD , EAP610GP-Desktop , SG2428LP , EAP655-WE-AC , EAP211-Bridge , EAP225-Outdoor , SX3008F , EAP783 , SG3452P , EAP265 HD , SG2428P , SG2008P , EAP653 , TL-SG3428 , SG6654X , EAP211-Bridge KIT , TL-ER604W , EAP655-Wall , TL-SG3428MP , EAP773 , EAP772 , EAP650 , EAP770 , TL-SX3206HPP , SX3206HPP , ER706W
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.
Contents
This guide will provide detailed instructions on how to configure separate management VLANs for Omada managed switches and Aps, a client VLAN other than VLAN 1, and isolate them with the clients connected.
- Omada Controller (Software Controller / Hardware Controller / Cloud Based Controller, V5.9 and above)
- Omada Smart, L2+ and L3 switches
- Omada AP
- Omada Gateway
When setting up the network, some customers prefer to modify the management VLANs for the controller, gateway, AP, and switch, and then designate a separate VLAN for clients. This approach ensures that different types of devices are managed in different VLANs, and prevents connected clients from accessing the devices, thereby improving network security.
This guide is suitable for configuring a completely new network for a Small Office/Home Office (SOHO) scenario. This means there are no pre-existing configurations, such as management VLANs, and the network scale is simple and typical. If you want to configure a set of professional business networks or already have a set of network configurations and want to integrate the Omada devices into the network, please refer to the How to configure Management VLANs for Omada Switches and APs (for Business scenario).
Usually, the topologies are like the following, connecting the controller directly to the gateway:
As shown in the topology, the final goal is to shutdown VLAN 1 from the network, set VLAN20 for clients usage, all the clients connected will obtain IP address at 192.168.20.x/24, set VLAN 30 for switch management, and the switches will use a management IP at 192.168.30.x/24, VLAN 40 for AP management, and the APs will use a management IP at 192.168.40.x/24, for gateway and controller, their VLAN will still remain default, but change to another VLAN ID, you can also change the IP addresses for them.
Following are the detailed configuration steps based on the example shown in the topologies above.
Step 1. Adopt the gateway in default VLAN.
Step 2. Create the VLANs needed.
First, create the client VLAN 20, switch management VLAN 30 and AP management VLAN 40. Go to Settings – Wired Networks – LAN - Networks, click Create New LAN.
Below is the example of switch management VLAN 30, its Purpose should be configured as Interface. In LAN Interfaces, tick all the LAN ports you are using, then configure its IP, subnet and DHCP Server. You can configure the name, VLAN ID, subnet IP as you want. Click Save after finished.
Then create the clients VLAN and AP management VLAN as the same method.
Step 3. Configure the default VLAN.
After that, make a change on the default VLAN, click Edit on Default VLAN, change its VLAN ID and subnet IP to bypass VLAN 1 in the network, here I choose to change it to VLAN 10, 192.168.10.x/24 and enable the DHCP server in this network.
Final result should be like this:
Till now, you have created the VLANs in the network and also the interfaces on the gateway. And the IP address of gateway will be switched to 192.168.10.1. After that, you will need to reboot the hardware controller to trigger the DHCP procedure and obtain IP address from 192.168.10.x/24 so you can readopt the gateway, if you are using software controller, just unplug the PC to obtain the IP address again or set a static IP for your PC. Now the Device page should be like:
Step 4. Adopt all switches and APs.
After adopting the switches and APs, they should all obtain IP address from the default VLAN, which subnet is 192.168.10.x/24.
Step 5. Configure the management VLAN for switches.
Go to Devices, click on the switch to enter its private configuration page, go to Config – VLAN Interface, enable the switch management VLAN Interface, click Apply.
Now the switch management VLAN interface has been enabled on the switch, next, configure the management VLAN of the switch. Click the Edit button of the switch management VLAN.
Tick the Enable box to set this VLAN as the management VLAN. After setting it as management VLAN, you can configure its fallback IP, which means when the device failed to get an IP address via DHCP, it will fallback to this IP address, ensuring the management of this device, here I set it as 192.168.30.10, included in the switch management VLAN. Click Apply to save the configuration.
Shutdown the default VLAN Interface to finish the switching of management VLAN, click Apply to save the configuration.
Wait for a moment to let the configurations hand out to the device, the switch may be readopted during this procedure. You will find that the IP address of the switch has been changed to the new VLAN after finished switching management VLAN.
Step 6. Configure the management VLAN for APs.
Go to Devices, click on the EAP to enter its private configuration page. Go to Config – Services and set Management VLAN as Custom, then choose the corresponding VLAN, click Apply to save the configuration.
Wait for a while, after the configuration is executed, you will find the IP address of AP has been changed.
Step 7. Configure port profiles on switches for the use of clients VLAN.
To ensure all the wired clients obtain IP address from clients VLAN, we need to change the port profile of all the downlink ports on switches which directly connect to end devices to the clients VLAN profile.
Go to Devices, click on the switch to enter its private configuration page, go to Ports, select the downlink ports which connect directly to end devices, then click Edit Selected to batch change their port profiles.
Change the profiles of these ports to the profile which is automatically created after creating the clients VLAN, click Apply to save the configuration.
Step 8. Configure SSID VLAN for wireless clients.
Go to Settings – Wireless Networks – WLAN, click Create New Wireless Network to create a SSID for wireless clients.
Set a name and password for this SSID, then click to expand the Advanced Settings, set VLAN to Custom, then in Add VLAN, select the clients VLAN we have created, click Apply to save the configuration.
Step 9. Create ACL rule to prevent clients from accessing controller and network devices.
Go to Settings – Network Security – ACL – Gateway ACL, click Create New Rule to create a new ACL rule.
Enter a name as the Description for this rule, for Direction, choose LAN -> LAN, for Policy, choose Deny, then select all the Protocols, for the Source and Destination, set the Type as Network, then choose the clients VLAN as source and all other management VLANs as the destination. Click Create to create this rule which denies clients to access the controller and other network devices.
By setting this ACL rule, when the client devices are connected and obtain IP address from 192.168.20.x/24, they will not be able to access the controller or the switch, enhancing the network security.
Step 10. Set DHCP Option 138 on all DHCP Servers.
DHCP Option 138 is used to inform the clients the IP address of Omada controller when offering IP address during DHCP procedure, although all the devices are successfully adopted and could communicate with the controller now, they may lost connection with Omada controller after a reboot, so the DHCP Option 138 is needed, after configured, the devices could still obtain the IP address of the controller after a reboot, ensuring their stable management.
Go to Settings – Wired Networks – LAN – Networks, click Edit on the interface, scroll down and expand Advanced DHCP Options, input the controller’s IP address in Option 138 column, click Save to apply the configuration.
|
After this configuration, the gateway, switches and APs are in different management VLANs.
The wired PC connected on the switch is obtaining IP address from the clients VLAN 192.168.20.x/24 :
The phone connected wirelessly is obtaining IP address from clients VLAN 192.168.20.x/24:
The client cannot access managed network devices:
Till now we have introduced how to set up a new network and use different VLAN networks to manage gateway, switches, APs, then connect clients in a specific VLAN and isolate them with the network devices.
Get to know more details of each function and configuration please go to Download Center to download the manual of your product.
Related FAQs
Looking for More
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
We'd love to get your feedback, please let us know how we can improve this content.
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
We have updated our Policies. Read Privacy Policy and Terms of Use here.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy .
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
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
Livechat
__livechat, __lc2_cid, __lc2_cst, __lc_cid, __lc_cst, CASID
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
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
Hotjar
OptanonConsent, _sctr, _cs_s, _hjFirstSeen, _hjAbsoluteSessionInProgress, _hjSessionUser_14, _fbp, ajs_anonymous_id, _hjSessionUser_<hotjar-id>, _uetsid, _schn, _uetvid, NEXT_LOCALE, _hjSession_14, _hjid, _cs_c, _scid, _hjAbsoluteSessionInProgress, _cs_id, _gcl_au, _ga, _gid, _hjIncludedInPageviewSample, _hjSession_<hotjar-id>, _hjIncludedInSessionSample_<hotjar-id>
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or