Early Access Deco BE85 V1/V2 Pre-release Firmware 1.3.0 Introduces DoH/DoT, Internet Backup, and More!
Update on Oct 19, 2026:
The official firmware version for Deco BE85 V1/V2 has been released publicly. Users can check for updates via the Deco's web interface or through the Deco App to install the latest version manually.
How to Update TP-Link Deco Firmware
If you cannot find the latest firmware version, please download the firmware (v1.3.0) here and upgrade it manually.
1.3.0 Build 26090112
We will manually lock this post to better focus on discussions regarding the new firmware. Please feel free to start a new thread here if you need assistance.
Best Regards
----------------------------------
Hey All,
We're excited to share early access to a new firmware update for Deco BE85 V1/V2, packed with new features and enhancements designed to elevate your Deco Mesh Home Networking experience. This firmware is currently in pre-release; however, your testing and feedback may help accelerate its official release!
This Article Applies to:
Deco BE85 V1/V2
Firmware Modifications:
New Features/Enhancements:
1. Supported fixing a specific port as the WAN port.
2. Added Hybrid Mesh feature.
3. Added Internet Backup feature.
4. Added DoH & DoT feature.
5. Added Speed Limit feature for client devices.
6. Optimized HomeShield feature.
7. Improved stability and security of the system.
Firmware Download Link:
| Deco BE85 V1/V2 | 1.3.0 Build 26080612 Rel 48751 (Pre-release Firmware) |
Attention: Please do not upgrade directly to Pre-Release Version 1.3.0. First, check for any available updates via the Deco app to see if v1.2.4 is available and if so, install it. If it is not yet available to you via the Deco app, follow these steps:
- After downloading and opening the compressed file, open the included text file.
- Follow the text instructions and manually upgrade to version 1.2.4 first, then proceed with version 1.3.0.
Notes:
- Please be sure you have read the Beta Test Agreement before upgrading the Pre-release firmware!
- Please ensure your Deco app is fully up-to-date.
- This firmware cannot be reverted directly to the previous official version.
- There will be an official firmware release in the future. If you are not comfortable using beta firmware, please wait for the official release or contact our support team for assistance.
- For detailed instructions on how to install the firmware on your Deco Mesh System, visit: How to manually update the firmware via web UI.
Additional Information
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.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Sun Aug 30 22:39:52 2026 kern.emerg : PRIVACY_ASSETS_CLCT_ONLINE_STAT_INFO
Sun Aug 30 22:39:52 2026 kern.emerg : PRIVACY_ASSETS_CLOUD_REPORT_SUCCESS
Sun Aug 30 22:49:52 2026 kern.emerg : PRIVACY_ASSETS_CLCT_ONLINE_STAT_INFO
Sun Aug 30 22:49:52 2026 kern.emerg : PRIVACY_ASSETS_CLOUD_REPORT_SUCCESS
Sun Aug 30 22:59:52 2026 kern.emerg : PRIVACY_ASSETS_CLCT_ONLINE_STAT_INFO
Sun Aug 30 22:59:52 2026 kern.emerg : PRIVACY_ASSETS_CLOUD_REPORT_SUCCESS
Mon Aug 31 18:37:30 2026 daemon.err nrd[3098]: send ioctl failed
Mon Aug 31 18:37:30 2026 daemon.err nrd[3098]: send ioctl failed
Mon Aug 31 18:37:30 2026 daemon.warn tpap[12267]: srv channel: tmp output: recv ctrl header successed.
Mon Aug 31 18:37:30 2026 daemon.warn tpap[12267]: [TLS-TMP] TLS Server session: recv packet, len:123
Mon Aug 31 18:37:31 2026 daemon.err nrd[3098]: send ioctl failed
Mon Aug 31 18:37:31 2026 daemon.err nrd[3098]: send ioctl failed
Mon Aug 31 18:37:32 2026 daemon.err ai-center: [eth_get_linkrate:103]: Unknown Duplex! (255)
Mon Aug 31 18:37:32 2026 daemon.err ai-center: [eth_get_linkrate:103]: Unknown Duplex! (255)
Mon Aug 31 18:37:32 2026 daemon.err uhttpd[22104]: *** WARNING : deprecated key derivation used.
Mon Aug 31 18:37:32 2026 daemon.err uhttpd[22104]: Using -iter or -pbkdf2 would be better.
Mon Aug 31 18:37:32 2026 daemon.err uhttpd[22104]: *** WARNING : deprecated key derivation used.
Mon Aug 31 18:37:32 2026 daemon.err uhttpd[22104]: Using -iter or -pbkdf2 would be better.

- Copy Link
- Report Inappropriate Content
Hi,
Thank you for sharing your test results.
Based on your description, the reported phenomenon appears to be relatively complex and may require further investigation by our technical team. To better diagnose the root cause, please reproduce the reported phenomena, then follow the instructions below to collect the Deco system log and send us the Deco App log for analysis. Please reply to us once you have sent the app log.
How to Get Deco System Log
How to Get and Send Deco App Log to TP-Link Support
Best Regards
- Copy Link
- Report Inappropriate Content
I have installed the pre-release firmware and, for the functions I use, it is working quite well.
For me encrypted DNS is the feature I wanted most.
I see a MAC address whitelist feature which I haven't seen before as well and I do use the security subscription features and constantly struggle with devices and private MAC addresses.
So this feature is of interest to me as well.
First question would be is it actually useful (open question to allow you)?
You may be thinking of asking what I mean by the above question but if you do then either the way it's implemented makes the question irrelevant (which you should have explained) or it's bound to be useless by design.
This sounds a bit vague, so let me ask a few more questions to clarify.
I'm pretty sure there is a limit on the number of DHCP reservations, maybe 64 or 128, correct (probably mainly due to only being able to store persistent configuration in NVRAM)?
Which prompts the question "what's the NVRAM size"?
And
1) Do you store the DHCP reservations list in NVRAM?
2) Do you store the "Device isolation" list in NVRAM?
3) What other configuration values/lists do you store in NVRAM?
4) Where is the persistent security related information stored, settings, parental control profiles, block exclusions etc.?
I have around 40 reservations and just over 50 devices in the isolation list, and several parental control profiles so am I going to be able to use an "AllowList" for my 100-110 MAC addresses?
Given that historically routers have very limited persistent storage wouldn't it make sense to implement/allow simple regular expressions in the block list. Some simple examples could be given for users, eg ?[26AaEe]::::: which would block all private MAC addresses (aka. RFC 7042) assuming the empty :: matches all in this case (not stands for 00 as in actual addresses), [] matches a single character of a set, and ? any single character . Clearly there would need to be some more simple rules but this would be far more economical for storage than enumerating the allowlist.
Of course, if you have much larger NVRAM on these devices than most devices it might not be such a potential problem.
- Copy Link
- Report Inappropriate Content
Hi,
If you are referring to the Allow List Mode on the Deco App > Security > Wi-Fi Access Control page, please refer to the instructions below to use this feature.
How to configure Wi-Fi Access Control on TP-Link Deco
When Allow List Mode is selected, only client devices on the Allow List can access your Wi-Fi network (except when Guest Network Exception is enabled). If you add a device by MAC address to the Allow List, you need to enter the device's actual MAC address, not "::".
Best Regards
- Copy Link
- Report Inappropriate Content
Solla-topee wrote
Hi,
If you are referring to the Allow List Mode on the Deco App > Security > Wi-Fi Access Control page, please refer to the instructions below to use this feature.
How to configure Wi-Fi Access Control on TP-Link Deco
When Allow List Mode is selected, only client devices on the Allow List can access your Wi-Fi network (except when Guest Network Exception is enabled). If you add a device by MAC address to the Allow List, you need to enter the device's actual MAC address, not "::".
Best Regards
@Solla-topee Yes it is the Allow List Mode I'm refering to.
Kindly answer my questions as they are specific to the ability of this function to work as TP Link have implemented it.
Don't mix up my suggested feature request with my questions about how the implementation, described by your referred instructions, works.
I'm concerned that, if the sort of error condition I'm asking about occurs and is not properly caught and handled I could end up with corrupt router NVRAM which at the least would require a factory default reset.
- Copy Link
- Report Inappropriate Content
Hello,
I would like to report an instability issue observed after upgrading my Deco BE85 units to firmware 1.3.0, following the recommended upgrade path from version 1.2.4.
My setup is:
- Two Deco BE85 units configured in Access Point mode.
- Main Deco connected to the modem through its 10G combo port.
- Wired Ethernet backhaul between the two Deco units using the same certified Cat7 Ethernet cable used in all tests.
- The current stable configuration uses the 10G non-combo port on the Main Deco and a 2.5G port on the Satellite Deco for the wired backhaul.
- A MacBook Pro is connected by Ethernet to the Satellite Deco's 2.5G port.
- The Internet connection is a 2.5 Gbps FTTH line with approximately 500 Mbps upload.
- The iPhone 16 Pro Max has MAC address XX:XX:XX:XX:BE:97.
With the iPhone set to Auto band selection, the MacBook Pro connected to the Satellite reaches approximately:
- 2.3 Gbps download.
- 480–500 Mbps upload.
This confirms that the FTTH connection, the wired backhaul, and the Satellite's Ethernet forwarding are capable of delivering the expected performance.
However, if I use the Deco app to force the iPhone 16 Pro Max to the 6 GHz band, the behavior changes significantly. The Main Deco continues to achieve approximately 2.3 Gbps, but the MacBook Pro connected by Ethernet to the Satellite drops to approximately 100 Mbps during the nPerf test.
The MacBook remains connected by Ethernet, and the Wi-Fi network appears available, but the traffic passing through the Satellite is heavily degraded. After returning the iPhone setting to Auto, performance returns to normal.
This suggests that the issue is not related to the FTTH line or the modem. It appears to affect the forwarding/path-selection behavior of the Satellite when a client is forced to remain on 6 GHz.
The logs also show repeated roaming/steering-related errors involving the iPhone's MAC address:
- Invalid beacon reports for XX:XX:XX:XX:BE:97.
- wlanif_kickout_node operations.
- qca_kickout_node failed to send ioctl.
- wlanifBSteerEventsBufRdCB: Invalid message len 48 bytes.
- wlanif_isSTAMoved: XX:XX:XX:XX:BE:97 move from ath2 to eth2.
- stadbEntryGetARBtmThreshold: NULL entry!
The iPhone is not connected by Ethernet, so the message indicating that it moved from the 6 GHz interface (ath2) to eth2 appears to be an inconsistent internal path or client-state report. It seems that the firmware is incorrectly associating the iPhone's Wi-Fi roaming state with an Ethernet/path-selection event.
The recurring message below is also present continuously in firmware 1.3.0:
ai-center: eth_get_linkrate: Unknown Duplex! (255)
This message was not present in my older logs from firmware 1.2.4, but it appears repeatedly in 1.3.0, typically every few seconds. It is also present when the network is otherwise working normally, so I cannot state that it is the direct cause of the 100 Mbps limitation. However, it may be related to the firmware's Ethernet link monitoring or path-selection logic.
I have also previously tested a 10G-to-10G wired backhaul. In that configuration, I observed:
- Fan speed increasing to maximum on both BE85 units, even with similar network load where the fans normally remained off.
- An unstable Satellite connection.
- The Satellite becoming unreachable from the Deco app.
- Loss of Internet connectivity for devices connected to the Satellite.
- Bridge and Ethernet-related errors, including eth2/eth3 link events, bridge configuration conflicts, TIPC host-unreachable messages, and repeated ioctl failures.
The current asymmetric configuration, using 10G on the Main side and 2.5G on the Satellite side, is much more stable. It has operated for approximately 24 hours without the severe Satellite isolation observed during the 10G-to-10G test, although the Unknown Duplex message remains present.
For now, the practical workaround is to leave the iPhone 16 Pro Max set to Auto instead of forcing it to 6 GHz. With Auto selected, the wired MacBook connection through the Satellite returns to approximately 2.3 Gbps.
Could TP-Link please investigate the interaction between the following components in firmware 1.3.0?
1. 6 GHz client band forcing and roaming/steering.
2. 802.11k/BTM/RRM handling for Wi-Fi 7 clients such as the iPhone 16 Pro Max.
3. Wired backhaul path selection and Satellite Ethernet forwarding.
4. The ai-center eth_get_linkrate: Unknown Duplex! (255) error.
5. The Invalid message len 48 bytes, kickout-node, and NULL AR BTM threshold errors.
6. Wired 10G backhaul behavior, including fan control and Satellite stability.
The issue appears to be firmware-related because the same certified Cat7 cable and the same physical network environment behave normally with the current 10G-to-2.5G configuration, while forcing the iPhone to 6 GHz reproducibly causes the wired Satellite throughput to fall to approximately 100 Mbps.
I can provide complete syslog files and additional controlled test results if required.
Thank you.
- Copy Link
- Report Inappropriate Content
Just to clarify a previously reported issue which may be relevant to the new BE85 firmware currently in beta testing:
I have six Deco BE85 units operating in AP mode, with DHCP and DNS provided by Windows Server 2025.
The issue is not the Deco node names displayed in the Deco app. Each node can already be given a different name in the app.
The issue is the hostname presented by the individual BE85 units to the external DHCP server. Despite the nodes having different names in the Deco app and different MAC/IP addresses, the BE85 units present the same hostname to DHCP.
This creates a problem when the Windows DHCP server performs Dynamic DNS (DDNS) registration. Multiple physical Deco nodes are using the same hostname, so DHCP/DNS cannot uniquely associate that hostname with an individual BE85.
My previous report received a reply explaining how to rename a Deco node in the Deco app. Unfortunately, that does not change the DHCP hostname and therefore does not address the issue.
As a new BE85 firmware version is currently in beta testing, could you please check whether this issue has been addressed in the new firmware?
Ideally, each physical BE85 should present a unique hostname to an external DHCP server, preferably based on its individually configured Deco node name.
- Copy Link
- Report Inappropriate Content
Hi,
The address reservation list, device isolation list, allow/block list, parental control profiles, and settings such as Wi-Fi settings are stored in NVRAM. We do not have information about the NVRAM size; however, features such as Address Reservation, Device Isolation, and the Allow List operate independently of one another, and the number of entries that can be added to each is limited; thus, using them will not compromise the Deco's NVRAM. For instance, if the Allow List supports up to 128 MAC address entries, you can add 128 entries to it regardless of how many items have already been added to Address Reservation or Device Isolation.
Best Regards
- Copy Link
- Report Inappropriate Content
Hi,
Regarding the new speed phenomenon, please confirm the following information when your iPhone is configured to prefer connecting to the 6GHz Wi-Fi in the Deco App for analysis.
1. What are the download and upload speeds on your iPhone when connecting to the satellite Deco? You can test speed on www.speedtest.net.
2. Is the 100Mbps download speed tested on www.speedtest.net on your MacBook Pro? What's the link speed on your MacBook Pro?
What Is Wi-Fi Link Speed and How to Check It on Windows, Mac, and Android
3. Have you tested the main Deco's download and upload speed on www.speedtest.net when connecting the MacBook Pro to the main Deco's 2.5Gbps port?
Best Regards
- Copy Link
- Report Inappropriate Content
Hi, thank you for your reply.
I understand the purpose of the requested tests. However, I would like to clarify that the main issue is not simply a speed-test result.
The behavior is reproducible and configuration-dependent:
- With the iPhone 16 Pro Max configured as Auto in the Deco app, the wired MacBook Pro connected to the satellite can reach approximately 2.3 Gbps download and approximately 480–500 Mbps upload.
- When the same iPhone is configured to prefer 6 GHz and is associated with the Satellite Deco, the wired throughput through that same Satellite can fall to approximately 100 Mbps.
- The Main Deco remains able to reach approximately 2.3 Gbps under the same conditions.
- Returning the iPhone setting from forced 6 GHz back to Auto restores normal multi-gigabit performance through the satellite.
Therefore, the problem is not the FTTH line, the ISP, the speed-test server, or the MacBook itself.
The variable that triggers the problem is the forced 6 GHz preference for the iPhone in the Deco app, and the impact is seen on the wired traffic passing through the same satellite Deco.
I would also like to emphasize that this appears to be a combined wired-and-wireless management problem on the satellite connected to the Main Deco by Ethernet backhaul.
The logs show recurring errors that appear relevant to this issue:
- "Invalid beacon report" for the iPhone client.
- "wlanif_kickout_node" operations.
- "qca_kickout_node failed to send ioctl".
- "wlanifBSteerEventsBufRdCB: Invalid message len 48 bytes".
- "stadbEntryGetARBtmThreshold: NULL entry!".
- "wlanif_isSTAMoved: XX:XX:XX:XX:BE:97 move from ath2 to eth2".
The iPhone is not connected by Ethernet. Therefore, the last message appears to be an inconsistent internal client/path report: a 6 GHz client-steering event is being associated with the Ethernet interface/path state.
Firmware 1.3.0 also continuously logs:
"ai-center: eth_get_linkrate: Unknown Duplex! (255)"
This message was not present in my previous 1.2.4 logs using the same certified Cat7 cable and the same physical network environment.
In separate 10G-to-10G wired-backhaul tests, I also experienced fan speed increasing to maximum, Ethernet/bridge instability, loss of the satellite from the Deco app, and loss of Internet access for devices connected to the satellite.
Related logs included Ethernet link events, bridge/path-selection errors, and TIPC “Host is unreachable” errors.
For these reasons, I believe the issue requires engineering analysis of the firmware 1.3.0 interaction between:
1. Forced 6 GHz client preference.
2. Client steering and 802.11k/BTM/RRM handling.
3. Satellite Ethernet forwarding.
4. Wired backhaul path selection.
5. The recurring ai-center link-rate/duplex error.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 5
Views: 8053
Replies: 56
