@Sunshine Hello, does this FW fix also issues with shared storage? Share over SMB randomly fails with error 0x80070032 (more is here https://community.tp-link.com/en/home/forum/topic/612704) and DLNA (or Media share) is completely broken. Media share doesn't recognize most of the movies despite all of the movies have supported format. Also browsing is spoiled as it shows multiple times the same folder names.

  @Sunshine 

Great news! Will a new firmware that improves OpenVPN performance be available for AX53 also?

  @Sunshine 

I just uploaded the firmware to my AX55 test router and to an AP mode AX55 on my local network.  More than an hour has passed and I noted the following:

1.  An iPhone5 was connected to the AX55 test router on the 2,4 Ghz main network for about 45 minutes.  The IPhone Wifi was then turned off.  The test router still shows the iPhone as a connected client after half an hour so it would appear that the Connected Clients list is not updatng properly.

2. All of the wireless clients connecting to the AP mode router (a large mix of IoT devices, cameras, iPhones, etc.) are displaying the same icon (a circle with three dots). It appears the client identification feature is not working in AP mode, at least with the icons.

UPDATE:

1.  After leaving the test router on all night, this morning the clients list still shows the iPhone5 as connected.

2.  A connection was established with an iPhone8 on the test router.  For the device name, the list displays "network device".  Not knowing how precise the client identification feature is supposed to be, I don't know if this normal or not.  The icon is a circle with 3 dots just like what appears on the AP router with all the devices.

.

3.  The main router was just upgraded with the beta firmware. Most connected devices display the circle icon as mentioned above. Three Reolink cameras display a computer icon as does one of two PCs. One PC (an iMac running Windows) displays the computer icon correctly while another PC (an HP All-In-One desktop) displays the circle icon. Four Amazon Echo devices all display an icon which resembles a tablet.  Finally, one air conditioner (Daikin) displays a hexagon icon with what looks like a fan blade in the center. The other air conditioner is connected via the access point which has the icon problem mentioned above.

  @Sunshine 

The private address was enabled. After disabling it, the old name reappeared that had been configured previously.  The icon also changed from a circle to a cellphone.  I will have to check all my iPhones and iPads to see if they are configured for a private address.  Thanks for the suggestion.

  @Sunshine 

New Update:

The AX55 router has been up and running for a little over an hour.  The icon has changed back to a circle on almost all of the devices.  Only the iMac, the old iPhone 5, and two first generation iPads are still showing the correct icon.

  @Sunshine 

Following up to my previous posts, I would like to add the following comments:

1.  After several days with the beta firmware, I have experienced problems where three different PCs (an iMac running Windows, an HP laptop, and an HP desktop) do not obtain an IP address from the router after being powered off for a prolonged period.  The DHCP is not working properly.  The router appears to be connected to the internet as evidenced by its green lights and by devices already connected such as SIP telephones.  To get the PC connected, I must manually assign an IP address, establish the connection, and then change the connection back to DHCP.

2.  Not being familiar with Fing, I decided to download the Fing desktop version to see what its capabilities are regarding client identification.  At first, I could not even get the program to execute on two PCs, but I finally got it to run on the HP desktop.  I was rather disappointed when Fing could only identify some 13 devices out of more than 25 on my LAN.  The identification that it did perform was only partial, usually giving me just the manufacturer’s name.  For example, it could not identify any Reolink IP cameras, Daikin air conditioners, Echo devices, Devolo non-WiFi PLC devices, and even some TP-Link routers such as the TL-WR840N.  If their own software can not properly (or accurately) identify these LAN devices, then one must think that the TP-Link firmware can do no better.  Something else that I do not like is the idea of having to generate traffic to third-part servers for device identification.

3.  Due to the connection problems mentioned above and seeing that the client identification is not really any better than with the current firmware, I downgraded the firmware in all my routers back to the current 1.2.3 version.  That, in itself, wasn’t easy either as the normal upgrade process doesn’t work when trying to go back to the previous version.  Fortunately, I found the needed information for downgrading on the TP-Link website.

4.  My recommendation to TP-Link would be to not implement (for now) the supposed client identification features of Fing.  If those features are going to be implemented, then provide an option, such as “Enhanced Client Detection” that can be disabled if the end user does not need it or want to use it.

  @Sunshine 

Ethernet cable backhaul for mesh please :(