@JustinW 

Had a similar issue with my Roberts radio. Router wasn't giving the radio an ip address. Same as above i chaned the security setting and radio came on. Went back to original wpa2 and radio stayed on. Also gave radio a  reservation  or static ip. Worked ever since.

I had the same problem

Hi, My 2.4 network was already set to Wpa2-psk and aes (aes is the only option available in this firmware it seems). I tried the guest network setting (although guest networks are disabled). With no luck. I’ll try the firmware later when my Family aren’t using the network. Justin

@JustinW I got my router 5 days ago and from day one  I faced a lot of issues : 

1- WIFI not stable sometimes will not work and I must reset my Wi-Fi on my iPhone device.

2-OPENVPN seems not working after setting it up everything when I export the config file the remote server it shows my public IP instead of the dynamic domain name.

3-Theere is no login authentication to the VPN sever therefore if anyone get the config file and load it in his device, he will be able to connect to my VPN / network.

2-DHCP lease time now limited to 3 days only I recommend this to be maximum of 7 days. 

3-There is no network ports status page to show the details of which ports are in use and what is the link speed.

4-The IP reservation in the DHCP I have too added manually but and a lot of new router when you display the connected devices click on the IP address it will show you a list of option for the same IP , i.e. Block IP , reserve it in DHCP , limit the internet speed .. etc. 

4-For the VPN SSL why you do not integrate, and use Lets Encrypt free SSL instead of using local generated SSL certificate.

 

I hope someone from TP-Link to share these issues to their firmware developers’ team:

 

Thank you

 

So, the beta firmware provided seems to have solved the problem, all my Sonos devices are working directly connected to the AX6000.

 

I'll see what the stability is like during the next few days and report back!

 

It would be great to know when the firmware moves from beta to full release, or the fixes go into a new release.

 

Thanks!

 

Justin

So far this build seems better, I've had some cases where an airport express, acting as an airplay2 gatway has had some drop outs. This connects on 2.4Ghz. But this hasnt occurred with the Sonos devices as yet. 
 

luckily, I'm not facing the issues these guys are with what I think is the same version. 
 

https://community.tp-link.com/en/home/forum/topic/210860?page=5

 

I'm going to set up some monitoring with telegraf to see if I have any drops on 5GHz

 

have noticed a problem with one windows 7 laptop with an intel adapter that wont connect if ax is on. So I turned that off on 2.4 for now. I don't know if thats new with this beta firmware. May look at driver updates there. 

Is the beta firmware for the EU region or just US? I have the same problems with 5 GHz and thought it might be worth trying. Thanks

@Transmission1 

 

I'm based in the UK, and it worked fine for me. Haven't checked which channels etc are available, suspect that would be the main reason for the regionalisation. 
 

Justin

This is still quite fragile. 
 

I decided to split my ssids (most of my devices were sticking to 2.4 most of the time). I dont use smart connect due to its documented behaviour on tp-link of only switching devices between networks every 24 hrs. 
 

so I renamed the 5Ghz network, assuming this would not impact the 2.4 Ghz. i could connect my phone to either network. 
 

However, Iimmediately lost the ability to see my sonos kit, and an airport express I was using as an airplay2 adaptor. My phone was connected to the new 5Ghz network at this point. (I didnt try connecting via 2.4 at this point, wish I had). 
 

so I switched the 5Ghz name back to match the 2.4 name. At this point the config was exactly the same as before. 
 

still couldn't see the sonos and airplay devices even with my mobile on 2.4. 

router reboot didnt help. 

 

I toggled the guest network isolation (which has been suggested before.) with no luck. 
 

in the end, locking the 2.4 to ch6 20 mhz brought it all back (this was set to auto before -when it was working). 
 

Its almost like config changes corrupt other parts of the config or have unintended consequences. 
 

I'm beginning to think about returning the router (but may have an issue with this, having flashed it, and had it for more than 14 days). Not impressed so far.