There are a lot of posts here regarding this problem. 5.8 seems to be ok. 5.11 seems to be bad.This version is unstable on PC.
After few days (two is maximum) the router stops respond without any information, only way how to get them online is reboot.
Router contains 8 wireless cards and one on board ethernet.
With previous version (5.7) router runs excelently all the time after instalation.
I downgraded the PC router to 5.7 :
That is one of the bugs with 5.9, 5.10, 5.11. You have to use 5.8 with x86 for now.my x86 router lock up to, after upgrade from 5.8 to 5.9 and then unstable occured.
tried upgrade to 5.11 but wouldn't help.
my conf :
webproxy internal, couples of mangling and queue tree, thats it.
with version 5.8 run flawlessly.
Hi Alexspils. What is your ethernet controller model? I have some intel ethernet controllers. Have a problem of high latency if traffic exceeds 100Mbps.i`m running 5.11 on x86 (core 2 duo, intel nics, multicpu=yes) for about 14 days, no problems...
Does anybody know any stable version? Could anybody tell: is it possible to downgrade? How?Having reboot proplems on x86 with pppoe and bpg too... And no logs and somthing useful... Too bad...
Thank you for info... But, I think only developers can do something to help us...Only x86 unit I have been having a problem on myself is my testing unit, it's a Soekris net4501. Works fine most of the time. Only have has a couple random reboots, need reattach the serial cable and see if there are any messages on the console. Seems random though haven't actually caught it yet. Only other strangeness I see is the unusual queuing CPU usage that I have seen go up to like 40%, I have no queues setup, tried setting up some to see if it made a difference and no real change.
Wow! great news! Thank you very mutch! Could you please tell us: patch or new release?we have made a pre-release version with a potential fix for x86 reboots. please email us to get the beta
Hi AlxFirst, How is your packet loss and latency, when using mangle, queue tree and traffic exceeds 200Mbps? I have problem with my 8core x86 and RB1100AHx2. When using queue tree with prerouting marked packets and traffic exceeds 150Mbps, there is very high latency and packet loss occurs for prerouted packets.upgrade my two routers-x86 (dual-core) from 5.7 to 5.12 - 3 days, all is right. Using bgp, queue-tree, mangles, nat, mpls, gre-tunnels - all works fine (at one router - 350-450 Mbit transfer, and 40-70 Mbit at other).
what CPU load?Hi AlxFirst, How is your packet loss and latency, when using mangle, queue tree and traffic exceeds 200Mbps? I have problem with my 8core x86 and RB1100AHx2. When using queue tree with prerouting marked packets and traffic exceeds 150Mbps, there is very high latency and packet loss occurs for prerouted packets.
/ip firewall mangle export
add action=change-mss chain=forward disabled=no new-mss=1440 passthrough=yes protocol=tcp tcp-mss=1441-65535
add action=mark-connection chain=forward comment=Eco_512k disabled=yes dst-address-list=!OTHERISP new-connection-mark=Eco_512k passthrough=yes src-address-list=Eco_512k
add action=mark-packet chain=forward comment=Eco_512k connection-mark=Eco_512k disabled=yes new-packet-mark=Eco_512k passthrough=no
add action=mark-connection chain=forward comment=Eco_5120k disabled=yes dst-address-list=!OTHERISP new-connection-mark=Eco_5120k passthrough=yes src-address-list=Eco_5120k
add action=mark-packet chain=forward comment=Eco_5120k connection-mark=Eco_5120k disabled=yes new-packet-mark=Eco_5120k passthrough=no
add action=mark-connection chain=forward comment=Eco_4096k disabled=yes dst-address-list=!OTHERISP new-connection-mark=Eco_4096k passthrough=yes src-address-list=Eco_4096k
add action=mark-packet chain=forward comment=Eco_4096k connection-mark=Eco_4096k disabled=yes new-packet-mark=Eco_4096k passthrough=no
add action=mark-connection chain=forward comment=Eco_3072k disabled=yes dst-address-list=!OTHERISP new-connection-mark=Eco_3072k passthrough=yes src-address-list=Eco_3072k
add action=mark-packet chain=forward comment=Eco_3072k connection-mark=Eco_3072k disabled=yes new-packet-mark=Eco_3072k passthrough=no
add action=mark-connection chain=forward comment=Eco_256k disabled=yes dst-address-list=!OTHERISP new-connection-mark=Eco_256k passthrough=yes src-address-list=Eco_256k
add action=mark-packet chain=forward comment=Eco_256k connection-mark=Eco_256k disabled=yes new-packet-mark=Eco_256k passthrough=no
add action=mark-connection chain=forward comment=Eco_2048k disabled=yes dst-address-list=!OTHERISP new-connection-mark=Eco_2048k passthrough=yes src-address-list=Eco_2048k
add action=mark-packet chain=forward comment=Eco_2048k connection-mark=Eco_2048k disabled=yes new-packet-mark=Eco_2048k passthrough=no
add action=mark-connection chain=forward comment=Eco_128k disabled=yes dst-address-list=!OTHERISP new-connection-mark=Eco_128k passthrough=yes src-address-list=Eco_128k
add action=mark-packet chain=forward comment=Eco_128k connection-mark=Eco_128k disabled=yes new-packet-mark=Eco_128k passthrough=no
add action=mark-connection chain=forward comment=Eco_1024k disabled=yes dst-address-list=!OTHERISP new-connection-mark=Eco_1024k passthrough=yes src-address-list=Eco_1024k
add action=mark-packet chain=forward comment=Eco_1024k connection-mark=Eco_1024k disabled=yes new-packet-mark=Eco_1024k passthrough=no
add action=mark-connection chain=forward comment=Eco_10240k disabled=yes dst-address-list=!OTHERISP new-connection-mark=Eco_10240k passthrough=yes src-address-list=Eco_10240k
add action=mark-packet chain=forward comment=Eco_10240k connection-mark=Eco_10240k disabled=yes new-packet-mark=Eco_10240k passthrough=no/queue tree export
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Total_download packet-mark="" parent=global-out priority=8
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_512k_down packet-mark=Eco_512k parent=Total_download priority=8 queue=Eco_512k_down
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Total_upload packet-mark="" parent=ether1 priority=8
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_512k_up packet-mark=Eco_512k parent=Total_upload priority=8 queue=Eco_512k_up
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_1024k_down packet-mark=Eco_1024k parent=Total_download priority=7 queue=Eco_1024k_down
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_1024k_up packet-mark=Eco_1024k parent=Total_upload priority=8 queue=Eco_1024k_up
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_10240k_down packet-mark=Eco_10240k parent=Total_download priority=8 queue=Eco_10240k_down
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_10240k_up packet-mark=Eco_10240k parent=Total_upload priority=8 queue=Eco_10240k_up
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_5120k_down packet-mark=Eco_5120k parent=Total_download priority=8 queue=Eco_5120k_down
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_5120k_up packet-mark=Eco_5120k parent=Total_upload priority=8 queue=Eco_5120k_up
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_128k_down packet-mark=Eco_128k parent=Total_download priority=8 queue=Eco_128k_down
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_128k_up packet-mark=Eco_128k parent=Total_upload priority=8 queue=Eco_128k_up
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_256k_down packet-mark=Eco_256k parent=Total_download priority=8 queue=Eco_256k_down
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_256k_up packet-mark=Eco_256k parent=Total_upload priority=8 queue=Eco_256k_up
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_2048k_down packet-mark=Eco_2048k parent=Total_download priority=8 queue=Eco_2048k_down
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_2048k_up packet-mark=Eco_2048k parent=Total_upload priority=8 queue=Eco_2048k_up
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_4096k_down packet-mark=Eco_4096k parent=Total_download priority=8 queue=Eco_4096k_down
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_4096k_up packet-mark=Eco_4096k parent=Total_upload priority=8 queue=Eco_4096k_up
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_3072k_down packet-mark=Eco_3072k parent=Total_download priority=8 queue=Eco_3072k_down
add burst-limit=0 burst-threshold=0 burst-time=0s disabled=yes limit-at=0 max-limit=0 name=Eco_3072k_up packet-mark=Eco_3072k parent=Total_upload priority=8 queue=Eco_3072k_upCPU usage is 60-70%, then max bandwidth (250Mbit IN and 150-200Mbit out = total around 400-450Mbit) - then CPU usage around 85-90%what CPU load?Hi AlxFirst, How is your packet loss and latency, when using mangle, queue tree and traffic exceeds 200Mbps? I have problem with my 8core x86 and RB1100AHx2. When using queue tree with prerouting marked packets and traffic exceeds 150Mbps, there is very high latency and packet loss occurs for prerouted packets.
is it in PCQ queues?
New MT based on Core-i7 prepared 
- one bandwidth for one account, witch may have some IPs):use forward thread, not prerouting - in prerouting I see the strange results tooHi AlxFirst, How is your packet loss and latency, when using mangle, queue tree and traffic exceeds 200Mbps? I have problem with my 8core x86 and RB1100AHx2. When using queue tree with prerouting marked packets and traffic exceeds 150Mbps, there is very high latency and packet loss occurs for prerouted packets.upgrade my two routers-x86 (dual-core) from 5.7 to 5.12 - 3 days, all is right. Using bgp, queue-tree, mangles, nat, mpls, gre-tunnels - all works fine (at one router - 350-450 Mbit transfer, and 40-70 Mbit at other).
) We are (company, where I working) using Intel server netcards with biggest buffer-size and hardware queue.Sorry - mistake. "RPS" of couseHi AlxFirst,
1. What is RMS?
In my experience the simple-queue more slowly, more cpu-usage than queue-tree rules and more "bugs"2. When I`m using dynamic simple queues, forward chain of packet marks doesn`t pass over simple queues. I use marked packets for queue tree, that pass over simple queues. For example: Packets sourced from some internal media sharing servers must be not rated by simple queues.
3. My second try is to use PCQ queues instead of dynamic simple queues. In that case mangle forward chain works. Because PCQ rule created at queue tree. But there is very strange big packet loss at PCQ handling packets.
Now I'm using only queue-tree for all task about client's bandwidths. PCQ-type is very powerful for simple rule: one fixed guarantee speed for fixed clients number and when count of clients less of max in rule, then all clients get more guarantee-speed and separate the total rule-speed