basforge

Search titles, text and the “If it doesn’t work” cases.

    RU

    Fasttrack bypasses queues: rate limits only work without it

    Connections that went into fasttrack bypass Simple Queue and Queue Tree: the queue doesn’t see them and doesn’t limit them. For a guest limit or cake against lag to work, take that traffic out of fasttrack with an accept rule above it — don’t turn fasttrack off for the whole network.

    Fasttrack marks a connection after its first packets, and from then on the kernel takes it along a short path that skips the firewall, mangle and queues (Wired on MikroTik). A queue that’s supposed to cap the speed never sees those packets. The way to exclude traffic from fasttrack is an accept rule for it placed above the fasttrack rule: a packet that matches accept first never reaches fasttrack.

    An example — 50 Mbit/s down and 20 up for the whole guest network (Guest network on MikroTik):

    /ip firewall filter
    add chain=forward in-interface-list=GUEST connection-state=established,related \
        action=accept comment="guest: bypass fasttrack" \
        place-before=[find comment="defconf: fasttrack"]
    add chain=forward out-interface-list=GUEST connection-state=established,related \
        action=accept comment="guest: bypass fasttrack" \
        place-before=[find comment="defconf: fasttrack"]
    
    /queue simple add name=guests target=192.168.89.0/24 max-limit=20M/50M

    In max-limit upload comes first and download second, from the point of view of target, the guest network.

    For the whole network — a cake queue against lag on a busy link — you’d have to exclude all traffic through the ISP, which is the same as turning fasttrack off. A quad-core hAP ax² on gigabit copes without it; dual-core hEX models are already at the limit.

    If it doesn’t work

    A guest queue exists, its counter barely grows, guests download at full speed

    Cause
    Only a connection’s first packets go through the queue; the rest take fasttrack.
    Fix
    accept rules for guests above defconf: fasttrack, as below.

    Turned fasttrack off entirely — internet speed dropped, the CPU is at 100%

    Cause
    Now every packet goes through the whole firewall. On the dual-core hEX and hAP ax S with 25 rules that’s about 1.4 Gbit/s with large packets and much less with small ones.
    Fix
    Turn fasttrack back on and exclude only the traffic the queue needs to see.

    How to check

    Run a speed test from a guest phone and watch the counters:

    /queue simple print stats where name=guests
    #  name="guests" rate=19.8Mbps/49.6Mbps
    /ip firewall filter print stats where comment~"bypass fasttrack"

    rate holds at the limit and the rule counters grow — guest traffic goes through the queue.