New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More

New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More

155 Reply
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
5 hours ago

  @raq50 ,

Thanks for your reply.

You downloaded the BE800 firmware twice in total, right? That is, the first version and the latest version.

  0  
  0  
#157
Options
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
5 hours ago

Hi  @Joseph-TP

 

Yes, that is correct. I only downloaded the firmware twice: first the special SFP beta from the previous thread (Build 202511xx), and then this latest Build 20260313. I upgraded directly from the SFP beta to the current one.

  0  
  0  
#158
Options
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
4 hours ago - last edited 4 hours ago

Hi  @Joseph-TP

 

I found another critical bug in this beta version. I am unable to save any changes in the Wireless Settings menu (even simple things like changing Transmit Power).

Whenever I try to click "Save", I get two errors:

  1. A popup saying: "The name already exists, please set a different network name."

  2. A top bar notification: "Operation failed."

It seems the firmware's validation logic is conflicting with itself because I use the same SSID ("BACKBONE") for Main, 6GHz, and MLO networks (which worked perfectly in previous versions). Currently, the router is "locked" and won't allow any configuration updates.

I have attached screenshots of these errors. This is making further testing very difficult as I cannot adjust the network parameters.

 

I found a workaround for the saving issue. It turns out that having the same SSID ("BACKBONE") for both the Main Network and the MLO Network causes a validation error: "The name already exists, please set a different network name."

After changing the MLO SSID to something different (e.g., "BACKBONE_MLO"), I am finally able to save wireless settings again. This seems to be a bug in the SSID validation logic of the current beta build.

Please investigate why the firmware no longer allows unified SSIDs across MLO and Main networks, as this worked in previous versions.

  0  
  0  
#159
Options
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
4 hours ago - last edited 4 hours ago

  @Joseph-TP 

 

I have confirmed that the "Traffic Separation" setting can be saved ONLY IF the MLO Network SSID is different from the Main Network SSID.

It appears the firmware has a validation bug that blocks all "Save" operations if there is an SSID name conflict, even though it doesn't explicitly highlight the MLO field as the cause.

However, even after successfully saving "Traffic Separation" with the workaround, I still need to verify if the Guest Network is correctly reaching the BE550 satellites.

 

I have successfully resolved the issue! It turns out there is a UI Validation Bug in the BE800 Build 20260313.

The Problem: > When the Main Network SSID and the MLO Network SSID are identical (e.g., both named "BACKBONE"), the router throws an "Operation failed" error and blocks all wireless settings from being saved. This also prevented the "Traffic Separation" toggle from working.

The Solution/Workaround: > I changed the MLO Network SSID to a different name (e.g., "BACKBONE_MLO"). After this change, the router allowed me to save settings.

The Result: > Once "Traffic Separation" was successfully saved, the Guest Network immediately started working on the Archer BE550 V2 satellites without any issues!

Please ask the engineers to fix the SSID validation logic so that we can use unified SSIDs for both Main and MLO networks again, as we could in previous versions.

  0  
  0  
#160
Options
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
3 hours ago

  @Joseph-TP 

I think it could also help if the router shows more detailed system logs for connection drops. Right now it is hard to understand if the issue is from firmware, interference, or device behavior. Even a simple timeline of events (like reconnects, DHCP renew, or band switching) would make troubleshooting much easier for users.

  0  
  0  
#161
Options