Mangled traffic not picked up by queue

RouterOS General
1

Hi

I have setup simple PCQ queueing for a clients site (CCR1009 6.32.2)
The client has a 15 Mnps SDSL uplink

One of the objectives is to ‘protect’ VoIP traffic

Mangles:

/ip firewall mangle
add action=mark-connection chain=prerouting comment="SIP Signaling" dscp=26 \
    new-connection-mark=VOIP-CMD
add action=mark-packet chain=prerouting connection-mark=VOIP-CMD \
    new-packet-mark=VOIP-PMD passthrough=no
add action=mark-connection chain=postrouting dscp=26 new-connection-mark=\
    VOIP-CMU
add action=mark-packet chain=postrouting connection-mark=VOIP-CMU \
    new-packet-mark=VOIP-PMU passthrough=no
add action=mark-connection chain=prerouting comment="RTP VoIP" dscp=46 \
    new-connection-mark=VOIP-CMD
add action=mark-packet chain=prerouting connection-mark=VOIP-CMD \
    new-packet-mark=VOIP-PMD passthrough=no
add action=mark-connection chain=postrouting dscp=46 new-connection-mark=\
    VOIP-CMU
add action=mark-packet chain=postrouting connection-mark=VOIP-CMU \
    new-packet-mark=VOIP-PMU passthrough=no
add action=mark-connection chain=prerouting comment="UDP VoIP" \
    new-connection-mark=VOIP-CMD protocol=udp src-address=XXX.XXX.XXX.XXX \
    src-port=5060-5061
add action=mark-packet chain=prerouting connection-mark=VOIP-CMD \
    new-packet-mark=VOIP-PMD passthrough=no
add action=mark-connection chain=postrouting dst-address=XXX.XXX.XXX.XXX \
    dst-port=5060-5061 new-connection-mark=VOIP-CMU protocol=udp
add action=mark-packet chain=postrouting connection-mark=VOIP-CMU \
    new-packet-mark=VOIP-PMU passthrough=no
add action=mark-connection chain=forward comment="HTTP Queuing" dst-port=\
    80,443 new-connection-mark=HTTP-CM protocol=tcp src-address=\
    192.168.11.0/24
add action=mark-packet chain=forward connection-mark=HTTP-CM new-packet-mark=\
    HTTP-PM
add action=mark-connection chain=forward comment="LAN Queuing" \
    new-connection-mark=LAN-CM src-address=192.168.11.0/24
add action=mark-packet chain=forward connection-mark=LAN-CM new-packet-mark=\
    LAN-PM

Queues:

/queue simple
add disabled=yes dst=ether1 limit-at=1M/1M max-limit=2M/2M name=VOIP-RTP \
    packet-marks=voip-rtp priority=1/1 target=192.168.11.0/24
/queue type
add kind=pcq name=PCQ-Download pcq-classifier=dst-address \
    pcq-dst-address6-mask=64 pcq-limit=20 pcq-src-address6-mask=64 \
    pcq-total-limit=500
add kind=pcq name=PCQ-Upload pcq-classifier=src-address \
    pcq-dst-address6-mask=64 pcq-limit=20 pcq-src-address6-mask=64 \
    pcq-total-limit=500
/queue simple
add disabled=yes dst=ether1 limit-at=15M/15M max-limit=15M/15M name=NON-VOIP \
    queue=PCQ-Upload/PCQ-Download target=192.168.11.0/24
/queue tree
add max-limit=13M name=Downloads parent=global queue=PCQ-Download
add max-limit=13M name=Uploads parent=global queue=PCQ-Upload
add max-limit=2M name=1-VoIP-D packet-mark=VOIP-PM parent=Downloads priority=\
    1 queue=default
add max-limit=2M name=1-VoIP-U packet-mark=VOIP-PM parent=Uploads priority=1 \
    queue=default
add max-limit=7M name=3-LAN-D packet-mark=LAN-PM parent=Downloads queue=\
    default
add max-limit=7M name=3-LAN-U packet-mark=LAN-PM parent=Uploads queue=default
add max-limit=6M name=2-HTTP-D packet-mark=HTTP-PM parent=Downloads priority=\
    2 queue=default
add max-limit=6M name=2-HTTP-U packet-mark=HTTP-PM parent=Uploads priority=2 \
    queue=default

Is my logic sound ?

thanks
yann

2

When comparing to my own firewall-mangle rules, I see one difference: I only use prerouting, but you use postrouting?

3

http://www.mikrotik-routeros.com/2014/05/the-mother-of-all-qos-trees-v6-0/

4

i think you need to mark every packet not connections, matching DSCP value

use the rate and packet rate column on firewall mangle on winbox to see on real time if the mangle rule is catching the traffic

5

I still think that’s wrong. No other examples on wiki.mikrotik.com uses postrouting, and why would you? You want to mark the packet before it’s about to get routed (and queued), not afterwards. But give it a try, see if it’s helps.