New Release Introducing New HomeShield Firmware for Archer AX55
Hello Community,
Happy to inform you the new firmware for Archer AX55 V1 has been publicly released now. This new version makes important updates for HomeShield Pro services as well as a lot more features. 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:
Archer AX55_V1_1.2.2 Build 230511 (official firmware updated on 6/9/2023)
New Features/Enhancement:
1. Added Wireguad VPN feature.
If you wonder how to use WireGuard VPN feature with the router, check this previous thread.
2. Added lots of Advanced features to AP mode.
Important: Once changing the AX55 to work in AP mode, you won't be able to enjoy or configure HomeShield anymore.
- With this version, you will get an IoT network when the AX55 is working in Access Point Mode.
- You can configure Wireless Schedule for the wireless network.
- You could enable or disable WPS.
- You could configure Access Control for the network.
3. Added Flow Control switch.
4. Supported configuring the local DNS server as the Internet DNS server.
5. Optimized VPN client feature.
6. Optimized web UI of some advanced functions.
7. Improved the accuracy of Client Type Identification in the offline state.
8. Enhancing the Parental Control feature to support blocking traffic in more scenarios.
Bug Fixes:
1. Fixed the bug that caused Apple devices to be recognized as "unknown" devices at times.
2. Fixed some bugs related to the HomeShield feature, which enhances the stability and reliability of the network security function.
Welcome to upgrade and install this pre-released version on your Archer AX55, and feel free to report back to us with bugs, faults, errors, and your thoughts on how to improve.
Related Articles:
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Kevin_Z yes, I have installed the beta firmware earlier. Usually, the problem occurs after a few hours each power cycle of AX55. Will let you know if it resolved the issue tomorrow.
- Copy Link
- Report Inappropriate Content
I just upgraded the beta firmware on my test router. The IoT connections appear to be working OK now in the AP mode. I will continue testing throughout the day.
One issue however... After the reboot following the upgrade, the internet LED remains orange and the Internet Status of the web interface shows a red exclamation point. The internet connection however is OK and there is no problem navigating. The AP is using the WAN port to connect to the ISP's router. After upgrading a second AX55, it has the same issue when operating in AP mode.
After changing the test router back to Wireless Router mode from AP mode, the internet LED is now green and the web interface shows the usual checkmark. Therefore this orange LED issue is only occurring in AP mode.
- Copy Link
- Report Inappropriate Content
Thank you very much for the feedback on the beta firmware.
For the LED display orange issue when the AX55 is working in AP mode, we will report it to the development team and ask them to review the firmware.
- Copy Link
- Report Inappropriate Content
Minor bug with counting Mesh Devices
Scenario: My AX55 test router is operating in the Wireless Router mode. One RE700X range extender has been connected to the router in an EasyMesh configuration for some 24 hours with no problems.
After adding a second extender, this time an RE605X V1 (not EasyMesh compatible but OneMesh compatible), everything appeared to be OK. The RE605X showed up on the list in the AX55’s Network Map after selecting Mesh Devices. However, the number of devices in the circle above the list remained at 1 and never changed to 2. The number of “Satellite Devices” was correct on the EasyMesh page under Advanced.
To investigate this further, the RE605X was replaced with another RE700X. With 2 RE700X extenders, the numbers were correct on both web pages.
Again, the RE605X was added to the network after removing one of the RE700X extenders. And again, the number of Mesh Devices was incorrect on the Network Map page.
I remember the count being correct with earlier AX55 firmware, but I don’t remember just exactly which version. More recently I have not been using the RE605X as I replaced it with an RE700X. In any case, the number of mesh devices should be correct, whether OneMesh or EasyMesh, as the AX55 supports both,
- Copy Link
- Report Inappropriate Content
@Kevin_Z the beta firmware works that it doesnt drop the wireless connection anymore on the AX55. Thanks!
- Copy Link
- Report Inappropriate Content
Hello,
With the last version ( 1.2.2 Build 230511) Sometimes I see that I lose the internet connection.
Sometimes once a week and sometimes every days (between 8 pm and 6 am generally but not always).
I had that problem before the first beta (with wireguard) but only one a month so it was not important.
I am sure that the problem is with the AX55 because the phone was still working (RJ11 on the modem by voip) and after restarting the AX55 all was fine.
At the moment I have tried to force the unicast for the DHCP (in the advanced settings). I have no idea if it will help or not.
Would you have an idea?
Thank you
In the syslog I have
2023-05-11 00:00:10 imb[2820]: <6> 218506 Config interface initialization succeeded
2023-05-11 00:00:10 imb[2820]: <6> 218011 ARP Binding enabled
2023-05-11 00:00:10 imb[2820]: <6> 218506 Config interface initialization succeeded
2023-05-11 00:00:10 imb[2820]: <6> 218501 Initialization succeeded
2023-05-11 00:00:09 upnp[2678]: <6> 217504 Service start
2023-05-11 00:00:09 upnp[2678]: <6> 217505 Service stop
2023-05-11 00:00:07 remote-management[2266]: <6> 282505 Service stop
2023-05-11 00:00:05 dhcpc[1993]: <6> 210056 teardown and release
2023-05-11 00:00:05 dhcpc[1993]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-05-11 00:00:00 time-settings[1286]: <6> 279504 Service start
1970-01-01 00:00:32 led-controller[1118]: <6> 288051 Start to run STATUS_SAN
1970-01-01 00:00:31 led-controller[1118]: <6> 288504 Service start
2023-05-11 00:00:10 imb[2820]: <5> 218021 IP 192.168.1.122 and MAC 00-15-5D-XX-XX-XX bound succeeded
2023-05-11 00:04:44 dhcpc[18717]: <6> 210051 send discover with ip 0.0.0.0 and flags 0
2023-05-11 00:04:13 dhcpc[18717]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-05-11 00:03:43 dhcpc[18717]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-05-11 00:03:37 led-controller[1118]: <6> 288051 Start to run WAN1_OFF
2023-05-11 00:03:37 led-controller[1118]: <6> 288051 Start to run WAN0_ON
2023-05-11 00:03:37 led-controller[1118]: <6> 288051 Start to run LAN_ON
2023-05-11 00:03:12 dhcpc[18717]: <6> 210051 send discover with ip 0.0.0.0 and flags 0
2023-05-11 00:02:47 dhcpc[18717]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-05-11 00:02:44 dhcpc[18717]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-05-11 00:02:42 led-controller[1118]: <6> 288051 Start to run WAN1_OFF
2023-05-11 00:02:42 led-controller[1118]: <6> 288051 Start to run WAN0_ON
2023-05-11 00:02:42 led-controller[1118]: <6> 288051 Start to run LAN_ON
2023-05-11 00:02:41 dhcpc[18717]: <6> 210051 send discover with ip 0.0.0.0 and flags 80
2023-05-11 00:02:39 led-controller[1118]: <6> 288051 Start to run WAN1_OFF
2023-05-11 00:02:39 led-controller[1118]: <6> 288051 Start to run WAN0_OFF
2023-05-11 00:02:39 led-controller[1118]: <6> 288051 Start to run LAN_ON
2023-05-11 00:02:36 led-controller[1118]: <6> 288051 Start to run STATUS_ON
2023-05-11 00:02:35 qos[18006]: <6> 259504 Service start
2023-05-11 00:02:35 qos[18006]: <6> 259503 Function disabled
2023-05-11 00:02:34 led-controller[1118]: <6> 288051 Start to run GENERAL
2023-05-11 00:01:41 traffic-stats[14255]: <6> 269504 Service start
2023-05-11 00:01:22 factory-reset[12680]: <6> 284504 Service start
2023-05-11 00:01:20 parental-control[12041]: <6> 229504 Service start
2023-05-11 00:01:20 parental-control[12041]: <6> 229502 Function enabled
2023-05-11 00:01:16 access-control[11742]: <6> 239504 Service start
2023-05-11 00:01:16 access-control[11742]: <5> 239606 Flush conntrack table succeeded
2023-05-11 00:01:16 access-control[11742]: <6> 239502 Function enabled
2023-05-11 00:01:13 nat[11199]: <7> 211001 Flush conntrack
2023-05-11 00:01:13 nat[11199]: <6> 211502 Function enabled
2023-05-11 00:01:13 nat[11199]: <5> 211051 Create NAT chain succeeded
2023-05-11 00:01:11 nat[11199]: <6> 211501 Initialization succeeded
2023-05-11 00:01:10 nat[11199]: <6> 211501 Initialization succeeded
2023-05-11 00:01:09 basic-security[10719]: <6> 219504 Service start
2023-05-11 00:01:09 basic-security[10719]: <5> 219606 Flush conntrack table succeeded
2023-05-11 00:01:07 firewall[10004]: <6> 209504 Service start
2023-05-11 00:00:29 led-controller[1118]: <6> 288051 Start to run WIFI5G_ON
2023-05-11 00:00:29 led-controller[1118]: <6> 288051 Start to run WIFI2G_ON
2023-05-11 00:00:10 imb[2820]: <6> 218507 Daemon connection succeeded
- Copy Link
- Report Inappropriate Content
Can you please confirm some details with regard to the 1.2.2 Build 230511? And if possible, it's suggested to install the latest beta firmware that we provide here last week.
If the internet still drops, please help confirm the below detail:
1. Who is your ISP, and what kind of WAN Connection Type you're using on the AX55?
2. Do you connect any EasyMesh or Onemesh extenders to the network? How many extenders? What are the models?
Note: If there are EasyMesh or Onemesh extenders in the network, please verify if the devices are connected to the AX55 wireless network or connected to the extenders' when they drop the internet.
3. Do you remember the previous stable version of firmware for AX55? Is it the previous 1.1.8 version?
4. How about the LED status on the AX55 when the internet drops on some wireless client devices? Can you login to the web management page of the AX55 when there is no internet on the wireless clients but it still shows connected to the network?
If the dropping issue doesn't come with the AX55 firmware update, please follow these troubleshooting suggestions to solve it:
Troubleshooting: Unstable wireless connection on TP-Link router
Thank you very much.
- Copy Link
- Report Inappropriate Content
Hello,
Please pay attention that it is not a problem with the WIFI. I have the problem with a RJ45 cable too (Wifi and RJ45)
1) My ISP is Voo (Cable modem).
I have my voo modem in bridge mode (there were problems with Wireguard (wrong IP adress) so I decided to bridge my ISP modem
My WAN is of type Dynamic IP (assigned by the ISP and officiously fixed if I am not disconnected less than 24 hours) (it is a real IP and not behind a VPN)
2) I have tried to add a "Archer C6" as onemesh / easymesh and it didn't work (not compatible) so I have added one as a wifi hotspot (second network).
3) With the AX55 I never had a 100% stable version (I had to restart every 1-2 month) so I activated the automatic reboot.
I would say that with the first Wireguard version (February 2023) I started having problems but it could be problems because of the bridge and not the router too (clicking on Renew crashes my ISP router and I must restart it again)
4) The internet connection light is orange The Interface is responding (really slowly, sometimes I have to wait 20-30 sec. when accessing with IP address (192.168.1.1) then there is an error (talking about tplinkwifi.net ) and I must force it a second time 192.... and it works again (very slowly or it doesn't work too) and I power down the AX55 and power it back up.
EDIT : I will report with the new firmware in a few days but at the moment I have no more problem.
Thank you
Marc
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hello,
Yes I have upgraded and I had no problem with the internet connexion going down for 2 days. (I have no idea if it is because I have checked the Get IUP using Unicast or because the update).
The only "small problem" that stays is that when I connect to the router with my router ip address and I enter the password it tries to use tplinkwifi.net and not the ip address. I enter back the ip address and it works back again.
But at the moment all is perfect. Thank you
EDIT : At the moment still no problem.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 6
Views: 8038
Replies: 44
Voters 1