How to Configure Port Isolation Function on Our Layer 2 Manage switches through Web Browser
TL-SG2452 , T1500G-10PS , TL-SL2210 , TL-SG3424 , TL-SG2424P , TL-SG5428 , T2600G-52TS , T2600G-28TS , T2700G-28TQ , TL-SG5412F , T1500G-10MPS , TL-SG3424P , TL-SL3428 , TL-SL2218 , T1700X-16TS , T1600G-28TS , TL-SG2424 , TL-SG3216 , TL-SL5428E , T1700G-28TQ , T1500-28PCT , T1600G-28PS , TL-SG3210 , SG3210 , TL-SL2428 , T1600G-52TS , T3700G-28TQ , T1500G-8T , TL-SL2452WEB
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.
By using port isolation function, you can achieve the goal of preventing PCs under different ports communicating with each other without configuring VLAN.
How to configure:
Step1: Open your browser and log in the web interface of you switch.
Step2: please go to Switching->Port->Port Isolation->Port Isolation Config.
Port: Choose a port (assume it is port 1) you need to configure.
Forward Portlist: choose ports to which packets from port 1 can be forwarded.
Note: Since communications are bidirectional, if you want hosts under port 1 to communicate with hosts under port 2, you need both port1’s forward portlist allow port 2 and port2’s forward portlist allow port 1.
An example:
Topology:
PC1 connect to port 1, PC2 connect to port 2, PC3 connect to port 3, server A connect to port 4, server B connect to port 5.
Goal:
PC1, PC2, PC3 can’t communicate with each other, PC1 can access both server A and server B, PC2, PC3 can only access server A.
The configuration process is as follows:
Step1: Open the browser and log in the management-page of the switch.
Step2: After log in, please go to: Switching->Port->Port Isolation->Port Isolation Config.
Step3: Configure each port as below:
For port1:
For port2:
For port3:
For port4:
For port5:
Click Saving Config to save the configuration file.
If configure like this, PC1 can access both server A and server B, PC2 and PC3 can only access server A. Three PCs can’t communicate with each other.
Get to know more details of each function and configuration please go to Download Center to download the manual of your product.
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.
Recommended Products
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
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
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
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
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