Hi,
I have noticed on one of my routers running V6.0rc13 that queue tree is not working correctly. For example i am marking packets destined for my voip service and i can clearly see voip packets being marked. When calls are being made in the network i can see the data rate in the statistics tab of my rule.
Mangle
Chain =Pre-Routing
Dst. Address = x.x.x.x
Action = Mark Packet
New Packet Mark = QOS_VoIP
My queue tree rule does not show any traffic what so ever though.
Parent = Global
Packet Marks = QOS_VoIP
Queue Type = Default
Priority 2
Has anyone else seen this?
Re: Queue Tree not working with packet marks
Hi !
I´m getting no counting because I used also "Queue Type = Default"
Perhaps changing this to "ethernet-default" may help ?
(Just a thought .... 8=) )
Greetz.......Detlef
I´m getting no counting because I used also "Queue Type = Default"
Perhaps changing this to "ethernet-default" may help ?
(Just a thought .... 8=) )
Greetz.......Detlef
Re: Queue Tree not working with packet marks
No difference i am afraid, although now i have been looking at it on my screen for a while it seems queue tree is totally stuck.
I cannot even reset the counters, and the average rate on one of my queues is stick on 15.0kbps. There is about 25Mb of traffic between 21 customers on this particular site.
I cannot even reset the counters, and the average rate on one of my queues is stick on 15.0kbps. There is about 25Mb of traffic between 21 customers on this particular site.
Re: Queue Tree not working with packet marks
Well, to be more specific - I´m counting traffic on DSL and UMTS-Client here for myself.
Perhaps you want to check out "simple queue" - to see if the packets are counted here correctly....
On my side this is running fine right now...
target is the client-port of PPPoE.....
and "PPP-UMTS" is for UMTS-USB-Modem
Here´s my config for mangle
So I suppose you have to change the output-port to your IP-address....
Just forgot - I read in some place that this mangle-rules MUST be in first place.....
Greetz.......Detlef
Perhaps you want to check out "simple queue" - to see if the packets are counted here correctly....
On my side this is running fine right now...
Code: Select all
[admin@mikrotik.homenet] /queue simple> print
Flags: X - disabled, I - invalid, D - dynamic
0 name="DSL_Traffic" target=T-Online PPPoE via PPPoE-Bridge IPv4 parent=none
packet-marks=DSL_in,DSL_out priority=8/8
queue=ethernet-default/ethernet-default limit-at=0/0 max-limit=0/0
burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s
total-queue=ethernet-default
1 name="UMTS_Traffic" target=PPP-UMTS parent=none
packet-marks=UMTS_in,UMTS_out priority=8/8
queue=ethernet-default/ethernet-default limit-at=0/0 max-limit=0/0
burst-limit=0/0 burst-threshold=0/0 burst-time=0s/0s
total-queue=ethernet-default
and "PPP-UMTS" is for UMTS-USB-Modem
Here´s my config for mangle
Code: Select all
Flags: X - disabled, I - invalid, D - dynamic
0 ;;; Throughput via DSL
chain=postrouting action=mark-packet new-packet-mark=DSL_out
passthrough=yes out-interface=T-Online PPPoE via PPPoE-Bridge IPv4
1 chain=prerouting action=mark-packet new-packet-mark=DSL_in passthrough=ye>
in-interface=T-Online PPPoE via PPPoE-Bridge IPv4
2 ;;; Throughput via UMTS
chain=postrouting action=mark-packet new-packet-mark=UMTS_out
passthrough=yes out-interface=PPP-UMTS
3 chain=prerouting action=mark-packet new-packet-mark=UMTS_in
passthrough=yes in-interface=PPP-UMTS
Just forgot - I read in some place that this mangle-rules MUST be in first place.....
Greetz.......Detlef
Re: Queue Tree not working with packet marks
same problem here.
RouterOS : v 6.xx 64bit
CCR1016
RouterOS : v 6.xx 64bit
CCR1016
Re: Queue Tree not working with packet marks
Same here. Something is really broken with queues and mangle
Except I'm using a "release" version (6)
Except I'm using a "release" version (6)
Re: Queue Tree not working with packet marks
Hi all!
I've had the same problem.
And I even know the source: http://wiki.mikrotik.com/images/2/24/Packetflowv6.png
According to new packet flow it uses queue BEFORE prerouting.
So the incoming packets are marked after passing thru queue.
So there's no way to mark packets that come from interface, only (pre/post)routing and forward marks are processed.
I've tried to mark packets in input chain - no luck there(rule won't work in input)...
It was because of forwarding >_<
So marking in prerouting/forward/postrouting is right choice, just make sure these packets won't be re-marked.
I've had the same problem.
And I even know the source: http://wiki.mikrotik.com/images/2/24/Packetflowv6.png
According to new packet flow it uses queue BEFORE prerouting.
So the incoming packets are marked after passing thru queue.
So there's no way to mark packets that come from interface, only (pre/post)routing and forward marks are processed.
I've tried to mark packets in input chain - no luck there(rule won't work in input)...
It was because of forwarding >_<
So marking in prerouting/forward/postrouting is right choice, just make sure these packets won't be re-marked.