Deco M4 internet drop from time to time
Hi everyone,
I'm experiencing a recurring issue with my TP-Link Deco M4R(2.0) mesh router system, and I’m hoping someone here has encountered the same and found a reliable solution.
📌 Problem Summary
-
My Deco M4R randomly loses internet connectivity.
-
The LAN and Wi-Fi stay active – devices can still connect and receive IP addresses.
-
However, the internet goes down, and Deco does not automatically recover.
-
The only way to restore connection is by manually rebooting the main Deco unit (power cycle).
⚙️ My Configuration
-
Model: Deco M4R(2.0)
-
Firmware: 1.6.5 Build 20241231 Rel. 41802
-
Mode: Router
-
Configuration: ISP modem (Fiber twist p2420) -> Main Deco M4 (router mode) - Ethernet backhaul -> Satelite deco M4
-
WAN connection type: Static IP (set manually ~2 weeks ago didn't help), ISP recommends Dynamic IP
-
DNS: Manual (8.8.8.8 / 1.1.1.1)
-
IPTV/VLAN: Disabled
-
MAC Cloning: Enabled (matches working device)
-
WAN Port setting: Not available on my model
-
Multicast/IGMP Proxy: Enabled by default, cannot disable
🕵️♂️ What I’ve Tried / Observed
-
Internet from the ISP modem is fully functional — tested with laptop directly.
-
I have tried:
-
different Ethernet cables,
-
both Deco Ethernet ports,
-
switching to Access Point mode,
-
static and dynamic IP on WAN,
-
DNS and MAC clone settings.
-
Swap decos units betwen main and satelite
-
-
Logs show:
-
frequent WAN link loss (
br-wan
) even with static IP, -
Deco does not reinitiate WAN link or reconnect,
-
repeated errors like
send ioctl failed
,improxy multicast group failure
, -
WAN status goes from ONLINE → OFFLINE → ONLINE, but no traffic is restored unless rebooted.
-
💡 Additional Notes
-
That suggests either:
-
hardware issue with primary WAN port, or
-
firmware logic failing to reinitialize the WAN interface properly after loss.
-
❓ Looking for Help
Has anyone else:
-
Faced WAN link or DHCP issues like this with Deco M4R?
-
Found a way to force WAN renewal/reconnect without full reboot?
-
Managed to disable multicast proxy (improxy) or confirmed it as a cause?
I’ve already contacted TP-Link support, but would appreciate feedback from you too.
Thanks in advance!