Changing a connection mark after a certain number of bytes and connection rate. No longer works in 6.30.2.

RouterOS General
1

I have been using the following script for 6.25 to great effect. I created it for this post to help people mark their traffic. However, this particular section of script does not work correctly under 6.30.2.

Logic:

    1. If the connection has not been marked as HTTP_BIG yet, then mark it as HTTP.
  1. If the connection has transferred over 5MB AND the current rate is 200K or more, change the connection mark to HTTP_BIG.
  2. Mark the packets.

Has there been a change to 6.30.2 that prevents this type of logic? Connection-Rate appears to be broken. Connection-Bytes works correctly.

Note: remove the slash () below. It is there for display formatting only.

/ip firewall mangle
add action=mark-connection chain=prerouting \ 
connection-mark=!HTTP_BIG connection-state=new new-connection-mark=HTTP port=80,443 protocol=tcp

add action=mark-connection chain=prerouting \ 
connection-mark=HTTP connection-bytes=500000-0 connection-rate=200k-100M new-connection-mark=HTTP_BIG protocol=tcp

add action=mark-packet chain=prerouting \ 
connection-mark=HTTP_BIG new-packet-mark=HTTP_BIG passthrough=no

add action=mark-packet chain=prerouting \ 
connection-mark=HTTP new-packet-mark=HTTP passthrough=no
2

i confirm also that this no longer works with 6.30.2
if i remove connection-rate, it works!

3

im on 6.30 connection bytes is working but connection rate dont

i will upgrade to 6.30.2 bug fix to test

4

anybody knows in which previous version of ros “connection-rate” is working ok?
mikrotik can u confirm that this is a bug of 6.30.2 ?

5

i have a 6.26 implementation with connection-rate working

6

same issue, connection bytes working but connection rate dont

7

connection-rate will catch also traffic like “youtube,skype,apple facetime,streaming radio,streaming videos”, right?

please edit 1st post…

If the connection has transferred over 5MB AND…
to
If the connection has transferred over 0.5MB AND…

8

i just downgrade to 6.26 and yes it works!

9

does not work also in 6.31 with reset configuration!

10

please report it at

http://forum.mikrotik.com/t/6-31-released/90490/1

maybe we can achieve it solved on bugfix release

6.31 released