Last firmware 1.3.6 broke my router ER8411

Last firmware 1.3.6 broke my router ER8411

Last firmware 1.3.6 broke my router ER8411
Last firmware 1.3.6 broke my router ER8411
Thursday - last edited Thursday
Model: ER8411  
Hardware Version: V1
Firmware Version: 1.3.6

I updated my router to the last software because i had some problems about "physical disconnection" in my WAN ports.

 

After update to 1.3.6 i have MORE "pysical disconnection ports" even SFP+ and Ethernet, and my CPU router is directly 90% all time.

Cannot use nothing, no internet because "WAN is down" every few seconds.

 

 

Hardware V1

 

I try other routers and work very fine so the problem is my ER8411 and last firmware.

Few times i saw my ONT link pairing with 100mbps on ER8411... then disconnect.. then appear with 1Gb link... 

On my SFP+ link with 10Gb have same problem, every few seconds disconnect then reconnect.. then disconnect... then reconnect...

 

 

Cannot use nothing.

I try to disable one link and use only 1 WAN, imposible, DNS not resolving.... 

Also have Pppoe problems ... 

few months ago i cannot use my ONT with ER8411 because always have PADI errors, and then you release new firmware and fixed this... all work, not 100% good but 80% some errors sometimes... but now? now nothing work.

 

And cannot downgrade to another firmware... so i have my company unusable, need find another router brand.

All this problems not happen with pfSense.

 

 

 

 

 

I have router ER8411 and switch SX3832.

What i need to do ? Thats crazy.

  0      
  0      
#1
Options
7 Reply
Re:Last firmware 1.3.6 broke my router ER8411
Thursday
  0  
  0  
#2
Options
Re:Last firmware 1.3.6 broke my router ER8411
Thursday

  @MR.S 

 

Is not downgradeable firmware... 

  0  
  0  
#3
Options
Re:Last firmware 1.3.6 broke my router ER8411
Thursday

  @est3ban129 

 

okay, have you tried?

  0  
  0  
#4
Options
Re:Last firmware 1.3.6 broke my router ER8411
Thursday - last edited Thursday

  @est3ban129 

 

you cannot load older firmware directly once on 1.3.6  

 

Emergency mode or SSH roll-back is the only way

 

I have 2 ER8411 on 1.3.6, other than some VPN related bugs, i am not seeing these issues you noted on either of them - all physical port connections are stable, CPU is stable at around 5% (even with IDS, DPI etc enabled)

 

Factory reset it and let the controller readopt it first and see if the issues persist

  1  
  1  
#5
Options
Re:Last firmware 1.3.6 broke my router ER8411
Friday

  @est3ban129 

Thank you so much for taking the time to post the issue on the TP-Link community!

To better assist you, I've created a support ticket via your registered email address and escalated it to our support engineer to look into the issue. The ticket ID is TKID251113617please check your email box and ensure the support email is well received. Thanks!

Once the issue is addressed or resolved, welcome to update this topic thread with your solution to help others who may encounter the same issue as you did.

Many thanks for your great cooperation and patience!

  1  
  1  
#6
Options
Re:Last firmware 1.3.6 broke my router ER8411
Friday
From your description, the issue appears to be related either to ONT compatibility or to physical-line instability. Please let us know: The exact ONT model. The cable type/length (and part number if known) between the ONT and the ER8411. Whether you have already tried swapping the Ethernet cable. Whether inserting a switch between the ONT and the ER8411 changes the behavior. Regarding the CPU-spike symptom, how many active clients are currently on the ER8411?
  0  
  0  
#7
Options
Re:Last firmware 1.3.6 broke my router ER8411
Friday

  @Ethan-TP 

 

For approximately two years I have been running an ER8411. At the beginning, I used four WAN connections, three of them with Ubiquiti Networks UFiber Nano G ONTs. All three identical ONTs worked perfectly for more than a year without any issues.

 

Later, I cancelled two of those WAN lines and kept only one UFiber Nano G for a 1 Gb connection. On another line (10 Gb), I used the ISP’s own Router, a ZTE ZXHN F8748, connected to the ER8411 through SFP+.

 

This SFP+ connection with the ZTE ONT began showing intermittent “physical disconnection” events. These drops last about one second according to the logs, and every time they occur, the CPU usage spikes heavily.

 

Because of this, I purchased an HCOM XGSPON ONT from AliExpress. Before firmware 1.3.1, the ER8411 always failed PPPoE negotiation with PADI errors, but after updating to 1.3.1 it started working normally.

 

After some weeks, however, the physical disconnection events began again on the SFP+ port. The ONT never loses synchronization or its public IP, so the problem appears to be inside the ER8411. Updating to 1.3.3 seemed to fix the issue briefly, but after a week the disconnections returned, and even WAN4 (RJ45) began showing the same physical disconnection errors, even though that port had always worked perfectly since the day I bought the device.

 

Yesterday the situation became critical: nothing worked. DNS failed, pages loaded halfway, speed tests didn’t complete, and the CPU remained unstable. I had to reboot the router around 20 times. When connecting the ONTs to pfSense, speed tests run normally. Connecting them back to the ER8411 gives poor results or fails entirely.

 

 

To stabilize things temporarily, I removed PPPoE from the SFP+ port, set it to DHCP, and placed the ISP’s ZTE router in front, creating a double NAT. Even with this workaround, I woke up today with 14 new physical disconnection events.

 

 

Additional information

 

  • Physically, there are around 15 devices connected.

  • Including the Proxmox clusters, there are around 80 total devices on the network.

  • All the main traffic enters through just two WAN ports.

  • I do not use anything advanced such as VLANs on LAN, IDS/IPS, or heavy packet inspection.

  • The configuration is simple and standard.

  • I updated to firmware 1.3.6 one week ago, and since then the problems became much worse and the instability increased dramatically.

 

  0  
  0  
#8
Options