@Zhmak How are your internet providers set up? What is your link backup setup for the device? Do you have the device plugged into a UPS or battery backup?

When did this issue begin? Were there any changes to the network prior to this issue starting? 

NeilR_M wrote

  @Zhmak How are your internet providers set up? What is your link backup setup for the device? Do you have the device plugged into a UPS or battery backup?

When did this issue begin? Were there any changes to the network prior to this issue starting? 

First provider is static IP (with IP some aliases)

Second is configured via DHCP

Third is PPPoE

Load balancing weights set up as 5:8:1. And VPN service which fail too is on first provided.

Link backup is disabled. Shouldn't load balancing keep users online? Judging by the balancing weights, users access the internet through a third provider. And I connect to the VPN through the first provider. It's doubtful they're disconnected at the same time. The provider's equipment is also powered by a UPS.

Gateway is connected to line interactive UPS. And there is no power outages during this problem.

There are no log entries about internet outages or port shutdowns.

I don't know what started this. It happens too rarely to be related to any changes.

I set up a periodic reboot of the gateway every morning. This significantly reduced the number of freezes. Before, they happened once a week or more often.

Оccasionally strange message appear on the gateway physical console:

free(): invalid pointer

  @Zhmak 

I have seen this exact scenario. 

Do you have bandwidth controls enforcing bandwidth limits on the WAN connections?  I have found if you have more than about 4 rules VLANs will start randomly losing internet traffic, which can be resolved by togglign the bandwidth rule off and on again.

Keeping my rule set below a total of 4 and this has not happenned.  I have reported this

  @GRL 

I am reporting the same  recurring "hard hang" issue across three separate ER8411 v1.0 units at three different sites. Every few days or weeks, traffic stops entirely and only a physical reboot restores connectivity.

I have already tried the following on all 3 units with NO success:

• Firmware: Updated to the latest stable (1.3.6 Build 20251028 Rel.12399).

• Services: Disabled IDS/IPS, mDNS, and URL Filtering to rule out memory leaks.

• Hardware: Confirmed stable temps and tested with different SFP+ modules and DAC cables.

• Environment: All sites have different ISPs and configurations; the only common denominator is the ER8411 v1.0 hardware.

Despite these "standard" fixes, the units continue to lock up. Is TP-Link acknowledging a hardware flaw with the v1.0 revision? We need a stable kernel fix or an RMA path to a hardware version that works.

Model: ER8411 v1.0

Affected Units: 3/3

Controller Version: 6.0.0.24

  @Zhmak 

The freeze happened again today, but I was in the office.

My laptop received an address via DHCP over a wired connection.

On the default VLAN, the gateway's web interface was accessible and functional. However, it was not accessible from the user VLAN.

8.8.8.8 couldn't be pinged, and it timed out. Addresses on the other VLAN couldn't be pinged.

Unfortunately, I was forced to reboot the gateway so that the users could work.

It appears that the issue is software-related. This is indicated by the sharp increase in the time between crashes when rebooting the gateway daily. Without it, the freezes occurred once or twice a week.

Is it possible to obtain more detailed logs of the gateway's operating system? If I access it via SSH, the console reports that the gateway is managed by a controller, and the available commands are limited.

Please help me figure out this problem. If this happens again, I'll have to replace the gateway with something more manageable. But I didn’t want to lose the convenience of the SDN OMADA