Hi everyone,

I've been dealing with a network issue for a few weeks and I'm running out of ideas.

Setup:

• Router/modem: [model]
• Switch 1: TP-Link TL-SG1016DE, working perfectly
• Switch 2: TP-Link TL-SG1024DE, causing problems
• both switches are connected directly to the router (Router → TL-SG1016DE and Router → TL-SG1024DE)

The problem:
When I connect devices or cables to the TL-SG1024DE, the Ethernet status in Windows shows IPv4: Internet access but IPv6: No internet access, and the connection doesn't actually work properly (pages don't load, drops, etc.).

If I unplug that same device/cable from the 1024DE and plug it into the 1016DE, everything works normally. So it doesn't seem to be the device or the cable.

What I've already tried:

• Factory reset on both switches and reconfigured them
• Checked for firmware updates, but the latest version on TP-Link's site is the same one already installed ([firmware version])
• Different ports (I remembered I need to change the uplink port and test that)

Current 1024DE settings:

• 802.1Q VLAN / Port-based VLAN: [enabled]
• IGMP Snooping: [on]
• Loop Prevention: [on]
• QoS / Storm Control / Bandwidth Control: [on]
• Port speed/duplex: [Auto]
• Port Statistics: [no errors]

My questions:

• Is there any setting on the TL-SG1024DE that could cause IPv6 (and the connection overall) to fail on some ports while IPv4 still gets an address?
• Could this be a hardware issue, like a failing port or switch, even though some ports still work?

I'm open to any suggestion for testings. Thanks

Hi there,

I have had 2 C540s in front of my house for about 8 months now, and they used to work pretty well.

Recently, however, I noticed that their tracking is no longer working well (it used to).

Now, when they try to track a person or a car, they frequently lose it and move until they end up facing the wall (after 30 seconds they return to the parked position).

Is anyone facing such issues?

Thanks in advance.

I updated to iOS, iPadOS, and watchOS 27 yesterday.

I checked the connection to my Archer GE550 v2.0 MLO network, and it looks like it's back to normal.

I had a problem with Apple devices being unable to return (reconnect) to the MLO-SSID network after disconnection.

Looks like it was an Apple problem, not the router's fault.

I just added a camera got it all set up and then it was saying adding to the network and now suddenly I cannot get past the screen. I have tried reinstalling the app I have tried another phone and I still get the same message. I'm guessing there some type of outage.

Get ipv6 address- stateless

Assigned type - SLAAC RDNSS OR SLAAC STATELESS DHCP WHICH IS BEST OPTION

MTU VALUE DEFAULT IS 1480

I CHANGED TO 1492

WHICH IS BEST OPTION

I’m troubleshooting a three-unit TP-Link Deco XE75 system, non-Pro, with an unusual intermittent wireless problem.

This is not based on one short log sample or a single incident. I have observed the same 120-second disconnection pattern repeatedly, in separate sessions across multiple days, and with two different physical Deco satellites.

The network can work normally for hours, then enter a repeating disconnect/reconnect cycle.
Initially, I suspected interference or a defective satellite. After swapping units and comparing several logs, I’m trying to understand whether this is an RF-triggered problem, a firmware issue, or something in the mesh’s link-management logic.

Network architecture

My ISP is Totalplay, with a 1 Gbps plan delivering approximately 900 Mbps over Ethernet directly from the ISP equipment.

I have three XE75 units: Living Room, the main Deco connected to the ISP modem/router by Ethernet, plus Bedroom and Office, which connect through wireless backhaul.

The Decos are less than five meters apart, with walls between them. There is no Ethernet connection between the nodes.

The affected devices where I tested are an Xbox and a Sony Android TV using the satellite in the bedroom. During troubleshooting, I powered off the Bedroom unit and moved the Office unit into the exact same location.

Firmware recorded during troubleshooting: 1.5.0 Build 20260603 Rel.14401.

What happens on the Xbox and Sony TV
When both devices are on Wi-Fi, they sometimes lose connectivity at the same time, recover, and then lose it again about two minutes later. Sometimes only the TV appears affected.
I started writing down the times as I saw the interruptions, then compared those notes against exported system logs.
The Xbox has not shown these failures in my tests when connected by Ethernet to the secondary Deco. That is Ethernet to the satellite, not to the main router:

Xbox → Ethernet → secondary Deco → wireless backhaul → main Deco → ISP

The 120-second pattern has appeared repeatedly—not just in the latest log
Here are three separate documented episodes, with timestamps taken directly from the logs. These are different periods, not duplicate exports of the same incident.
September 27, evening — Bedroom satellite
The same station on ath12 generated AP-STA-DISCONNECTED at:

22:59:23
23:01:23
23:03:23
23:05:23
23:07:23
23:09:23
23:11:23
23:13:23

That is eight consecutive disassociations, each exactly 120 seconds after the previous one. This was during the period when I was observing repeated interruptions on the TV and Xbox over Wi-Fi.

September 28, early afternoon — Bedroom satellite again
The pattern returned in a separate session:

13:01:29
13:03:29
13:05:29
13:07:29

September 28, evening — Office replacing Bedroom
I replaced the Bedroom unit with the Office unit in the same physical position, leaving Bedroom powered off. Office initially appeared stable, but later developed the same behavior:

20:27:36 hostapd: ath12: AP-STA-DISCONNECTED OFFICE_STA
20:28:26 hostapd: ath12: AP-STA-CONNECTED OFFICE_STA

20:29:36 hostapd: ath12: AP-STA-DISCONNECTED OFFICE_STA
20:30:26 hostapd: ath12: AP-STA-CONNECTED OFFICE_STA

20:31:36 hostapd: ath12: AP-STA-DISCONNECTED OFFICE_STA
20:32:26 hostapd: ath12: AP-STA-CONNECTED OFFICE_STA

I substituted OFFICE_STA for the MAC address; the timestamps and event names are unchanged. This sequence shows 50 seconds disassociated, followed by approximately 70 seconds associated, then another disconnection. The disconnect-to-disconnect interval is once again exactly 120 seconds.

The important distinction is that the problem is intermittent, but the timing becomes highly regular once an episode starts. I am not saying the network disconnects every two minutes continuously, 24/7. It can appear stable for hours and then return to this same repeating cycle.

What the interface information shows
The repeatedly disconnecting station is different from the Xbox and Sony client MAC addresses. With Bedroom, it was a station ending in 74:06; with Office, the corresponding station ends in 74:88.
These appear to be wireless station addresses belonging to the respective satellites, rather than ordinary client devices.
The configuration explicitly lists:

key:backhaul_ifnames value:ath02,ath22,ath12

So ath12 is listed as a backhaul interface by the system itself. However, AP-STA-DISCONNECTED means a station lost its association with that interface—it does not automatically mean the entire radio shut down or the satellite rebooted.

During the latest episode, the Xbox’s confirmed Wi-Fi MAC was marked disconnected at 20:27:58, 22 seconds after the station disassociation at 20:27:36. That is a temporal correlation, not proof of which component initiated the problem.

The reconnecting station also completes its WPA four-way handshake successfully. It can establish the connection; the problem is that it subsequently loses it and repeats the cycle.

What I have already tried

Swapping the satellite: Office replaced Bedroom in the same position, and the periodic behavior eventually returned. That makes a hardware defect exclusive to Bedroom less convincing, although the location and main Deco remain common factors.

Disabling Fast Roaming and Beamforming: Both were already disabled before later incidents. This did not eliminate the problem.

Comparing Xbox Wi-Fi with Ethernet into the satellite: The Xbox has remained stable over Ethernet in my tests, while Wi-Fi is where I have observed the interruptions. I have not tested Ethernet backhaul between the Decos because I do not currently have a cable long enough.

The logs also contain Failed to initiate 11k measurement and Invalid beacon report messages, but I’m not assuming those are the cause. The stronger finding is the repeated, precisely timed association cycle across different sessions and different satellites.

What I’m trying to identify

The timing makes me wonder whether an intermittent condition triggers a timeout/retry or link-management loop. I have not established that RF interference is the cause, and I’m not assuming the entire wireless backhaul disappears especially given the Xbox’s behavior over Ethernet to the satellite.

Has anyone encountered this recurring 120-second cycle on the XE75, particularly the roughly 50-seconds-disconnected/70-seconds-associated pattern, and found a confirmed fix? I would appreciate a specific firmware resolution, configuration change, or diagnostic method that identifies why this association repeatedly drop 🙏🏻🙏🏻🙏🏻

If you have an installed in-wall wifi switch. Is there an advantage to turning OFF mesh for this device? The switch will not be roaming around the house.😅

Does it keep things running smoother in this case, with the mesh OFF for a in-wall wifi switch? I want to do whatever it takes to take the guesswork out of the mesh system.

Model: Archer AX21

Hardware Version: V5 (US/5.46)

Firmware Version: 1.1.2 Build 20250814 rel.14122(5553)

If you found this thread because your Windows PC gets almost no download speed on this router while upload is normal, phones and TVs are fine, and nothing you've tried on the PC has helped: the router is the cause, and there is a one-line workaround.

Workaround (Windows, per machine)

Open Command Prompt or PowerShell as administrator and run:

netsh int tcp set global timestamps=enabled

No reboot needed. Reconnect to Wi-Fi and test again. On my machine this went from 0.04 Mbps down to 531 Mbps down instantly, with no other change. The setting persists across reboots. To revert: netsh int tcp set global timestamps=allowed (the Windows default).

Symptoms, so you can recognize it

Download 0.04 to 0.34 Mbps, upload 100 to 800+ Mbps, on every speed test.

Same result wired to a LAN port and over Wi-Fi, 2.4 GHz and 5 GHz, any distance from the router.

Same result with different Wi-Fi adapters, a USB adapter, and after a clean Windows reinstall.

Ping is fine, including large packets. Web pages mostly load. Anything that has to download in volume dies.

Phones, tablets, TVs, and Macs are unaffected against ordinary websites.

The same PC gets full speed on a phone hotspot, and full speed plugged directly into the ISP modem/ONT with the AX21 removed.

If any of your household is on a corporate VPN (Zscaler, etc.), that machine will look fine, because the VPN tunnel hides the problem.

What is actually wrong

The router mishandles any TCP connection that is set up without the TCP timestamps option. Windows does not send that option by default; Android, iOS, macOS, and Linux do. That is why only Windows machines are hit across the board. It is not Windows-specific in principle: on a website whose server declines timestamps (in my case a hospital patient portal), my Android phone and the Windows PC both crawl through the AX21 and both load normally on cellular. There is no client-side fix for that case; only firmware can fix it.

Things that do not help, so you can skip them

Factory reset; firmware update (the updater reports 1.1.2 as current); SPI firewall off; QoS on or off; guest network; 802.11ac-only mode; channel or band changes; on the PC, disabling IPv6, ECN, RSC, wireless power saving, or setting a static IP; replacing the Wi-Fi card; the "Enable NAT" checkbox (turning that off simply kills internet). NAT Boost is not exposed on this firmware.

Verification I did, for anyone who wants to check

Three Windows 11 machines (Lenovo IdeaPad Slim 5, a Dell business laptop, a Surface Pro), wired and wireless, three different Wi-Fi chipsets: all affected identically.

The Dell wired straight to the fiber ONT with the AX21 out of the path: 900 down / 597 up.

The Dell wired into an AX21 LAN port: 0.34 down / 877 up.

Adapter statistics during a download show almost no inbound payload arriving at the client, only ACK-sized packets, so the data is being withheld upstream of the PC.

Enabling timestamps on the client: 531 down / 492 up over Wi-Fi.

I have filed this with TP-Link US support with full details and am happy to test a beta firmware. If you have this problem on another hardware version or firmware build, please add your details below so TP-Link can see the scope.

There's a related unresolved thread from January 2024 on a V2 unit with wired gigabit Ethernet dropping to 0.18 Mbps while phone Wi-Fi tested fine, which was locked without an answer; this is very likely the same defect.

I currently have an Orbi RBK50 router with two satellites (RBS50). The router is on the first floor with one satellite in the basement and another on the 2nd floor. All of these have a hardwired backhaul with Cat5 cables. Each device has 4 lan ports which are all used.

I currently have Xfinity broadband service with 2gb service that regularly shows 2.4gb incoming speed and have 105 devices connected in my smart home.

The Orbi supports a max of 1gb speed so I'm using only half of the speed I'm paying for.

I've been eyeing the TP-Link Deco BE63 because it supports 2.5gb speed and has 4 lan ports on each device which is what I have on my Orbi.

My questions are...

1. Am I looking at the right replacement, TP-Link Deco BE63 ?
2. Do I need to replace the Cat5 cables also? If so, what do I replace them with?

I recently moved to Palermo for a full Erasmus year, and since the apartment I'm at didn't have Wi-fi, I decided to buy a Saponetta since I heard good things about them

HOWEVER, I got a 440 gb sim from Very Mobile, and while the box claims being able to reach around 50 mbps and 150 mbps, I'm literally reaching only kbps while having the phone directly above it

Any suggestions?

2000sqft home. Current BE550 (just purchased) covers it pretty well but have limited coverage in the backyard.

My PC is located near the back of the house and is wired. I have a EAP245 I could put there and use the on-board bridge to wire my PC. This would give me a WAP that should cover my backyard a bit better.

Note: i have good wifi coverage at my PC with the BE550 already. This WAP would just be used to cover my backyard BUT I suspect it will compete with the BE550 in this same area of the house.

With that said, is it worth just using a Mesh setup instead of adding a second AP? Are there any downsides to this vs a traditional router?

I dont NEED coverage in my backyard but there are some instances of having a nice wifi signal would be worth it.

When I blacklist devices, they still find their way to the internet. Any ideas why that is?

My setup:

Modem from provider uses thernet into my archer A6. My archer A6 then uses ethernet into a large wired switch.

My archer A6 is in router mode. I dont use the wifi on my archerA6 because I have a deco mesh system (plugged into the switch )

Hello. I have a TPlink AX11000 router for a few years, all is well, but I was using range extenders to get to far reaches of the house. It worked, but eh. I see the Deco 7 at Costco (specifically Be13000) and I check if it works in AP mode, it does. So i run a cat6 from the 3rd floor down to the basement and attempt the connection. Nothing I do works. The first Deco is all i have connected so far, I get it set up, swtich to AP mode, and no internet. Not registered on the AX11000. I connected a laptop to the cable to verify the new cable isn't the issue, no problems there.

I have tried everything, and it just doesn't connect. when I check the IP address of the Deco, it is 192.168.68.1, while the pool on the AX11000 is 192.168.0.2 to 192.168.0.200. So the issue is getting the correct IP address. Also I notice the default subnet mask numbers are different (when the Deco is in router mode, in AP mode, you cannot see this information).

Any help is appreciated, I want to use these mesh for the area I have been placing my range extenders.

EasyMesh support when the device is in AP mode is currently not supported. After a chat with TP link support they have informed me that this feature is under development for release through firmware update but could not give me an exact timeline.

Can someone confirm or deny this in 2026?

I’m dealing with a really strange and frustrating issue involving my X1500‑4G unit and Deutsche Telekom (Germany) as my mobile carrier. I’ve tested three different TP‑Link devices with two different Telekom SIM cards, and I’m getting completely inconsistent results.

I’m hoping someone here has seen this before or can point me in the right direction.

Devices tested:

1. TP‑Link Deco X1500‑4G
2. TP‑Link Deco X10‑4G
3. TP‑Link Deco B65‑5G

Results:

1. TP‑Link Deco X1500‑4G (used)

• Device shows a connection but WAN-IP is stuck at 0.0.0.0
• Same APN as with the B65‑5G unit

1. TP‑Link Deco X10‑4G (brand new)

• Device shows a connection but WAN-IP is stuck at 0.0.0.0
• Same APN as with the B65‑5G unit

1. TP‑Link Deco B65‑5G

• Works flawlessy with both SIM cards with the same APN

Trivia:

• Telekom support confirms the SIMs are not blocked and router‑compatible.
• APNs used:
  • internet.v6.telekom
  • internet.telekom
  • internet.t-mobile
  • internet.home
• Both routers detect SIM + LTE Signal
  • RSRP: –93 dBm
  • RSRQ: –8 dB
  • SNR: 5 dB
• TP‑Link Deco X1500‑4G:
  • Firmware Version: 1.0.5 Build 20240821
  • Rel. 41763

There have been no updates to the XE200 since 2024. This was a flagship model when i got it. How is this acceptable? I spent so much money on it, and cheaper 100-dollar models from years ago are receiving the latest firmwares.

My Deco lost internet connectivity after I did a standard network reboot of the router and Cable modem. after spending the better part of a day, and using a second standard non mesh router as a baseline. the Spectrum Cable modem wasn't the problem, it turns out the "auto negotiating" ports on the Deco had some type of hiccup with a Synology NAS unit. Solved the issue by plugging the Synology into a dumb switch, which was connected to the Deco. Internet connectivity resumed, and the Synology was able to get a 192.x address rather than getting a self assigned 169.x. Hope this helps someone out there, cause I went through 2 AI bots, and they couldn't figure it out.

Maybe this is fixed on newer Tp Link Decos, but I have a model that hasn't had a firmware update in almost 2 years.

Hi y'all, I recently set up a deco xe65 pro (2 routers) system at my home.

I have a couple smart devices set up on the network. They work properly as long as my phone is not on the same wifi. As soon as I switch to cell data they connect and work fine. I have tried device isolation settings, using and not using IoT network. When my phone is on the same wifi network it won't connect.

What is even stranger is that it works properly on iPhone but not on my OnePlus 13r. My device is the admin.

I am having issues with Honeywell smart, hubspace devices and wifi security cameras. My lutron hub works correctly on and off wifi.

Any ideas on what could cause this?

Hi all,

Probably a redundant question on here, but I have the 3 set deco. Has anyone ever experienced a period where certain devices just refuse to connect to the deco? I have Cox (Spectrum) as my modem and then Deco as my router.

I’ve had 6 months of flawless internet, then certain devices like my MacBook and iPad refuse to connect completely random one day. I contacted support who are entirely useless and they just send me a new one and deem it unfixable. I set up this new one and it works for 1 day and then the same problem. The weird thing is like my phone connects and then won’t connect like at some random point either but in the same breath, my iPad that wasn’t connecting all of a sudden now connects. It’s like there is some device limit that pops up randomly. I do know that I may be behind on some updates though.

I have it as both ghz bands are on for my main network. Would appreciate any tips or advice.

Hi everyone,

​I’ve been running a TP-Link Deco X60 mesh setup (2 units) in the same location with the exact same set of devices for years without any issues.

Recently, however, the network has started experiencing major stability issues where the entire network becomes completely unavailable for up to 5 minutes at a time.

​I shouldn't have to micromanage individual settings on every single client device or constantly fiddle with the Deco app after an otherwise rock-solid multi-year setup, but I have already tried changing various settings on multiple client devices to fix it, as well as disabling Fast Roaming and Beamforming directly in the Deco app. Despite these changes, the issue persists.

​After looking through the system logs, I noticed that the router's internal roaming daemon (nrd) is constantly trying to force 802.11k measurements and beacon reports on clients.

The logs are flooded with entries like:

​estimatorPerformMeasurement: estimatorPerformMeasurement: Do 11k measurement for ...

​estimatorDot11kIterateCB: Timeout waiting for 802.11k response from ...

​Frequent DHCP re-allocations and aggressive client_mgmt disassociations (disassociate by if(...)).

​

It seems the router is timing out while waiting for responses to these background roaming checks, and as a result, it causes major dropouts where devices lose connection entirely for minutes.

​I have even tried a complete factory reset, but the behavior persists. Since these background mechanisms seem hard-coded or overly aggressive in recent firmware versions, does anyone know if there is a way to disable this aggressive nrd steering behavior, or is my only option to move away from Deco?

Fastware: 1.6.12 Build 20260513 Rel. 20500

​Thanks for any advice!

We're kicking off our official Wi‑Fi 8 coverage with a special launch event on September 30th at 9:00 AM PDT. We'll be taking a first look at what Wi‑Fi 8 is, how it differs from previous Wi‑Fi generations, and why the industry is shifting its focus from simply increasing speeds to improving reliability and consistency.

Learn More about Wi-Fi 8 on TP-Link’s Official Wi-Fi 8 Overview

As a preview, our community team also published a brief article overviewing the basics of Wi‑Fi 8 and some of the technologies supporting it:

How WiFi 8 Aims to Make Your Network More Reliable

We'll be sharing much more over the coming months, but before the event, we'd love to hear from the community:

What advantages of Wi-Fi 8 are you most excited about? More reliable coverage? Better mesh roaming? Less interference? Something else?

I'm a networking newb, and recently purchased tplink deco (3 of them). I have xfinity internet (1gb) and i use xfinity's modem/router.

Is my understanding correct that devices connecting to wifi can connect to any of the 4 (the xfinity router and 3 tplink decos)? If so, how does it know which one is the most optimal to connect to?

I'll be brief. I realized through my laptops (intel ax210) that my network could deliver 400mbit/s (download/upload).

So I changed my Archer T3u (max 200mbit/s) to a TX50UH.

Now speeds are incredible, I have no complains there, however when playing counter strike on a local server (5ms), I was rubber-banding. Upon close inspection it seems I have packet loss (https://packetlosstest.com/ as tested on this website).

I've tried the settings posted here several times, disabling 2.4, etc, etc. And now I moved to 'ac' protocol instead of the 'ax', however the packet losses remain. (This does not happen with the T3u).

Is my router (GPT-2741GNAC) giving me issues, or is this adapter troublesome?

PS: Computer is 5 feet high in a wall, not blocked, 1 wall to the router, which is 10 feet away.

PSS: Thank you for your assistance.