Why is my TP-Link Range Extender not getting the same speed as the main router?

RE105 , RE300 , RE505X , RE715X , RE305 , RE205 , RE600X , RE655BE , RE653BE , TL-WA860RE , RE190 , RE705X , RE650 , RE550 , RE330 , RE450 , RE230 , RE815XE , RE215 , RE605X , RE615X , RE500X , RE900XD , RE315 , RE700X , RE1500X , RE3000X , RE580X , Archer Air R5 , RE1750X , RE780X , RE500XD , TL-WA850RE , RE750C , RE2700X , RE360 , TL-WA855RE , RE200 , RE365 , RE815X , TL-WA854RE , RE220
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.
The purpose of a Range Extender is to expand Wi-Fi coverage and improve the speed at some points. You might not be able to get the same speed as the main router when you are using the Range Extender due to the distance and limitation of Wi-Fi. We usually get lower speed at the position of the Range Extender when compared to the main router.
Here is a simple example of the above theory:
Network topology:
Note: All the clients are in the same position as the Range Extender
Due to the working pattern and protocol/regulation of Wi-Fi technology, the more wireless hops, the slower the speed would be. When Client 1 is connected to the main router and Client 2 is connected to the Range Extender, Client 2’s speed will be slower than Client 1’s, as Client 2 goes through an extra wireless hop compared to Client 1.
However, there will be no speed difference if the client is wired to Range Extender.
Overall, the speed relation of each client in the above topology is as follows:
Client 1 ≈ Client 3 > Client 2
Note: The above speed relation is a reference as the actual speed will vary as a result of device’s specification difference and environmental factors, including building materials, obstacles, volume and density of traffic, etc.
¿Es útil esta pregunta frecuente?
Sus comentarios nos ayudan a mejorar este sitio.
¿Cuál es tu preocupación con este artículo?
- Insatisfecho con el producto
- Muy complicado
- Titulo confuso
- Eso no aplica a mi
- Demasiado vago
- Otro
Gracias
Agradecemos sus comentarios.
Haga clic aquí para comunicarse con el soporte técnico de TP-Link.
Este sitio utiliza cookies. Si continúa navegando por el sitio, acepta el uso que hacemos de las cookies. No volver a mostrar Más información .
Este sitio utiliza cookies. Si continúa navegando por el sitio, acepta el uso que hacemos de las cookies. No volver a mostrar Más información .
Cookies basicas
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
Chat en vivo
__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
Cookies de análisis y marketing
Las cookies de análisis nos permiten analizar sus actividades en nuestro sitio web para mejorar y adaptar la funcionalidad de nuestro sitio web.
Nuestros socios publicitarios pueden configurar las cookies de marketing a través de nuestro sitio web para crear un perfil de sus intereses y mostrarle anuncios relevantes en otros sitios web.
Google Analytics y Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads y DoubleClick
test_cookie, _gcl_au
Meta Pixel
_fbp
Crazy Egg
cebsp_, _ce.s, _ce.clock_data, _ce.clock_event, cebs
lidc, AnalyticsSyncHistory, UserMatchHistory, bcookie, li_sugr, ln_or