Device Model: TP-Link Deco XE75 Pro
Firmware Version: 1.2.11 Build 20240724 Rel. 38913
App Version: 3.8.157

 

Issue Description:

 

I’m experiencing an issue with the port forwarding configuration in the TP-Link Deco app, where enabling both TCP and UDP for specific ports (5154, 9, and 7) allows Wake-on-LAN (WoL) and Magic Packet Server (MPS) functions to work correctly, but system logs and network diagnostics suggest an inconsistency in how the app handles UDP traffic. Here’s the detailed report:

 

1. Observed Behavior

 

I configured port forwarding rules in the Deco app for UDP and TCP on ports 5154, 9, and 7 to enable remote WoL and MPS functionality for my PC (internal IP: 192.168.x.x, MAC: XX-XX-XX-XX-XX-XX).

 

Despite selecting “TCP & UDP” for these ports in the app, running netstat on my PC shows no UDP listeners for the Magic Packet Server (mpserver.exe), only TCP listeners on port 5154.

 

However, WoL and MPS functions work successfully on all three ports (5154, 9, and 7) over both Wi-Fi and mobile data (using a DDNS hostname like my-ddns-hostname), suggesting UDP traffic is being forwarded correctly despite the lack of UDP listeners in netstat.

 

2. Expected Behavior

 

When I enable both TCP and UDP in the port forwarding rules, I expect the Deco router to forward both TCP and UDP traffic correctly to my PC, and netstat should show UDP listeners on ports 5154, 9, and 7 if the Magic Packet Server is configured to listen on these ports.

 

The app should accurately reflect and implement the selected protocol (TCP/UDP) without discrepancies between the UI and actual network behavior.

 

3. Steps to Reproduce

 

Setup:
Ensure a PC is connected to the Deco network with a static IP (e.g., 192.168.x.x) and a unique MAC address (e.g., XX-XX-XX-XX-XX-XX).

 

Install the Magic Packet Server software by Nikita Somenkov on your PC, configured to listen on TCP port 5154 for MPS functions and UDP ports 9 and 5154 for WoL (verify with netstat -a -n -o | findstr 5154 and netstat -a -n -o -p UDP | findstr [9|5154]).

 

Set up DDNS in the Deco app with TP-Link DDNS (e.g., my-ddns-hostname) and ensure it resolves to the router’s public IP.

 

Port Forwarding Configuration:
In the Deco app, navigate to Settings > Advanced > Port Forwarding > Add Rule or Edit Rule.

 

Create or edit rules for:
Service Name: MagicPacket_Server, Service Type: Custom, Internal/External Port: 5154, Internal IP: 192.168.x.x, Protocol: TCP & UDP.

 

Service Name: WoL_PC, Service Type: Custom, Internal/External Port: 9, Internal IP: 192.168.x.x, Protocol: TCP & UDP.

 

Save the rules.

 

Testing:
Use the Magic Packet app on a mobile device (e.g., iPhone) to send WoL packets to my-ddns-hostname on ports 5154, 9, and 7 over Wi-Fi and mobile data.

 

Verify WoL and MPS functions work successfully.

 

On the PC, run the following commands in Command Prompt (as Administrator) to check for UDP and TCP listeners:

 

netstat -a -n -o | findstr 5154
netstat -a -n -o -p UDP | findstr 5154
netstat -a -n -o -p UDP | findstr 9

 

Result: WoL/MPS work, but no UDP listeners appear in netstat, only TCP on port 5154, suggesting a discrepancy or bug in the app’s protocol handling.

 

4. Actual Results

 

WoL and MPS functions succeed on ports 5154, 9, and 7 over both Wi-Fi and mobile data, but netstat on the PC shows only TCP listeners on port 5154 (PID 9676, mpserver.exe), with no UDP listeners on 5154, 9, or 7.

 

Example netstat output for TCP 5154 (partial):

 

TCP 0.0.0.0:5154 0.0.0.0:0 LISTENING 9676
TCP 192.168.x.x:5154 [External IPs]:[Ports] TIME_WAIT 0

 

Example netstat output for UDP 5154, and 9:

 

[No output for UDP 5154, 9]

 

5. Impact

 

The inconsistency creates uncertainty about the reliability and security of port forwarding, as UDP traffic appears to work despite no visible UDP listeners. This could lead to misconfiguration risks or undetected issues in other network setups.

 

It also complicates troubleshooting and optimization, as the UI suggests both protocols are enabled, but network diagnostics (e.g., netstat) tell a different story.

 

6. Environment

 

Operating System: Windows 11 Pro

 

Network: Static IP 192.168.x.x, Unique MAC XX-XX-XX-XX-XX-XX, DDNS my-ddns-hostname, Public IP dynamic

 

7. Request

 

Please investigate this inconsistency between the Deco app’s port forwarding UI (TCP & UDP enabled) and the actual network behavior (only TCP shown in netstat, no UDP listeners).

 

Provide guidance on whether this is a UI bug, a limitation of the router’s port forwarding implementation, or a configuration issue on my end.

 

8. Additional Notes

 

I’ve confirmed WoL and MPS work on ports 5154, 9, and 7 using the Magic Packet app, but the lack of UDP listeners in netstat raises concerns about reliability and security.

 

I’m willing to provide further logs or perform additional tests as requested. I have access to system logs in the Deco app and can save them locally or emulate the issue by repeating these steps and capturing logs during testing. Please advise on how to share logs or specific diagnostic steps.