[SOLVED] How do I fix an unstable network on RB750 with v6.35.4

Hello All,
I have a RB750 running v6.35.4 and its working fine after reboot in several hours,
but sometimes working unstable need to reboot it and get working fine again.

Screenshot of Ping:




I used following function on my RB750:

  • PPPoE Client
  • L2TP Client with IPSec
  • Firewall Mangle (Mark Connection Packet) [14 rules]
  • IPv4 Route (Routing Mark and Static)
  • Queue Tree and PCQ

When RB750 get unstable cause:

  • IPv4 ping unstable but IPv6 fine
  • IPv4 packet drop Intermittently but IPv6 fine

System Resources:

  • CPU about: ~70% [on download file] <15% [normal]
  • Memory: ~ 8-7 MB

Here are rules of Firewall mangle:

Flags: X - disabled, I - invalid, D - dynamic 
 0  D chain=forward action=change-mss new-mss=1410 passthrough=yes tcp-flags=syn 
      protocol=tcp out-interface=all-ppp tcp-mss=1411-65535 log=no 
      log-prefix="" 

 1  D chain=forward action=change-mss new-mss=1410 passthrough=yes tcp-flags=syn 
      protocol=tcp in-interface=all-ppp tcp-mss=1411-65535 log=no log-prefix="" 

 2    ;;; Gamming Acc for IP range via L2TP
      chain=prerouting action=mark-connection new-connection-mark=co_game_acc 
      passthrough=yes dst-address-type=!local src-address-list=Local-Network 
      dst-address-list=Game-Acc log=no log-prefix="" 

 3    chain=prerouting action=mark-routing new-routing-mark=ro_game_acc 
      passthrough=no dst-address-type=!local src-address-list=Local-Network 
      dst-address-list=Game-Acc log=no log-prefix="" 

 4    chain=input action=mark-connection new-connection-mark=co_game_acc 
      passthrough=no in-interface=l2tp-game1 log=no log-prefix="" 

 5    chain=output action=mark-routing new-routing-mark=ro_game_acc 
      passthrough=no connection-mark=co_game_acc log=no log-prefix="" 

 6    ;;; Mangled for queue tree by port and size
      chain=forward action=mark-connection new-connection-mark=co_qt_game 
      passthrough=yes protocol=udp packet-size=0-512 log=no log-prefix="" 

 7    chain=forward action=mark-packet new-packet-mark=pk_qt_game passthrough=no 
      connection-mark=co_qt_game packet-size=0-512 log=no log-prefix="" 

 8    chain=forward action=mark-connection new-connection-mark=co_qt_icmp 
      passthrough=yes protocol=icmp log=no log-prefix="" 

 9    chain=forward action=mark-packet new-packet-mark=pk_qt_icmp passthrough=no 
      protocol=icmp connection-mark=co_qt_icmp log=no log-prefix="" 

10    chain=forward action=mark-connection new-connection-mark=co_qt_web_down 
      passthrough=yes protocol=tcp src-port=80,8000,8080,8081,443,53 
      packet-size=0-1024 log=no log-prefix="" 

11    chain=forward action=mark-packet new-packet-mark=pk_qt_web_down 
      passthrough=no connection-mark=co_qt_web_down packet-size=0-1024 log=no 
      log-prefix="" 

12    chain=forward action=mark-connection new-connection-mark=co_qt_web_up 
      passthrough=yes protocol=tcp dst-port=80,8000,8080,8081,443,53 
      packet-size=0-1024 log=no log-prefix="" 

13    chain=forward action=mark-packet new-packet-mark=pk_qt_web_up 
      passthrough=no connection-mark=co_qt_web_up packet-size=0-1024 log=no 
      log-prefix="" 

14    ;;; Mangled for queue tree by packet size
      chain=forward action=mark-connection new-connection-mark=co_qt_small 
      passthrough=yes packet-size=0-512 log=no log-prefix="" 

15    chain=forward action=mark-packet new-packet-mark=pk_qt_small passthrough=n>
      connection-mark=co_qt_small packet-size=0-512 log=no log-prefix="" 

16    chain=forward action=mark-connection new-connection-mark=co_qt_big 
      passthrough=yes packet-size=513-1524 log=no log-prefix="" 

17    chain=forward action=mark-packet new-packet-mark=pk_qt_big passthrough=no 
      connection-mark=co_qt_big packet-size=513-1524 log=no log-prefix="" 

I guess this issue caused by firewall rules or Room temperature (~31 ℃)
And supout.rif file is here: https://mega.nz/#!JkZTSDZT

Anyone know how to fix it? THANKS.
Regards

THERE ARE THE SAME PROBLEM
This problem is only shown on version 6.29 or later, I think is made by FastTrack (start supported from 6.29).
Now, I’m downgraded RB750 to 6.25 and watch network stability.

http://forum.mikrotik.com/t/6-29-6-30rc20-and-6-30rc24-on-rb750-and-powerbox/89235/1 > // 6.29, 6.30rc20 and 6.30rc24 on RB750 and Powerbox
http://forum.mikrotik.com/t/rb750-high-latency-on-lan/90649/1 > // RB750 - High latency on LAN

Downgrade to 6.25, RB750 up-time more than 3 days now.
Problem has been solved.
BUT what cause the problem in 6.29+, maybe FASTTRACK ?