Hey everyone,

Hope someone can help me out here. I've got a Deco BE65 Pro as my main unit (firmware 1.3.1 Build 26042912 Rel. 23561) connected via ethernet to my Bell Fibe modem, with 4 wireless satellite nodes (2 x BE65 Pro, 1 X50-Outdoor and 1 BE25). Small home, been working fine until recently (except in one room which I cannot figure out either!).

For the past while my whole network has been dropping multiple times a day. Every device in the house loses internet simultaneously - my Mac, Samsung TV, wife's Mac, even the ecobee thermostat. After some digging I found the BE65 Pro is actually rebooting itself and seemingly everything down with it.

I managed to catch the crash sequence in the logs tonight and found this repeating right before each reboot:

Thu Jun 18 22:31:45 2026 user.emerg IMPROXY: FATAL[init_interface@251]: exiting.....
Thu Jun 18 22:31:46 2026 user.emerg: tp219,505[18304]
Thu Jun 18 22:31:47 2026 user.emerg: tp219,606[18304]
Thu Jun 18 22:31:50 2026 user.emerg IMPROXY: FATAL[init_interface@251]: exiting.....
Thu Jun 18 22:31:55 2026 user.emerg IMPROXY: FATAL[init_interface@251]: exiting.....

Also seeing these alongside it:

• wandetect3: not in router mode
• wandetect3: get eth0 intf_type error
• wlanif_deleteWdsEntry: ath02, ath22
• wlanifBSteerEventsBufRdCB: Invalid message len: 48 bytes
   

The really concerning part is the identical IMPROXY FATAL error also shows up in older logs that appeared on the logs page from April 28, meaning maybe it has been happening for months.? I've confirmed with Bell that the internet line itself is stable, so it's definitely the Deco crashing.

I also noticed the same IMPROXY error has been reported by other users on older Deco models going back years - is this a known bug that's resurfaced in 1.3.1?

One other thing - I have a Samsung TV on the network and I saw a thread mentioning Samsung devices can sometimes trigger reboots on BE65/BE63. Could that be related?

Firmware is showing as up to date so I can't just update my way out of this. Has anyone else experienced this or found a fix? Is there a beta firmware available that addresses the IMPROXY crash?

Thanks in advance!