Archer BE800 V1 Support for VPN Merge, Guest/IoT Network Extension via EasyMesh, and More!

Archer BE800 V1 Support for VPN Merge, Guest/IoT Network Extension via EasyMesh, and More!

33 Reply
Re:Archer BE800 V1 Support for VPN Merge, Guest/IoT Network Extension via EasyMesh, and More!
a week ago

  @Ryan Just noticed this.  Lost power, when router rebooted MLO network are not shown as available.  Had to go into the router settings and disable/enable it to be seen again. Verified by turning off router and when it came back on the MLO netwrok was not available until I disabled/enabled again.

1
1
#32
Re:Archer BE800 V1 Support for VPN Merge, Guest/IoT Network Extension via EasyMesh, and More!
a week ago - last edited a week ago

  @DVair 

 

Thanks for the feedback―and for taking the initiative to reproduce the behavior. Will send this up to the teams.  👍 

Make Your Home Wi-Fi Greener with Power-Saving Features Check out Our Community Newsletter and Monthly Firmware Updates in our Knowledge Base Contact Support Join our Official Subreddits: , r/tplink, r/tapo, r/omada_networks
0
0
#33
Re:Archer BE800 V1 Support for VPN Merge, Guest/IoT Network Extension via EasyMesh, and More!
a week ago

  @Ryan 

 

This is not fully unique to this beta fw but is a bug and it does translate into impacting a new features as well so you can make the line that it's a bug and kill 2 birds with one stone maybe?

 

I have BE800 in AP mode setup as main for EasyMesh

I have 2x BE400 setup via wire backhaul as extenders in this mesh.

 

In the BE800 it never shows clients connected to the BE400's despite they are.

 

One impact on the new features, binding can't work.

I can't go to the BE400 via the main unit and bind anything because it shows no clients on them. It only appears to show clients on the BE800 (which I guess you can bind those items but isn't really helpful if you want to bind something to an extender).

IF I go direct to the webUI of the BE400 and look at clients I can see the ones connected to it but binding isn't supported at this layer, only the main can control.

 

Similar bug exist in the tether app. It does not ever think anything is connected to the extenders despite items are.

 

I suspect the heart of the issue is AP Mode support seems to not be implemented properly still with something. I've not previously reported this as not the end of the world but now with a nice new feature I'd like to use, it has merrit to being fixed.

 

I am happy to report the other features do seem to work well now though such as IoT and Guest syncing.

 

So now just need AP mode fixed for where clients are connected :)

 

Another "nice" to have thing would be is if WPA3 Enterprise could be supported. Currently only WPA2 Enterprise is on main SSID. Would also love to see guest network allow us to select protection like main and IoT and not be limited. For example I want to force WPA2 only on guest but not an option.

0
0
#34