New Release WireGuard VPN Firmware for Archer AX55
Hello Everyone,
We are thrilled to announce that we now have officially published the WireGuard VPN firmware for Archer AX55 V1, which we believe you’re going to love it. Please check for the updates on your router web GUI or Tether App for the new firmware, or you can download the latest firmware from the website as follows:
WireGuard VPN Firmware for Archer AX55 V1.0 (official firmware updated on 6/9/2023)
How to Configure WireGuard VPN Client on Archer AX55
Please follow the steps below to set up and configure the WireGuard VPN Client on the Archer AX55:
Step 1 Please download the configuration file from your VPN provider.
Step 2 We currently support some basic parameters of the WireGuard configuration file as Pic 1. If the configuration file you are using includes IPv6 address, MTU or many more (example as Pic 2), please edit the file and delete those parameters, then save the file.
Step 3 Visit http://tplinkwifi.net, and log in with your TP-Link ID or the password you set for the router. Go to Advanced > VPN Client.
Step 4 Enable VPN Client, then save the settings.
Step 5 Click Add button in the up-right of the Server List, specify a description for the VPN and choose WireGuard as the VPN type, click BROWSE to import the configuration file provided by your VPN provider, then click SAVE.
Step 5 Check and enable the WireGuard in the Server List, add and enable the VPN Access for the devices that will use the VPN function.
Note: It's NOT suggested to use the same configuration file on multiple VPN Clients simultaneously. You could import the configuration file into your mobile phones as well as the router, but you are not allowed to connect to the VPN server simultaneously based on WireGuard protocols.
How to Set up Archer AX55 as a WireGuard VPN Server
Step 1 On the Web GUI of Archer AX55, go to Advanced > VPN Server, check and enable WireGuard.
Step 2 Click Add button in the upper-right of the Account List to add the profile, then save it.
Note: Each profile can be only used for one device at the same time. If you want to connect 2 devices to the WireGuard VPN server, please create 2 profiles for them accordingly.
Step 3 Export the configuration file on the devices that you want to connect to the WireGuard VPN Server.
a. For smartphones, you can scan the QR Code directly on your WireGuard App.
b. For computers, you can click Export button to export the configuration file, and import it into your WireGuard client.
Other New Features/Enhancements:
1. Added IoT Network.
This allows you to create a dedicated wireless network for the IoT smart devices. You can find it under Advanced > Wireless > IoT Network.
2. Support configuring HomeShield features on Web GUI.
3. Support configuring local DNS servers on WAN/Internet page.
Some users would like to build their own DNS servers within the local network, which was only achievable on the router's DHCP Server settings. Now you can configure it on the WAN/Internet page.
4. Added Access Control feature in AP mode (Security > Access Control).
5. Support retrieving the PPPoE dial-up settings from the old router.
There are cases that you are replacing your old Wi-Fi router with this Archer AX55, and it could be troublesome to set up the internet if you no longer remember your PPPoE username and password. Now this won't be an issue. You can retrieve the PPPoE settings easily from the old router by following the two steps as shown below:
More features and enhancements are waiting for you to explore:
- Added Flow Control ON/OFF switch (Advanced > Network > LAN > Flow Controller).
- Optimized the Web GUI in AP mode.
- Optimized IPv6 feature.
- Optimized UI for USB sharing.
- Optimized Port Forwarding function.
- Optimized VPN Client function.
- Optimized UI for configuring IPTV/VLAN.
Welcome to upgrade and install this beta firmware on your Archer AX55, and feel free to reporting back to us with bugs, faults, errors, and your thoughts on how to improve.
Related Articles:
Wi-Fi Routers that are Planned to support WireGuard VPN
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
FYI, homeshield security, no longer works.
- Copy Link
- Report Inappropriate Content
@Kevin_Z I haven't had any success in getting it to connect. I thought I would test it for you before sending the router back.
This is the log after many attempts. It just seems to hang up on the connecting portion:
####################################################################
# Archer AX55 System Log
# Time = 2023-04-02 10:53:24
# H-Ver = 1.0.0 ; S-Ver = 1.1.9 Build 20230323 rel.70160
# LAN: I = 192.168.0.1 ; M = 255.255.255.0 ; MAC = B4:B0:24:78:46:CC
# WAN: W = dhcp ; I = 24.19.39.134 ; M = 255.255.252.0 ; MAC = B4:B0:24:78:46:CD
# G = 24.19.36.1 ; D1 = 75.75.75.75 ; D2 = 75.75.76.76
# Clients connected: 10 ; WI-FI : 9
####################################################################
2023-04-02 10:51:34 nat[6626]: <6> 211501 Initialization succeeded
2023-04-02 10:51:33 nat[6626]: <6> 211501 Initialization succeeded
2023-04-02 10:51:26 remote-management[5903]: <6> 282505 Service stop
2023-04-02 10:51:26 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:51:24 nat[5369]: <6> 211501 Initialization succeeded
2023-04-02 10:51:23 nat[5369]: <6> 211501 Initialization succeeded
2023-04-02 10:51:21 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:50:56 dhcps[4238]: <6> 212504 Service start
2023-04-02 10:49:57 nat[1322]: <6> 211501 Initialization succeeded
2023-04-02 10:49:56 nat[1322]: <6> 211501 Initialization succeeded
2023-04-02 10:49:49 remote-management[624]: <6> 282505 Service stop
2023-04-02 10:49:47 nat[32580]: <6> 211501 Initialization succeeded
2023-04-02 10:49:46 nat[32580]: <6> 211501 Initialization succeeded
2023-04-02 10:49:44 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:49:31 nat[31419]: <6> 211501 Initialization succeeded
2023-04-02 10:49:31 nat[31419]: <6> 211501 Initialization succeeded
2023-04-02 10:49:26 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:49:22 nat[30132]: <6> 211501 Initialization succeeded
2023-04-02 10:49:21 remote-management[30391]: <6> 282505 Service stop
2023-04-02 10:49:21 nat[30132]: <6> 211501 Initialization succeeded
2023-04-02 10:49:18 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:47:51 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:47:48 nat[25945]: <6> 211501 Initialization succeeded
2023-04-02 10:47:48 nat[25945]: <6> 211501 Initialization succeeded
2023-04-02 10:47:46 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:47:40 remote-management[25207]: <6> 282505 Service stop
2023-04-02 10:47:39 nat[24802]: <6> 211501 Initialization succeeded
2023-04-02 10:47:39 nat[24802]: <6> 211501 Initialization succeeded
2023-04-02 10:47:36 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:47:22 nat[23564]: <6> 211501 Initialization succeeded
2023-04-02 10:47:22 nat[23564]: <6> 211501 Initialization succeeded
2023-04-02 10:47:16 remote-management[22957]: <6> 282505 Service stop
2023-04-02 10:47:14 nat[22470]: <6> 211501 Initialization succeeded
2023-04-02 10:47:14 nat[22470]: <6> 211501 Initialization succeeded
2023-04-02 10:47:11 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:46:57 nat[20943]: <6> 211501 Initialization succeeded
2023-04-02 10:46:56 nat[20943]: <6> 211501 Initialization succeeded
2023-04-02 10:46:54 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:46:49 remote-management[20258]: <6> 282505 Service stop
2023-04-02 10:46:48 nat[19715]: <6> 211501 Initialization succeeded
2023-04-02 10:46:47 nat[19715]: <6> 211501 Initialization succeeded
2023-04-02 10:46:45 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:45:23 nat[16241]: <6> 211501 Initialization succeeded
2023-04-02 10:45:23 nat[16241]: <6> 211501 Initialization succeeded
2023-04-02 10:45:15 nat[15075]: <6> 211501 Initialization succeeded
2023-04-02 10:45:15 remote-management[15353]: <6> 282505 Service stop
2023-04-02 10:45:14 nat[15075]: <6> 211501 Initialization succeeded
2023-04-02 10:45:12 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:44:59 nat[13616]: <6> 211501 Initialization succeeded
2023-04-02 10:44:58 nat[13616]: <6> 211501 Initialization succeeded
2023-04-02 10:44:50 remote-management[12915]: <6> 282505 Service stop
2023-04-02 10:44:49 nat[12406]: <6> 211501 Initialization succeeded
2023-04-02 10:44:48 nat[12406]: <6> 211501 Initialization succeeded
2023-04-02 10:44:46 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:44:05 nat[10070]: <6> 211501 Initialization succeeded
2023-04-02 10:44:04 nat[10070]: <6> 211501 Initialization succeeded
2023-04-02 10:43:57 remote-management[9399]: <6> 282505 Service stop
2023-04-02 10:43:55 nat[8905]: <6> 211501 Initialization succeeded
2023-04-02 10:43:55 nat[8905]: <6> 211501 Initialization succeeded
2023-04-02 10:43:52 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:42:54 nat[6099]: <6> 211501 Initialization succeeded
2023-04-02 10:42:54 nat[6099]: <6> 211501 Initialization succeeded
2023-04-02 10:42:44 nat[4857]: <6> 211501 Initialization succeeded
2023-04-02 10:42:43 remote-management[5138]: <6> 282505 Service stop
2023-04-02 10:42:43 nat[4857]: <6> 211501 Initialization succeeded
2023-04-02 10:42:41 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:41:22 nat[1321]: <6> 211501 Initialization succeeded
2023-04-02 10:41:21 nat[1321]: <6> 211501 Initialization succeeded
2023-04-02 10:41:15 remote-management[705]: <6> 282505 Service stop
2023-04-02 10:41:13 nat[32684]: <6> 211501 Initialization succeeded
2023-04-02 10:41:13 nat[32684]: <6> 211501 Initialization succeeded
2023-04-02 10:41:10 traffic-stats[12800]: <6> 269004 stats reset
2023-04-02 10:40:18 upnp[29849]: <6> 217504 Service start
2023-04-02 10:40:18 upnp[29849]: <6> 217505 Service stop
2023-04-02 10:40:15 remote-management[29447]: <6> 282505 Service stop
2023-04-02 10:40:05 qos[28629]: <6> 259504 Service start
2023-04-02 10:40:05 qos[28629]: <6> 259503 Function disabled
2023-04-02 10:40:05 qos[28629]: <6> 259505 Service stop
2023-03-23 00:05:39 nat[28177]: <6> 211501 Initialization succeeded
2023-03-23 00:05:38 nat[28177]: <6> 211501 Initialization succeeded
2023-03-23 00:05:33 led-controller[1107]: <6> 288051 Start to run WAN1_ON
2023-03-23 00:05:33 led-controller[1107]: <6> 288051 Start to run WAN0_OFF
2023-03-23 00:05:33 led-controller[1107]: <6> 288051 Start to run LAN_ON
2023-03-23 00:05:30 nat[26296]: <6> 211501 Initialization succeeded
2023-03-23 00:05:30 nat[26296]: <6> 211501 Initialization succeeded
2023-03-23 00:05:24 dhcpc[21340]: <6> 210054 receive ack from server with ip 24.19.39.134, options(serverid=96.113.84.143;lease=3600;subnet=255.255.252.0;router=24.19.36.1;dns=75.75.75.75 75.75.76.76;)
2023-03-23 00:05:24 dhcpc[21340]: <6> 210053 send select request with options(cliid=01/b4:b0:24:78:46:cd:;reqip=24.19.39.134;serverid=96.113.84.143;)
2023-03-23 00:05:24 dhcpc[21340]: <6> 210052 receive offer from server with ip 24.19.39.134, options(serverid=96.113.84.143;lease=3600;subnet=255.255.252.0;router=24.19.36.1;dns=75.75.75.75 75.75.76.76;)
2023-03-23 00:05:24 dhcpc[21340]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-03-23 00:05:23 dhcpc[21340]: <6> 210060 timed out, enter init state
2023-03-23 00:05:23 dhcpc[21340]: <6> 210053 send select request with options(cliid=01/b4:b0:24:78:46:cd:;)
2023-03-23 00:05:22 dhcpc[21340]: <6> 210053 send select request with options(cliid=01/b4:b0:24:78:46:cd:;)
2023-03-23 00:05:20 dhcpc[21340]: <6> 210053 send select request with options(cliid=01/b4:b0:24:78:46:cd:;)
2023-03-23 00:05:14 dhcpc[21340]: <6> 210053 send select request with options(cliid=01/b4:b0:24:78:46:cd:;)
2023-03-23 00:05:14 dhcpc[21340]: <6> 210059 timed out, enter rebinding state
2023-03-23 00:05:14 dhcpc[21340]: <6> 210058 1/2 lease passed, enter renewing state
2023-03-23 00:05:00 dhcpc[21340]: <6> 210054 receive ack from server with ip 192.168.100.11, options(subnet=255.255.255.0;router=192.168.100.1;lease=20;serverid=192.168.100.1;)
2023-03-23 00:04:59 dhcpc[21340]: <6> 210053 send select request with options(cliid=01/b4:b0:24:78:46:cd:;)
2023-03-23 00:04:59 dhcpc[21340]: <6> 210059 timed out, enter rebinding state
2023-03-23 00:04:59 dhcpc[21340]: <6> 210058 1/2 lease passed, enter renewing state
2023-03-23 00:04:45 dhcpc[21340]: <6> 210054 receive ack from server with ip 192.168.100.11, options(subnet=255.255.255.0;router=192.168.100.1;lease=20;serverid=192.168.100.1;)
2023-03-23 00:04:44 dhcpc[21340]: <6> 210053 send select request with options(cliid=01/b4:b0:24:78:46:cd:;)
2023-03-23 00:04:44 dhcpc[21340]: <6> 210059 timed out, enter rebinding state
2023-03-23 00:04:44 dhcpc[21340]: <6> 210058 1/2 lease passed, enter renewing state
2023-03-23 00:04:34 upnp[23428]: <6> 217504 Service start
2023-03-23 00:04:34 upnp[23428]: <6> 217505 Service stop
2023-03-23 00:04:31 remote-management[23074]: <6> 282505 Service stop
2023-03-23 00:04:30 dhcpc[21340]: <6> 210054 receive ack from server with ip 192.168.100.11, options(subnet=255.255.255.0;router=192.168.100.1;lease=20;serverid=192.168.100.1;)
2023-03-23 00:04:29 dhcpc[21340]: <6> 210053 send select request with options(cliid=01/b4:b0:24:78:46:cd:;)
2023-03-23 00:04:29 dhcpc[21340]: <6> 210059 timed out, enter rebinding state
2023-03-23 00:04:29 dhcpc[21340]: <6> 210058 1/2 lease passed, enter renewing state
2023-03-23 00:04:24 qos[22664]: <6> 259504 Service start
2023-03-23 00:04:24 qos[22664]: <6> 259503 Function disabled
2023-03-23 00:04:24 qos[22664]: <6> 259505 Service stop
2023-03-23 00:04:22 nat[21745]: <6> 211021 IPSEC ALG enabled
2023-03-23 00:04:22 nat[21745]: <6> 211021 L2TP ALG enabled
2023-03-23 00:04:22 nat[21745]: <6> 211021 PPTP ALG enabled
2023-03-23 00:04:22 nat[21745]: <6> 211021 SIP ALG enabled
2023-03-23 00:04:22 nat[21745]: <6> 211021 RTSP ALG enabled
2023-03-23 00:04:22 nat[21745]: <6> 211021 H323 ALG enabled
2023-03-23 00:04:22 nat[21745]: <6> 211021 TFTP ALG enabled
2023-03-23 00:04:22 nat[21745]: <6> 211021 FTP ALG enabled
2023-03-23 00:04:18 nat[21745]: <6> 211501 Initialization succeeded
2023-03-23 00:04:18 nat[21745]: <6> 211501 Initialization succeeded
2023-03-23 00:04:14 dhcpc[21340]: <6> 210054 receive ack from server with ip 192.168.100.11, options(subnet=255.255.255.0;router=192.168.100.1;lease=20;serverid=192.168.100.1;)
2023-03-23 00:04:13 dhcpc[21340]: <6> 210053 send select request with options(cliid=01/b4:b0:24:78:46:cd:;reqip=192.168.100.11;serverid=192.168.100.1;)
2023-03-23 00:04:13 dhcpc[21340]: <6> 210052 receive offer from server with ip 192.168.100.11, options(subnet=255.255.255.0;router=192.168.100.1;lease=20;serverid=192.168.100.1;)
2023-03-23 00:04:13 dhcpc[21340]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-03-23 00:04:10 dhcpc[21340]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-03-23 00:04:07 dhcpc[21340]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-03-23 00:04:07 led-controller[1107]: <6> 288051 Start to run WAN1_OFF
2023-03-23 00:04:07 led-controller[1107]: <6> 288051 Start to run WAN0_ON
2023-03-23 00:04:07 led-controller[1107]: <6> 288051 Start to run LAN_ON
2023-03-23 00:03:53 dhcpc[20305]: <6> 210056 teardown and release
2023-03-23 00:03:53 dhcpc[20305]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-03-23 00:03:53 led-controller[1107]: <6> 288051 Start to run WAN1_OFF
2023-03-23 00:03:53 led-controller[1107]: <6> 288051 Start to run WAN0_OFF
2023-03-23 00:03:53 led-controller[1107]: <6> 288051 Start to run LAN_ON
2023-03-23 00:03:50 dhcpc[20305]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-03-23 00:03:47 dhcpc[20305]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-03-23 00:03:47 led-controller[1107]: <6> 288051 Start to run WAN1_OFF
2023-03-23 00:03:47 led-controller[1107]: <6> 288051 Start to run WAN0_ON
2023-03-23 00:03:47 led-controller[1107]: <6> 288051 Start to run LAN_ON
2023-03-23 00:03:33 led-controller[1107]: <6> 288051 Start to run WAN1_OFF
2023-03-23 00:03:33 led-controller[1107]: <6> 288051 Start to run WAN0_OFF
2023-03-23 00:03:33 led-controller[1107]: <6> 288051 Start to run LAN_ON
2023-03-23 00:03:32 dhcpc[14271]: <6> 210056 teardown and release
2023-03-23 00:03:08 dhcpc[14271]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-03-23 00:02:38 dhcpc[14271]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-03-23 00:02:29 led-controller[1107]: <6> 288051 Start to run WAN1_OFF
2023-03-23 00:02:29 led-controller[1107]: <6> 288051 Start to run WAN0_ON
2023-03-23 00:02:29 led-controller[1107]: <6> 288051 Start to run LAN_ON
2023-03-23 00:02:07 dhcpc[14271]: <6> 210051 send discover with ip 0.0.0.0 and flags 0
2023-03-23 00:01:42 dhcpc[14271]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-03-23 00:01:39 dhcpc[14271]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-03-23 00:01:37 led-controller[1107]: <6> 288051 Start to run WAN1_OFF
2023-03-23 00:01:37 led-controller[1107]: <6> 288051 Start to run WAN0_ON
2023-03-23 00:01:37 led-controller[1107]: <6> 288051 Start to run LAN_ON
2023-03-23 00:01:36 dhcpc[14271]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-03-23 00:01:33 led-controller[1107]: <6> 288051 Start to run WAN1_OFF
2023-03-23 00:01:33 led-controller[1107]: <6> 288051 Start to run WAN0_OFF
2023-03-23 00:01:33 led-controller[1107]: <6> 288051 Start to run LAN_ON
2023-03-23 00:01:31 led-controller[1107]: <6> 288051 Start to run WAN1_OFF
2023-03-23 00:01:31 led-controller[1107]: <6> 288051 Start to run WAN0_OFF
2023-03-23 00:01:31 led-controller[1107]: <6> 288051 Start to run LAN_OFF
2023-03-23 00:01:29 led-controller[1107]: <6> 288051 Start to run STATUS_ON
2023-03-23 00:01:28 qos[13623]: <6> 259504 Service start
2023-03-23 00:01:28 qos[13623]: <6> 259503 Function disabled
2023-03-23 00:01:27 led-controller[1107]: <6> 288051 Start to run GENERAL
2023-03-23 00:01:22 traffic-stats[12794]: <6> 269504 Service start
2023-03-23 00:01:08 factory-reset[11433]: <6> 284504 Service start
2023-03-23 00:01:07 parental-control[11098]: <6> 229504 Service start
2023-03-23 00:01:07 parental-control[11098]: <6> 229502 Function enabled
2023-03-23 00:01:05 access-control[10883]: <6> 239504 Service start
2023-03-23 00:01:05 access-control[10883]: <6> 239503 Function disabled
2023-03-23 00:01:03 nat[10322]: <7> 211001 Flush conntrack
2023-03-23 00:01:03 nat[10322]: <6> 211502 Function enabled
2023-03-23 00:01:02 nat[10322]: <5> 211051 Create NAT chain succeeded
2023-03-23 00:01:00 nat[10322]: <6> 211501 Initialization succeeded
2023-03-23 00:01:00 nat[10322]: <6> 211501 Initialization succeeded
2023-03-23 00:00:58 basic-security[9822]: <6> 219504 Service start
2023-03-23 00:00:58 basic-security[9822]: <5> 219606 Flush conntrack table succeeded
2023-03-23 00:00:56 firewall[9072]: <6> 209504 Service start
2023-03-23 00:00:27 led-controller[1107]: <6> 288051 Start to run WIFI5G_ON
2023-03-23 00:00:27 led-controller[1107]: <6> 288051 Start to run WIFI2G_ON
2023-03-23 00:00:10 imb[2742]: <6> 218507 Daemon connection succeeded
2023-03-23 00:00:10 imb[2742]: <6> 218012 ARP Binding disabled
2023-03-23 00:00:10 imb[2742]: <6> 218506 Config interface initialization succeeded
2023-03-23 00:00:10 imb[2742]: <6> 218501 Initialization succeeded
2023-03-23 00:00:09 upnp[2546]: <6> 217504 Service start
2023-03-23 00:00:08 upnp[2546]: <6> 217505 Service stop
2023-03-23 00:00:06 remote-management[2193]: <6> 282505 Service stop
2023-03-23 00:00:05 dhcpc[1976]: <6> 210056 teardown and release
2023-03-23 00:00:05 dhcpc[1976]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-03-23 00:00:00 time-settings[1277]: <6> 279504 Service start
1970-01-01 00:00:32 led-controller[1107]: <6> 288051 Start to run STATUS_SAN
1970-01-01 00:00:31 led-controller[1107]: <6> 288504 Service start
- Copy Link
- Report Inappropriate Content
Hello @thechez
What kind of modem are you connecting the AX55 to? Can we have its model number?
There seems to be another modem or router in the network that handles the DHCP requests, which is why the AX55 fails to get internet access.
BTW, was the internet on the AX55 working fine with the previous beta firmware?
- Copy Link
- Report Inappropriate Content
Galicia86 wrote
FYI, homeshield security, no longer works.
Can you please describe the HomeShield issue you are experiencing in detail?
Please try to export and back up the settings on the AX55, reset the router to factory defaults, then re-upload the settings back into the router to confirm if you can make the HomeShield work again.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Thank you very much for the screenshots.
Please try unblinking the AX55 from your TP-Link account, and re-linking it to check if you can get the HomeShield security to work again.
If still fails, please email support.forum@tp-link.com with the following details:
1. Your TP-Link ID.
3. Tether App version.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
I've installed the beta firmware to support wireguard, however am getting very slow speeds while connecting the vpn client. My connection is about normally about 500mbps even whilst having the vpn running on my computer. however after using vpn client im getting speeds of about ~90mbps
- Copy Link
- Report Inappropriate Content
Information
Helpful: 12
Views: 32639
Replies: 109
Voters 4
