David-TP wrote

This Article Applies to:

Deco XE75(US/EU/AU/CA)_V2/V3
Deco XE5300(US)V2/V3

Deco WE10800(US)V2/V3
Deco XE75 Pro(US/EU/AU/CA)_V2/V3
Deco XE70 Pro(US)_V3

Vx.0=Vx.6(eg:V2.0=V2.6)

 

Firmware Modifications:

• Added Camera Security.
• Added Whitelist/ Wi-Fi Access Control to support Allow List and Block List
• Supported Captive Portal for Guest Network.
• Supported Firmware Auto Update.
• Supported ECO Mode 1.0 to save power.
• Supported WireGuard VPN.
• Integrated third-party VPN services.
• Supported limiting client speeds.
• Supported fixing a specific port as the WAN port.
• Optimize client type recognition.
• Support managing new Kasa and Tapo product categories (including light strips, multi-port outlets, etc.).

 

Download Links

Deco XE75/XE5300/WE10800_V2/V3	1.4.0_Build_20260130_Beta
Deco XE75 Pro/XE70 Pro_V2/V3	1.4.0_Build_20260130_Beta

Update Notice:

• Please be sure you have read the Beta Test Agreement before upgrading the Pre-release firmware!
• Please make sure the Deco APP is up-to-date.
• The Beta firmware versions can’t be degraded directly to the previous 1.3.1/1.2.9, etc. versions.
• How to manually update the firmware via web UI.

As always, we value your feedback. If you happen to encounter any concerns during or after the firmware upgrade, please feel free to comment below with the following information. Your input helps us continue to improve and provide the best possible products and support.

• Provide a detailed network layout, including how the devices are connected.
• Include a detailed description of the issue and as much information as possible regarding the specific conditions that seem to trigger the behavior.

 

Thank you for your continued support and for being part of our community.

  @David-TP does it address the 2.4ghz channel and channel width stability issues in prior versions? Where 2.4ghz uses all the same channel and max channel width, meaning 2.4ghz is unusable in some environments. Hoping they finally baked this in. Thanks.

  @pjs_gsy Finally got time to read this whole thread, and it's full of comments re this issue. Take note tp-link - Please impliment this fix in the mainstream releases! It's clear a lot of people need it.

" @David-TP does it address the 2.4ghz channel and channel width stability issues in prior versions? Where 2.4ghz uses all the same channel and max channel width, meaning 2.4ghz is unusable in some environments. Hoping they finally baked this in. Thanks."

  @David-TP Will there be any support for v1 of XE75 as i am waiting for the Wireguard Server upgrade for my network and connect it unless i have to move my main router to another Deco that supports it or move to another brand that support Wireguard Server . 

  @David-TP There were no problems after reverting to the previous firmware (1.30). In my post I was describing the problems with the beta firmware. I did not notice any other problem devices with the beta firmware (after rebooting everything). I did not test the beta firmware for long as both TVs not connecting was a real problem! My router is a Firewalla Gold SE that does not have WiFi.

  @David-TP Can we expect this formware to be updated with the 2.4ghz fixes from past betas soon?  I can't recommend anything TP-Link at this point with all the broken firmware.

  @David-TP 

Hello everyone and @David-TP,

I am experiencing a persistent IPv6 MTU issue with my Deco XE75 V3 and I would like to know if the 1.4.0 Beta addresses it before I flash this irreversible update.

My Setup:

Router: TP-Link Deco XE75 V3 (currently on the latest official 1.3.x firmware)

ISP: Vidanet (Hungary)

Modem: Arris TG6441 (configured in Bridge Mode)

Testing Device: Pixel 9 Pro XL

The Issue:

The Deco successfully receives an IPv6 prefix and delegates public IPv6 addresses to my devices. However, when running test-ipv6.com, I consistently get a 1/10 score with the error: "large packets are dropped" (MTU / PMTUD issue). This causes severe loading and timeout issues on certain websites and mobile apps.

What I've Tried:

I have already tried switching the IPv6 Assigned Type to SLAAC+RDNSS, setting manual Google IPv6 DNS, and even opening IPv6 firewall rules for the testing device, but the 1/10 MTU error remains. It seems the Deco is failing to negotiate the correct IPv6 packet size (MSS Clamping / PMTUD) with my ISP.

My Questions regarding the 1.4.0 Beta:

1. Does the new network engine in this 1.4.0 Beta fix IPv6 Path MTU Discovery (PMTUD) issues?

2. Does the new Web UI in this update finally allow manual MTU size configuration (e.g., 1452 or 1472) or MSS Clamping for the WAN port?

Since the beta is irreversible, I want to be sure it has the potential to solve this specific routing issue before upgrading. Any feedback from the TP-Link team or users who had similar IPv6 MTU problems would be greatly appreciated.

Thank you!

  @David-TP Hi @David-TP,

Thank you very much for the quick reply and the detailed information! I wanted to let you know that I have just sent an email to support.forum@tp-link.com with "Forum ID# 856648" in the subject line. I included all the details you asked for, along with the screenshots of the test-ipv6.com MTU error, my Deco settings, and the device network details.

I am looking forward to working with the senior engineers to find a solution for this PMTUD issue.

Thanks again for your help!

natszirt