How to connect TP-Link router with Starlink
Archer AC1900 , Archer C1200 , Archer C5400 , Archer AX12 , Archer C4 , Archer C5 , TL-WR843ND , Archer AX10 , Archer C2 , Archer AX95 , TL-WR842ND(RU) , Archer C59 (EU) , Archer AX96 , Archer AX23 (EU) , Archer C5v , Archer AX17 , Archer AX18 , Archer C6U , Archer AX15 , TL-WR940N , Archer BE850 , Archer C80 , Archer C58HP , Archer AXE95 , Archer AX53 (EU) , Archer C8 , Archer AX10000 , Archer C50 (W) , Archer C9 , Archer C6 , Archer C7 , Archer AX90 , TL-WR843N , Archer C5400X , Archer AX55(RU) , Archer AX5400 , Archer AX53 (RU) , Archer A20 , Archer C60 , Archer A1200 , Archer C64 , TL-WR820N , TL-WR941N , Archer AXE5400 , Archer AX73 (EU) , Archer AX5400 Pro , TL-WR941ND , Archer AX80 , TL-WR901N , TL-WR844N , Archer AX23 (RU) , Archer C59 , Archer C58 , Archer AX4200 , Archer C3200 , Archer A2 , Archer AX75 , Archer AX73 , Archer A10 , Archer AX55(EU) , Archer C50 , Archer C55 , Archer C54 , TL-WR841N , Archer BE550 , Archer AXE75 , Archer AX72 Pro , Archer A6 , Archer A7 , Archer AX72 , Archer A5 , TL-WR801N , Archer AX1450 , Archer A8 , Archer A9 , Archer AX68 , Archer AX5300 , Archer C4000 , Archer AX55 Pro , TL-WR902AC , Archer Air R5 , TL-WR842N , Archer AX1900 , TL-WR841HP , Archer AXE300 , Archer AX1500 , Archer BE700 , Archer AX60 , Archer AX73 (RU) , TL-WR802N , Archer AX73V , Archer AX3000 , Archer A2600 , Archer AX55 , TL-WR841ND , Archer C5200 , Archer AX53 , Archer AX51 , Archer A2200 , Archer BE650 , Archer C20(ISP) , Archer BE11000 Pro , Archer C3150 , Archer AX50 , Archer AX6000 , Archer C25 , Archer C24 , Archer GXE75 , Archer A64 , Archer AX10/A , Archer C2600 , Archer C21 , Archer AX72 (RU) , Archer C20 , TL-WR840N , Archer A10 Pro , Archer AX1800 , Archer BE800 , Archer BE3600 , Archer BE805 , Archer AX206 , TL-WR842ND , Archer C900 , Archer AX4400 , Archer C3000 , Archer C50
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.
There are two generations of Starlink Satellite Dish: The Gen-1 Terminal (Circular Dish) and the Gen-2 Terminal (Rectangular Dish). The main difference between the two versions is the removal of the Ethernet Jack. So with a Gen-2 Terminal, you must purchase an Ethernet Adapter from Starlink first to allow for a wired connection to the network.
Head below to learn how to connect the TP-Link router to the Starlink Terminal.
For the updated Gen-2 Starlink User Terminal
Unlike the Original Starlink Terminal, the Gen-2 Dish is Rectangular, and no PoE adapter is included. The Rectangular Dish will be directly powered by the Gen-2 Starlink router. Since there is no more Ethernet jack on the Gen-2 Starlink router, you must purchase an Ethernet Adapter from Starlink to Connect the TP-Link router.
- Connect the TP-Link router together with the Gen-2 Starlink router
Gen-2 Starlink router supports Bypass mode that will completely disable the built-in Starlink WiFi router functionality. A factory reset is required if you want to switch back to router mode. So when the TP-Link router is connected to the Ethernet adapter, there are two recommended setups.
- Enable Bypass mode on Starlink APP under Settings > Advanced, then set up the TP-Link router in Wireless Router mode.
- Leave Bypass mode disabled on Starlink APP, then set up the TP-Link router in Access Point mode.
For the original Gen-1 Starlink User Terminal
- Connect the TP-Link router without the Gen-1 Starlink router
Go through this FAQ to set up the TP-Link router.
- Connect the TP-Link router together with Gen-1 Starlink router
On this network topology, please connect the TP-Link router to the AUX port of the Gen-1 Starlink Router. To avoid double NAT, it is suggested to change the TP-Link router into Access Point mode.
Follow this guide to change the TP-Link router into Access Point mode.
For any further inquiries about the TP-Link router setup or configuration with Starlink, please contact our technical support.
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
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.
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
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