hope so =)Is this intended to fix Queue Tree performance ?
And simple queue.Is this intended to fix Queue Tree performance ?
The biggest improvements are in large numbers of simple queues, not queue tree setup. But please send a supout.rif file and a description of your setup to mikrotik support, we will see how to improve your situation.RoS6.19rc6
8500 simple queue
traffic about 300Mbit/s load 30%, active users about 1000
if traffic > 300Mbit/s loop reboot every 1 min load 100%
RoS6.18 500-600Mbit load 70%, works stability. But in BHCA we have about 1.5 Gbit/s, so we didn't tested MT in this time.
RoS6.19rc6
80 magle rules for mark traffic 20 HTB queues in tree pcq
700 Mbit/s avg 50% ( but when we switch MT for Linux, where is 1.2Gbit/s)
RoS6.18 400Mbit/s avg 60% (but when we switch MT for Linux, where is 1.2Gbit/s)
so "queue tree and simple " have a sad perfomance.
Linux+tc+ipset+iptables = 1.5G avg 50% in same configuration ( 8500 queues) in BHCA
Did you test the version that this topic is about? v6.17 doesn't include the fixes described here. Also the fixes are for CCR, not RB1100After the 6:17 version only problems.
CCR and RB1100 presenting as PPPoE server reboots. RBs three new 433AH we put into operation last week with version 4:17 reboot every 10 or 15 minutes and had intakes of 100% CPU at times.
RB1100 with rc6 also presented reboot.
It's complicated.
sureIs there a v6.19rc version available with all packages ?
6.19rc7 looped rebooting too (6.19rc5->6.19rc6
looped rebooting (
I have problem with queueing performance on CCR
upd. Send supout.rif file. Ticket#2014070866000341
6.19rc8 same (6.19rc7 looped rebooting too (6.19rc5->6.19rc6
looped rebooting (
I have problem with queueing performance on CCR
upd. Send supout.rif file. Ticket#2014070866000341
6.19rc9 same (6.19rc8 same (6.19rc7 looped rebooting too (6.19rc5->6.19rc6
looped rebooting (
I have problem with queueing performance on CCR
upd. Send supout.rif file. Ticket#2014070866000341
Send supout.rif files. Ticket#2014070866000341
We are working on your ticket, thanks!6.19rc9 same (
Send supout.rif files. Ticket#2014070866000341
Can you please write to support, with the memory leak supout.rif file? Thank youI replaced the RB433 with a RB2011UiAS-2HnD-IN and am seeing the same memory leak under 6.19rc9. So the problem seems to be with the mips be build. I have uninstalled everything except the combined ROS package and NTP. Disabled wireless too.
There also is an issue with the watchdog timer which prevents the system from booting properly. Have seen this same issue with RB433. For now I disable the watchdog and all is well, but would prefer to have it running.
Systems hit about 70% of available memory and then get kernel panic.
We don't have any particularly long IP filters, are not running any scripts, and are not doing anything that we have not done for the last 3 years.
Problem seems to have appeared around 6.18. May have to downgrade to 6.15 which seemed reasonably stable.
Thoughts?
Please clarify what exactly is happening, the description of the problem is not entirely clearI tried 6.19rc but mine kept bombing out in the sense of not booting the network connections?? it would boot but no link on network??has anybody else had this
thanks, we can repeat the issueOn CCR when you disable an ethernet interface and then reboot the router the interface becomes enabled when it restarts even though it shows as greyed out in winbox like it is disabled, this is a problem if you have 1000 PPPOE sessions coming in all at the same time after a reboot, if you disable an interface and reboot the router the interface should stay disabled.
*) bridge - added ~loop protection~ stp enhancement
sounds like now STP detects not only loops between different ports, but also a loop behind single portnormis, please explain what this line in changelog mean:*) bridge - added ~loop protection~ stp enhancement
it will be fixed within a few minutes, sorry about thatI can't download 6.19RC from the website
Is there a known problem? I keep getting an URL does not exist message.
Barry
it is a new boolean option in bridge port configuration, disabled by default.sounds like now STP detects not only loops between different ports, but also a loop behind single portnormis, please explain what this line in changelog mean:*) bridge - added ~loop protection~ stp enhancement
But how it's work?it is a new boolean option in bridge port configuration, disabled by default.
[admin@MikroTik] > int bri exp
# aug/19/2014 16:45:09 by RouterOS 6.19rc9
# software id = EYYM-NYPD
#
/interface bridge
add name=br-test
/interface bridge port
add bridge=br-test interface=ether1 loop-protection=yes
add bridge=br-test interface=ether2 loop-protection=yes
add bridge=br-test interface=ether3 loop-protection=yes
But how it's work?it is a new boolean option in bridge port configuration, disabled by default.
ether1 and ether3 shortciruit by cable. Nothing changed i.e. bridge forwards ~300Mbps broadcasts (~400000 packets/sec) between interfaces, in log i see standart warning "interface,warning ether1 excessive broadcasts/multicasts, probably a loop" and nothing more happen.Code: Select all[admin@MikroTik] > int bri exp # aug/19/2014 16:45:09 by RouterOS 6.19rc9 # software id = EYYM-NYPD # /interface bridge add name=br-test /interface bridge port add bridge=br-test interface=ether1 loop-protection=yes add bridge=br-test interface=ether2 loop-protection=yes add bridge=br-test interface=ether3 loop-protection=yes
Where i wrong?
*) bridge - added ~Auto Isolate~ stp enhancement (802.1q-2011, 13.25.5)
13.25.6 AutoIsolate
A Boolean. Set by management if isolate (13.25.20) is to be set, causing a Designated Port to transition to Discarding if both AdminEdge (13.25.1) and AutoEdge (13.25.5) are FALSE and the other bridge presumed to be attached to the same point-to-point LAN does not transmit periodic BPDUs—either as a Designated Port or in response to BPDUs with the Proposal flag set (see 13.21). The recommended default of this parameter is FALSE. AdminEdge and AutoEdge are both reset only on ports that are known to connect to other bridges.
+ 1I guess my confusion was in expecting the RC download links to be removed once the release was final. Barry.