How to configure Management VLAN in Standalone mode for EAP
EAP225-Wall , EAP225-Outdoor , EAP245 , EAP223 , EAP265 HD , EAP230-Wall , EAP620 HD , EAP613 , EAP115 , EAP610 , EAP235 , EAP653 , EAP650-Outdoor , EAP655-Wall , EAP615-Wall , EAP653 UR , EAP660 HD , AP9665 , EAP670-Outdoor , EAP673 , EAP650 , EAP670 , EAP235-Wall , EAP690E HD , EAP225 , EAP623-Outdoor HD , EAP110-Outdoor , EAP650-Wall , EAP610-Outdoor , EAP115-Wall
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.
Management VLAN provides a safer method to manage the EAP. With Management VLAN enabled, only the hosts in the Management VLAN can access the web page of the EAP. Since most hosts cannot process VLAN TAGs, you can connect the management host to the network via a switch, and set up correct VLAN settings for the switches on the network to ensure the communication between the host and the EAP in the Management VLAN. This article introduces how to configure Management VLAN in standalone mode.
Step 1 log in to the web interface of the EAP Series products.
Please refer to this link to log into the web interface of the EAP: https://www.tp-link.com/support/faq/1000/
Step 2 Go to Management-Management VLAN to enable management VLAN.
Please specify the VLAN ID of the management VLAN. Only the hosts in the Management VLAN can log in to the EAP via the Ethernet port.
Note: Once you have enabled the management VLAN and input the VLAN ID here, the EAP will get a IP from corresponding management VLAN network, thus will be disconnected from the computer which is not in the management VLAN. So you cannot log in to the web interface of the EAP anymore with the present PC once Management VLAN enabled.
However, if you want them talk to each other still, as long as the traffic between VLANs is not blocked, you could allow the hosts from other VLANs accessing the EAP by enabling Layer-3 accessibility before management VLAN configuration.
About how to enable layer-3 Accessibility
Go to Management –Web Server to enable Layer-3-Accessibility
Layer-3 Accessibility: With this feature enabled, devices from a different subnet can access the management web page of the EAP. With this feature disabled, only the devices in the same subnet can access the management web page of the EAP. Layer-3 Accessibility is disabled by default for safety reasons.
Related FAQs
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
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
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 . Don’t show again
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 . Don’t show again
Standaard Cookies
Deze cookies zijn noodzakelijk voor de werking van de website en kunnen niet worden uitgeschakeld.
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 en Marketing Cookies
Cookies voor analyse geven ons de mogelijkheid uw activiteiten op onze website te volgen en zo de functionaliteit van de website aan te passen en te verbeteren.
Marketing cookies kunnen op onze website worden geplaatst door externe adverteerders waar wij mee samenwerken om een profiel te creëren met uw interesses en u zo van relevante advertenties te kunnen voorzien op andere websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au