# I had to choose between turning 3 TP-Link Deco XE75 Pros into e-waste or patching in IoT VLANs myself — discovered TP-Link left Port 20001 root file-write unfixed 2 years after Black Hat '24, and built true 802.1Q VLAN 30 tagging to OPNsense — retained record

> Retained reddit record from reddit:homelab.

Canonical: https://highsignal.app/data/records/36bb76a73fb62278

[← sources](https://highsignal.app/data)


source: [reddit](https://highsignal.app/data/reddit) (reddit:homelab)  published 2026-10-18 17:05 ingested 2026-10-19 02:41

[original source ↗](https://www.reddit.com/r/homelab/comments/1x98dso/i_had_to_choose_between_turning_3_tplink_deco/)

## retained text



```
If you run TP-Link Deco units (like the **XE75 Pro V3**) in **Access Point (AP) mode** in front of a real firewall (OPNsense / pfSense / UniFi), you've probably noticed two annoying limitations:

1. The Deco app has a dedicated **"IoT Network"** toggle, but it doesn't let you assign a VLAN ID to it — all IoT traffic gets dumped untagged onto `br-lan` alongside your main LAN.
2. Even if you try to use the **Guest Network VLAN ID** trick, it silently fails to tag Ethernet frames in AP mode unless you use specific port/backhaul setups.

In 2026, proper IoT network segmentation is a basic security requirement — and artificially withholding it on capable Wi-Fi 6E hardware is unacceptable. Today I faced a choice: **either throw three working Deco XE75 Pro units onto the e-waste pile, or reverse-engineer firmware** `1.5.0 Build 20260603 Rel. 15804` **and activate/patch the feature myself.**

# 1. Why the Stock Firmware Doesn't Tag IoT VLANs (Decompiled Rootfs Findings)

After decrypting and unpacking the `1.5.0` SquashFS rootfs:

* **The IoT VLAN knob exists in UCI, but is a total no-op:** `/etc/config/iot_wifi` actually has `option vlan_enable '0'`, and `/etc_ro/init.d/iot_network` has code for `iot_vlan_id` and `switch_iot_config` — **but TP-Link commented out lines 41–69 and omitted** `/lib/iot_network/iot_eth.sh` **from the firmware image!** Meanwhile `/lib/wifi/wificommon.sh` (line 651) hardcodes `uci_set wireless $section network "lan"`.
* **Guest VLAN in AP mode is gated in** `/etc/init.d/guest-eth.sh`\*\*:\*\* In `Router` mode, [`guest-eth.sh`](http://guest-eth.sh) adds switch ports `0t 1t 2t 3t 6t` to the guest VLAN. In `AP` mode on the main unit, it only adds the internal CPU port (`6t`) and skips external switch port tagging.

# 2. How We Got Root Without UART — 2 Years After CCS'24 / Black Hat '24, tmpsvr Is Still Wide Open

Two years ago (CCS 2024 / Black Hat USA 2024), researchers showed that every Deco unit listens on **TCP port** `20001` (Dropbear SSH) and tunnels to [`127.0.0.1:20002`](http://127.0.0.1:20002) (`tmpsvr`).

* **TP-Link had two years (2024 → June 2026) to secure** `tmpsvr`\*\*.\*\* All they did in firmware `1.5.0` was bump the SSH RSA key size from 512-bit to 2048-bit, while leaving password authentication (`SHA1(your_tplink_email)` \+ your TP-Link ID password) and the underlying `root` handlers completely untouched!
* On `tmpsvr`, opcode `0x00F0` still reads any file as `root`, opcode `0xC456` **(**`inner_file_push`**) still writes any file to any path as** `root` (`io.open(params.file, "w")`, zero path validation), and even the 2024 `tty2tcp` (`0xC505`) shell injection handler is still unfixed in the code.
* From `0xC456`, swapping `/tmp/luci-indexcache` gives full `root` Lua / shell execution (`io.popen`), and we were able to create a dedicated `br-iot` bridge (`eth1.30` \+ `ath08` 2.4GHz IoT VAP + `ath18` 5GHz IoT VAP + `switch1` VLAN 30 on `2t 6t`) across all three mesh units talking directly to OPNsense (`192.168.30.1`).

# 3. Why Public Release & Repositories

Because TP-Link already had two years since the 2024 disclosure and only increased the RSA key length while leaving `tmpsvr` unfixed, we are releasing both repositories publicly so that every Deco owner has the chance to (a) take immediate defensive precautions around port `20001` and their TP-Link ID password, and (b) equip their existing Decos with proper 802.1Q VLAN segmentation instead of replacing working hardware:

* **802.1Q IoT VLAN Runtime & Native Web-UI (**`deco-iot-vlan`**):** [https://github.com/CPlusPlus17/deco-iot-vlan](https://github.com/CPlusPlus17/deco-iot-vlan)
* **Security Advisory & PoC (**`deco-filepush-disclosure`**):** [https://github.com/CPlusPlus17/deco-filepush-disclosure](https://github.com/CPlusPlus17/deco-filepush-disclosure)

**Quick takeaway for Deco owners:** Make sure your TP-Link ID password is unique (never reused anywhere else) and restrict TCP port `20001`, because on 1.5.0 that port still exposes full `root` file read/write.

We also turned the firmware investigation and our ongoing IoT VLAN experiments into an animated music video: [Port 20001 — Four AIs, Three Routers, One VLAN](https://youtu.be/DmKSK-eHLB0).
```



document fetched 2026-10-19 00:32 · canonical https://reddit.com/r/homelab/comments/1x98dso/i_had_to_choose_between_turning_3_tplink_deco
