AX6000 V2 - latest firmware from cloud services - broken router connection of clients

AX6000 V2 - latest firmware from cloud services - broken router connection of clients

AX6000 V2 - latest firmware from cloud services - broken router connection of clients
AX6000 V2 - latest firmware from cloud services - broken router connection of clients
2025-04-11 07:48:57 - last edited 2025-04-17 10:16:44
Model: Archer AX6000  
Hardware Version: V2
Firmware Version: 1.2.1 Build 20250221 rel.13966 (4555)

Dear TP-Link

 

It looks like the lastest firmware of 1.2.1 Build 20250221 rel.13966 (4555) has broken the router

 

The router can connect to the internet ok, speedtest/ ping etc from the router interface works fine.

 

Any clients connected (wired or wireless) to the router, cannot connect to the internet.

 

Can you please fix the firmware and send me a link to a version I can upgrade my router with to make it work again.

 

Thanks

 

Shap

 

  3      
  3      
#1
Options
1 Accepted Solution
Re:AX6000 V2 - latest firmware from cloud services - broken router connection of clients-Solution
2025-07-04 11:23:07 - last edited 2025-07-04 11:23:11

Hello @Drana  @ShapSMF,

 

Thanks for reminding me of the new official firmware for Archer AX6000 V2.

 

The official 1.4.1 and 1.4.2 version has already fixed the issue discussed in this thread. I've just updated the official post below:

[Solved] Devices Fail to Access the Internet After Updating Archer AX6000 V2 Firmware to 1.2.1

 

Please check for the updates via the AX6000's web interface or through the Tether App to install the latest version manually.

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Introducing AI QoS: Elevate Your Gaming Experience on the Archer GE800 Gaming Router! Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
Recommended Solution
  1  
  1  
#46
Options
44 Reply
Re:AX6000 V2 - latest firmware from cloud services - broken router connection of clients
2025-04-11 08:52:07

Hi @ShapSMF,

Thank you for reporting your issue to our community.

May I know what is the LED status of the router now? Have all clients lost their network connection?

Please try the suggestions below:

    1) Connect a PC directly into your modem to verify if your ISP Internet is stable.
    2) Make sure the Ethernet cable between your modem and the Router is connected properly, replaced old cables with new ones.
    3) Change the DNS Server of the Router, login the web management interface of the Router, go to Advanced > Network > Internet > Advanced Settings, change the two DNS Servers into 1.1.1.1 and 8.8.8.8How to Change the DNS servers on the wireless router and DSL modem router (New UI)?

 

  0  
  0  
#2
Options
Re:AX6000 V2 - latest firmware from cloud services - broken router connection of clients
2025-04-12 09:24:45
I did all the basic troubleshooting steps.... the light on the router is blue. I can successfully run a speedtest and ping from the router interface. Both wired and wireless clients connected to the router are blocked from the internet. I have no blacklisted clients. the ISP has no issues, I can connect directly a client to the ISP and its works fine. It is something is the latest firmware that is blocking traffic. My DNS is also 8.8.8.8 and 8.8.4.4
  1  
  1  
#3
Options
Re:AX6000 V2 - latest firmware from cloud services - broken router connection of clients
2025-04-12 13:52:33

  @Joseph-TP I have the same issue after this latest update. I also noticed that it's not possible to downgrade the firmware to the previous version. I already tried resetting  the device to factory reset and configure my entire network again (AX6000 V2 EU + 2 x RE605X + 4 * RE705X) but within a few minutes the issue reoccurs and there is no connectivity on both cable and WiFI. Restarting the router does not help.On the previous firmware the router was working fine.Supprisingly,the led on the router is blue despite no connectivity.

  1  
  1  
#4
Options
Re:AX6000 V2 - latest firmware from cloud services - broken router connection of clients
2025-04-15 02:32:37 - last edited 2025-04-15 02:33:53

Hi @KubaAdamus & @ShapSMF,

Thank you for your reply and testing results.

Please try the following suggestions:

1. Turn off IPv6;

2. Turn off blacklist on the Access Control page;

3.  Use a PC to Long ping the router's IP(192.168.0.1) and DNS (like 8.8.8.8), How to use the Ping command

Long Ping steps:

  • Ping -t <target IP or domain name>.  Example (continuously pinging the router LAN IP): ping -t 192.168.1.1
  • Press Ctrl + C to terminate and view the statistics.
  • Please take screenshots with the testing result.

 

Thank you.

 

  0  
  0  
#5
Options
Re:AX6000 V2 - latest firmware from cloud services - broken router connection of clients
2025-04-15 07:03:58 - last edited 2025-04-15 07:10:21

  @Joseph-TP 

 

Problem Statement: Since the last cloud firmware update to 1.2.1 Build 20250221 rel.13966 (4555), the AX6000 V2, wired clients are no longer accessible on the LAN. The router assigns the Wired LAN devices with an ip-address. From the router diagnostic page, the LAN devices can be pinged, but any other clients connected by Wifi such as a laptop, the Wired LAN devices are not reachable. uPNP is enabled. IPv6 is off and I have no blacklist items. See ping results below

 

 

Ping google from Wifi connected laptop - ok

shap@Shaps-MacBook-Pro-2 ~ % ping -t5 google.com

PING google.com (142.250.178.14): 56 data bytes

64 bytes from 142.250.178.14: icmp_seq=0 ttl=118 time=5.529 ms

64 bytes from 142.250.178.14: icmp_seq=1 ttl=118 time=7.809 ms

64 bytes from 142.250.178.14: icmp_seq=2 ttl=118 time=6.817 ms

64 bytes from 142.250.178.14: icmp_seq=3 ttl=118 time=7.692 ms

64 bytes from 142.250.178.14: icmp_seq=4 ttl=118 time=8.285 ms

 

--- google.com ping statistics ---

5 packets transmitted, 5 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 5.529/7.226/8.285/0.972 ms

 

Ping router from Wifi connected laptop - ok

shap@Shaps-MacBook-Pro-2 ~ % ping -t5 192.168.0.1

PING 192.168.0.1 (192.168.0.1): 56 data bytes

64 bytes from 192.168.0.1: icmp_seq=0 ttl=64 time=4.438 ms

64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=4.792 ms

64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=3.164 ms

64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=4.206 ms

64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=4.702 ms

 

--- 192.168.0.1 ping statistics ---

5 packets transmitted, 5 packets received, 0.0% packet loss

round-trip min/avg/max/stddev = 3.164/4.260/4.792/0.586 ms

 

Ping local LAN connected NAS1 device from Wifi connected laptop - FAILED

shap@Shaps-MacBook-Pro-2 ~ % ping -t5 192.168.0.119

PING 192.168.0.119 (192.168.0.119): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

 

--- 192.168.0.119 ping statistics ---

5 packets transmitted, 0 packets received, 100.0% packet loss

 

Ping local LAN connected NAS2 device from Wifi connected laptop - partial FAIL

shap@Shaps-MacBook-Pro-2 ~ % ping -t5 192.168.0.120

PING 192.168.0.120 (192.168.0.120): 56 data bytes

64 bytes from 192.168.0.120: icmp_seq=0 ttl=64 time=5.894 ms

64 bytes from 192.168.0.120: icmp_seq=1 ttl=64 time=5.141 ms

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

 

--- 192.168.0.120 ping statistics ---

5 packets transmitted, 2 packets received, 60.0% packet loss

round-trip min/avg/max/stddev = 5.141/5.518/5.894/0.376 ms

 

Ping LAN connected TV device from Wifi connected laptop - FAILED

shap@Shaps-MacBook-Pro-2 ~ % ping -t5 192.168.0.200

PING 192.168.0.200 (192.168.0.200): 56 data bytes

Request timeout for icmp_seq 0

Request timeout for icmp_seq 1

Request timeout for icmp_seq 2

Request timeout for icmp_seq 3

 

--- 192.168.0.200 ping statistics ---

5 packets transmitted, 0 packets received, 100.0% packet loss

 

The LAN connected TV can access the internet services, such as Youtube and Netflix etc...

 

So the issue seems to be related to the internal routing of traffic between the WLAN and LAN interfaces.

 

Prior to the firmware update, there was no issue locally connecting between Wifi clients and LAN clients.

 

I have already done a hard reset of the router back to factory settings to see if I could flush the routing table, it still has the same issue

 

I hope that help you narrow down the faulty code in the firmware

 

Thanks

 

Shap

 

 

  2  
  2  
#6
Options
Re:AX6000 V2 - latest firmware from cloud services - broken router connection of clients
2025-04-15 20:35:27
  0  
  0  
#7
Options
Re:AX6000 V2 - latest firmware from cloud services - broken router connection of clients
2025-04-15 20:36:08

  @mgvelm this is a firmware bug. the router works after disabling all 3 antivirus options. this tplink firmware needs to be fixed urgently.

  1  
  1  
#8
Options
Re:AX6000 V2 - latest firmware from cloud services - broken router connection of clients
2025-04-15 20:42:54

  @mgvelm did you need to reboot the router after disabling the all 3 Anti-virus options?

I'm still having the same issue as before, All device can connect to the internet (Wired and Wireless) but I'm not able to connect from Wireless to my Wired devices or the other way around. Its like the internal routing table is corrupted

  0  
  0  
#9
Options
Re:AX6000 V2 - latest firmware from cloud services - broken router connection of clients
2025-04-15 21:38:53

  @ShapSMF This is a firmware error. After disabling the 3 antivirus options, everything works. The antivirus does not work, but it should. TPlink needs to fix this. I reported it to them.

  2  
  2  
#10
Options
Re:AX6000 V2 - latest firmware from cloud services - broken router connection of clients
2025-04-15 21:48:43

  @mgvelm a reboot fixed it... thanks for investigating and finding a workaround 

  0  
  0  
#11
Options