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

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

  @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
Yesterday

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.

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

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
Yesterday - last edited Yesterday

  @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.

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

  @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
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
Yesterday

Hi @raq50 

Thank you so much for your feedback.

I will sync all your test results to the engineer. 

 

@Bluefish91  Have you set MLO Network SSID to the same as the Main network SSID? Would you mind testing whether changing the MLO SSID to a different one can help?

raq50 wrote

  @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  
#166
Options
Re:New Firmware for Archer BE800 V1 to Support VPN Merge,Guest/IoT Network Extend in EasyMesh, and More
Yesterday

  @Szaki26a ,

Thanks for contacting our community.

 

Did this anomaly only occur after this update?

You previously mentioned that UPnP data still cannot be retained. Has this been resolved?

I noticed your case has been escalated to the engineer via TKID260251424.  You can also reply to the engineer with details.

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

  @Joseph-TP 

Hello

 

I think it's the same issue. When the firmware upgrade happens, the router's UPnP list is lost. This isn't a new problem — I'm mentioning it to say it's still not fixed and could be serious, because devices only renegotiate UPnP when they reboot or reinitialize. That may explain why smart-home accessories stop working or behave strangely.

 

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

  @Joseph-TP 

Hello!

 

Today i've decided to swap my VSOL ONU with ODI DFP-34X-2C2 ONU stick. The stick should support up-to 2.5G speeds, but only negotiate at 1Gbps. Restart of the SFP+ stick or router doesn't help. In router webinterface it is always showing 1000Mbps. I'm on the latest BE800 beta firmware. Is there any fix for that?

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

  Hi @marto74bg,

 

Just to provide another data point: I am also using the latest Archer BE800 V1 beta firmware (Build 20260313), and my SFP+ connection is working perfectly at full speed.

I am using a different module: an "XGSPON ONT SC/APC XGSPON SSH STICK ONU SFP+ 10G", and the router correctly negotiates at 10 Gbps Full Duplex without any issues.

As you can see in my attached screenshot (Ethernet Status), the 10Gb negotiation is stable on this build. It seems the router's SFP+ port is capable of higher speeds on this firmware, so your issue with the ODI stick (limiting to 1Gbps instead of 2.5Gbps) might be a specific module compatibility or negotiation link rate issue.

Hope this helps!

 

  1  
  1  
#170
Options