@David-TP 

Thank you for your reply. I have already contacted local support as suggested, but received no feedback so far.

However, I have an urgent update regarding this issue. My Deco XE75 V1.0 is now experiencing total system crashes (tilts) that require a hard power cycle.

Upon inspecting the latest logs right before the crash, I found hundreds of critical errors related to the imsnoop process: daemon.err imsnoop: mcManagerMCProcess: vlan node X, add it to encap table

It appears that the IGMP Snooping table is overflowing or failing to handle multicast traffic from devices like Sonos and Android TV boxes , even when they are idle.

Crucially: Disabling the 'IPTV/VLAN' toggle in the Deco App does NOT stop these imsnoop errors from flooding the system log and eventually crashing the router.

Since this seems to be a separate but related stability issue with firmware 1.4.3:

1. Is there a way to completely disable the imsnoop/IGMP process via a hidden setting or the Web UI?

2. Is this a known memory leak or table overflow issue in the V1.0 hardware?

This is severely impacting my network, as the system crashes under normal domestic multicast load. Any specific workaround for the imsnoop flood would be greatly appreciated.

  @Pengo 

Hi!

Same issue on my side. Also tried the things you did, but nothing yet. Have you maybe found something in the meantime?

Thanks

  @David-TP 

Hi,

Also tagging you, just in case. I'm having a lot of problems lately, because of this issue, so I'm pretty desperate to find a solution. It is the exact same case as Pengo's.

Thanks

  @Pengo 

I sent an email to local tech support, they kept me waiting for a month and then forwarded my ticket to a higher level, but I have not yet receive any real assistance. I will let you know in case I have any update from them.

  @David-TP 

Hi,

Yes, same reports

I have the same type of devices, so Apple TVs, Sonos system, home assistant on a pi4 etc. I changed nothing in my network in the last 6 months at least.

The issues started on Monday or around Monday, 9th March.

The system worked perfectly up to that point as follows. 1 deco was the main connected as a router to the ISP modem (my ISP is DIGI Romania) . And the other 2 decos were connected to the main, 1 wired and the other one wireless to the wired second one. This was the setup that worked for at least 1 year, no problem.

Now I even got an Omada ER707-M2 (latest firmware too) to work as the router and switched the decos to AP. One main wired directly to the Omada, and the other 2 wireless chain, as in the images.

Even in this scenario, the decos keep disconnecting for a few seconds then coming back on. So a lot of disconnects while the directly wired devices tot the omada work without interruption. Performance is good when it works (over 500mb on the main, around 300 on the wireless decos on speedtest and with around 20 latency), but the disconnects are so frequent that it doesn't matter.

And yes. devices all go red. blinking for about a minute or 2 then reconnect.

Reset them about 7 times now and recreated everything from 0 in different combinations, trying a different main and not having all 3, etc. Same thing.

firmware 1.4.3 build 20240926 Rel. 38336

  @David-TP 

Hi, and thanks for the reply.

I did what you recommended, and it seems to be stable. This may be the issue. I let it ping for about 4 hours continuously, both the Omada and Google, and there were no drops and good stable pinging. I'll keep it up like this and get back to you with updates tomorrow. 

Does this mean I shouldn't use the other 2 ports for anything? Fortunately, I don't need them now, but it's still not a good scenario.

Thank you and have a nice one.