Archer BE9300 Wireguard client doesn't work after firmware update to Build 20241230

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Archer BE9300 Wireguard client doesn't work after firmware update to Build 20241230

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Archer BE9300 Wireguard client doesn't work after firmware update to Build 20241230
Archer BE9300 Wireguard client doesn't work after firmware update to Build 20241230
2025-02-02 16:30:45
Model: Archer BE550  
Hardware Version: V1
Firmware Version: 1.1.1 Build 20241230 rel.20267(5553)

I have an Archer BE550 v1.0 configured to work as a WireGuard client. At a different location, I have an Archer BE550 v1.0 configured to work as a WireGuard server. The Archer BE550 WireGuard client uses a wg_client file created by the Archer BE550 WireGuard server and connects to the server directly without a VPN provider. The setup worked fine (meaning that I could stream 1080p through the VPN) until the Archer BE550 Client updated through automatic update to firmware build 20241230. Traffic through the VPN ran normally for a few seconds and then slowed to the point that it is unusable (1-15 kbps). Attempts to visit websites through the VPN typically timeout before the sites load. Occasionally, I can get Whatismyipaddress.com to load through the VPN and show the server side ip address showing that the tunnel is active. If I use the exact same wg_client file on my laptop (Dell XPS running Windows 11, Build 26100.3037), the VPN runs at about 10-15 mbps according to speedtest.net, and whatismyipaddress.com confirms the tunnel is active by showing the server side public ip address.

 

I think that the problem is the 20241230 firmware. Does anyone else have the same problem? Is TP-Link working on a fix?

 

Thanks

  5      
  5      
#1
Options
1 Reply
Re:Archer BE9300 Wireguard client doesn't work after firmware update to Build 20241230
2025-02-17 22:23:07

  @SEich1 

I tried several different scenarios using the same WireGuard config file.

 

Setting the local BE550 to be a WireGuard client, hooking a second router's WAN to the BE550's LAN, entering the second router's MAC address on the local BE550 so that the second router uses the VPN tunnel, and connecting other devices (TV, laptop, iPhone) to the second router works.

 

I don't know why connecting devices directly to the client BE550 doesn't allow the VPN to work, but connecting them through a second router does.

 

TP-Link did email me, and I gave them the details. Hopefully they are working on a fix.

  1  
  1  
#2
Options