Hello, I found two errors or problems in this new firmware, using the VPN Client and doing the manual configuration (since I use Kaspersky VPN for Routers, and TP-Link doesn't provide official support), but anyway, we already know that TP-Link doesn't use IPv6 in its VPN, so when I configure it, the clients I activate to use the VPN automatically only use the VPN's IPv4 address. I think this is a complete waste, as we know that practically all websites in the world use IPv6, but okay. The problem, besides disabling IPv6 when using the VPN with only IPv4, gets even worse because when I restart the AX80, it simply has a problem with the VPN using the VPN's own IPv4 address (not my internet provider's), but uses the ISP's IPv6 address, making the connection weak and partially useless, as the traffic leaks through the ISP's IP address. So I ask that you look into this and correct it; it's quite serious for those who value VPN use. If needed, I can send a video or photos showing the error. Thank you in advance.

And the other problem I noticed in this new firmware is that the 5GHz power has decreased. We know it supports transmitting at 30dBm, but in this new version it's transmitting at 22dBm. The 2.4GHz is transmitting at At 22dBm, something is wrong with that. My AX72 for example, are also from the US and transmit at 5GHz - 24dBm and 2.4GHz - 29dBm. That's strange with the AX80. I noticed this because it reduced the quality and coverage distance of the 5GHz. And I didn't have ECO mode activated, nor any other type of power saving; everything is deactivated. My only criticisms are these; otherwise, the update is wonderful, congratulations. 

# Edit

The TP-Link website itself states that it transmits 30dBm, so I ask that you please review this

# Edit 2

I found another bug. During the initial setup, when I set the time zone and click "next," the next page is for choosing the connection type. In the previous firmware version, there was an automatic detection button so the router could detect the connection itself. In this new update, the button has simply disappeared. So there's another bug.

Thank you.