The subject is quite descriptive: when using Masquerade PCQ-Upload queues work like standard queues.
It stopped working in V6 due to changes in packet flow.
Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
Last edited by LatinSuD on Thu Dec 24, 2015 10:08 am, edited 2 times in total.
Re: Suggestion: make "PCQ-Upload" compatible with "Maquerade" again
what parent do you use?
Re: Suggestion: make "PCQ-Upload" compatible with "Maquerade" again
I think it doesn't work with any of them (global or interface)what parent do you use?
Re: Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
well, it works for us in usual way (hundreds of active users per PCQ queue, RouterOS v6.10 to v6.33) on 'global' parent, and seems like that 'feature' was fixed in early v6:
Code: Select all
What's new in 6.0beta1 (2012-Apr-13 15:26):
*) pcq queue is NAT aware (just like "/queue simple" and "/ip traffic-flow";Re: Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
And yet it fails.
I set up 2 PC uploading and I only get 1M combined upload.
Ironically this document gets it wrong (it is broken in v6, while it worked in v5):
http://mum.mikrotik.com/presentations/HR13/valens.pdf
Code: Select all
/ip firewall mangle
add action=mark-packet chain=forward new-packet-mark=prueba out-interface=pppoe-out1
/queue type
add kind=pcq name=pcq-upload-prueba pcq-classifier=src-address pcq-dst-address6-mask=64 pcq-rate=1M \
pcq-src-address6-mask=64
/queue tree
add name=pcq-upload-prueba packet-mark=prueba parent=global queue=pcq-upload-prueba
Ironically this document gets it wrong (it is broken in v6, while it worked in v5):
http://mum.mikrotik.com/presentations/HR13/valens.pdf
Re: Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
and what value you see in '/queue tree print stats', pcq-queues=?
still works fine for me, marking in 'forward', queues are under 'global'
still works fine for me, marking in 'forward', queues are under 'global'
Re: Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
It says:and what value you see in '/queue tree print stats', pcq-queues=?
still works fine for me, marking in 'forward', queues are under 'global'
Code: Select all
pcq-queues=1Btw, using version 6.32.4
Re: Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
we're using "action=same to-addresses=some.ip/25", and I see pcq-queues>400, for example (I should see not more than 128 if it were not working)Don't forget to use masquerade on the output interface.
Re: Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
So we agree that pcq-upload is currently not compatible with masquerade, right?
Re: Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
I didn't test it exactly with masquerade, I use generic src-nat. You may change "action=masquerade" to "action=same to-addresses=your.wan.ip.address" and recheck - this definitely works for me.So we agree that pcq-upload is currently not compatible with masquerade, right?
Re: Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
I only have 1 WAN IP address, can I use "same"?You may change "action=masquerade" to "action=same to-addresses=your.wan.ip.address" and recheck - this definitely works for me.
Re: Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
Sure. 1 IP address is whole /32 subnet
Re: Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
With connection tracking on, it definitely worksSo we agree that pcq-upload is currently not compatible with masquerade, right?
Re: Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
with connection tracking off, masquerade definitely does not workWith connection tracking on, it definitely works
Re: Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
Have you verified it personally in v6?With connection tracking on, it definitely worksSo we agree that pcq-upload is currently not compatible with masquerade, right?
Can you post a working example?
Re: Suggestion: make "PCQ-Upload" compatible with "Masquerade" again
I finally found the way.
You need simple queues (not queue tree)
Target must be the LAN interface.
Then you can specify the WAN interface as Dst (or use mangle to mark the upload).
Tested in ROS 6.38.7.
It also looks that my original example is working properly now, i'm not sure what happened.
You need simple queues (not queue tree)
Target must be the LAN interface.
Then you can specify the WAN interface as Dst (or use mangle to mark the upload).
Code: Select all
/queue simple
add dst=WAN max-limit=5M/100M name=PCQ queue=pcq-upload-default/pcq-download-default target=LAN
Tested in ROS 6.38.7.
It also looks that my original example is working properly now, i'm not sure what happened.
Who is online
Users browsing this forum: Bing [Bot], GoogleOther [Bot] and 86 guests