Queue tree vs FastTrack..

RouterOS General
1

Hi !
I have a little doubt !
I have created my first queue tree with some mangle rules.

/ip firewall layer7-protocol
add name=BitTorrent regexp=" ^(\\x13bittorrent protocol|azver\\x01\$|get /scrape\\\?info_hash=get /announce\\\?\
    info_hash=|get /client/bitcomet/|GET /data\\\?fid=)|d1:ad2:id20:|\\x08'7P\\)[RP]"
/ip firewall filter
add action=accept chain=forward comment="defconf: accept in ipsec policy" ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" connection-state=\
    established,related
add action=accept chain=forward comment="defconf: accept established,related, untracked" connection-state=\
    established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" connection-state=invalid
add action=drop chain=forward comment="defconf:  drop all from WAN not DSTNATed" connection-nat-state=!dstnat \
    connection-state=new in-interface-list=WAN
add action=accept chain=input protocol=icmp
add action=accept chain=input connection-state=established
add action=accept chain=input connection-state=related
add action=accept chain=input comment="allow l2tp" dst-port=1701 protocol=udp
add action=accept chain=input comment="allow pptp" dst-port=1723 protocol=tcp
add action=accept chain=input comment="allow sstp" dst-port=443 protocol=tcp
add action=drop chain=input in-interface=ether1-gateway
/ip firewall mangle
add action=accept chain=forward comment=DNS port=53 protocol=tcp
add action=accept chain=forward comment=DNS port=53 protocol=udp
add action=mark-connection chain=forward comment=client-dw-con in-interface=ether1-gateway \
    new-connection-mark=client-dw-con passthrough=yes
add action=mark-packet chain=forward comment=client-dw-pkt connection-mark=client-dw-con new-packet-mark=\
    client-dw-pkt passthrough=yes
add action=mark-packet chain=prerouting comment=client-up-pkt connection-mark=client-up-con new-packet-mark=\
    client-up-pkt passthrough=yes
add action=mark-connection chain=prerouting comment=client-up-con in-interface=ether2-master \
    new-connection-mark=client-up-con passthrough=yes
add action=mark-packet chain=forward comment=ps4-dw-pkt connection-mark=client-dw-con dst-address=192.168.0.20 \
    new-packet-mark=ps4-dw-pkt passthrough=no
add action=mark-packet chain=forward comment=ps4-up-pkt connection-mark=client-up-con new-packet-mark=\
    ps4-up-pkt passthrough=no src-address=192.168.0.20
add action=mark-packet chain=forward comment=http-dw-pkt new-packet-mark=http-dw-pkt packet-mark=client-dw-pkt \
    passthrough=no port=80,443 protocol=tcp
add action=mark-packet chain=forward comment=http-up-pkt new-packet-mark=http-up-pkt packet-mark=client-up-pkt \
    passthrough=no port=80,443 protocol=tcp
add action=mark-packet chain=forward comment=p2p-dw-pkt layer7-protocol=BitTorrent new-packet-mark=p2p-dw-pkt \
    packet-mark=client-dw-pkt passthrough=no
add action=mark-packet chain=forward comment=p2p-up-pkt layer7-protocol=BitTorrent new-packet-mark=p2p-up-pkt \
    packet-mark=client-up-pkt passthrough=no
add action=mark-packet chain=forward comment=other-up-pkt new-packet-mark=other-up-pkt packet-mark=\
    client-up-pkt passthrough=no
add action=mark-packet chain=forward comment=other-dw-pkt new-packet-mark=other-dw-pkt packet-mark=\
    client-dw-pkt passthrough=no
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" ipsec-policy=out,none out-interface-list=WAN
add action=masquerade chain=srcnat out-interface=ether1-gateway
add action=masquerade chain=srcnat comment="masq. vpn traffic" src-address=192.168.89.0/24
add action=dst-nat chain=dstnat comment=fifa-ps4-tcp dst-port=80,443,1935,3478-3480,3659,10000-10099,42127 \
    in-interface=ether1-gateway protocol=tcp to-addresses=192.168.0.20
add action=dst-nat chain=dstnat comment=ps4-tcp dst-port=80,443,3478,3479,3480 in-interface=ether1-gateway \
    protocol=tcp to-addresses=192.168.0.20
add action=dst-nat chain=dstnat comment=battlefield-ps4-tcp dst-port=3659,14000-14016 in-interface=\
    ether1-gateway protocol=tcp to-addresses=192.168.0.20
add action=dst-nat chain=dstnat comment=fifa-ps4-udp dst-port=3074,3478-3479,3659,6000 in-interface=\
    ether1-gateway protocol=udp to-addresses=192.168.0.20
add action=dst-nat chain=dstnat comment=battlefield-ps4-udp dst-port=80,443,9988,10000-10100,17502,42127 \
    in-interface=ether1-gateway protocol=udp to-addresses=192.168.0.20
add action=dst-nat chain=dstnat comment=ps4-udp dst-port=3478,3479 in-interface=ether1-gateway protocol=udp \
    to-addresses=192.168.0.20

But I have seen that with fast track enabled the queue doesn’t works properly. Therefore I disabled the fast track, but in this way the ping in lan is so increased ( from <1ms to 15ms ) . Is There a compromise ?

p.s : The ip address 192.168.0.20 is the ip of my playstation 4

2

That is the whole point of FastTrack. Please read this article:
https://wiki.mikrotik.com/wiki/Manual:IP/Fasttrack

“Note that not all packets in a connection can be fasttracked, so it is likely to see some packets going through slow path even though connection is marked for fasttrack. This is the reason why fasttrack-connection is usually followed by identical action=accept rule. Fasttracked packets bypass firewall, connection tracking, simple queues, queue tree with parent=global, ip traffic-flow(restriction removed in 6.33), IP accounting, IPSec, hotspot universal client, VRF assignment, so it is up to administrator to make sure fasttrack does not interfere with other configuration;”

3

ok. But in what way can I select packet that have to use fasttrack and whose have not to use fasttrack ?

because i want to give high priority to ps4 connection , and maybe I can use fasttrack for ps4 connection :smiley: Because my current configuration doesn’t seem so good for ps4, when I see youtube video or netflix on other pc the ps4 start to lag …