8) Et voila! That's why I asked this question - the half of Mikrotik community thinks that priority works with "max-limit" on each child queue only, the other half - with "max-limit" on parent queue, and the third half :) - with "limit-at" only. But in examples in the m...

Yes, according to "...to child queues so that they are able to reach max-limit" . But "Priority is responsible for distribution of remaining parent queues traffic..." tells me something different. So, if we don't have limit in parent queue, we have no remaining traffic in it too.

OK, but let's go back to the manual here: "We already know that limit-at (CIR) to all queues will be given out no matter what. Priority is responsible for distribution of remaining parent queues traffic to child queues so that they are able to reach max-limit Make a note that priority only work...

Oh my friend, you brought even more confusion, not clearness. In the past, in old versions of the manual, I remember it was written in this way, but look at the new wiki: "Child queue with higher priority will have chance to reach its limit-at before child with lower priority and after that chi...

read this topic: http://forum.mikrotik.com/viewtopic.php?f=2&t=27555
and watch this video: http://www.tiktube.com/?video=214

Well, I read it. And watched the movie too. This phrase ("priority doesn't work without limitation") is present in both places, but that's all, nothing more.

Nobody knows?

What exactly mean "priority doesn't work without limitation":

1) priority doesn't work without limitation in parent queue;
2) priority doesn't work without limitation in each child queue;
3) both?

Tx

OK, after several additional tests, I think the problem is that we can't mark same connections simultaneously in "prerouting" and "forward" by different criteria. Packets - yes, but connections - no. Otherwise strange things happen. So, if you use mark connection -> mark packet i...

No, I know that. You don't understand me... My point is, when you mark connection for some reason in "prerouting" whit src. port 80 (or else), this connection become unmarkable in "forward" whith src. address. Simply pass through. But it is sufficient to disable the rule in "...

No, it's just an example. But why is this happening? I thought that the two chains are completely independent of each other...
Appears that they are not, or I do not understand something...

For example: If we have in prerouting 1 chain=prerouting action=mark-connection new-connection-mark=http passthrough=yes protocol=tcp src-port=80 In forward 2 chain=forward action=mark-connection new-connection-mark=cl-conn passthrough=yes src-address-list=Clients 3 chain=forward action=mark-packet ...

In some of our tests we found that if we mark connection in "prerouting", for example with src. port 80, it is not possible to mark this connection again in "forward" with src. address or list. When we mark packet directly, this is not happen. Where is the mistake or this is a bu...

I think, 13 - 14 Mbps is maximum data rate that one pcq queue can handle. When I set 20M, for instance, nothing's happen - always 13-14 max.
Is that correct, or I miss somethimg?
Tanks

Hmm... But it basically works, the problem occur only in websites with user/pass, and not in all sites, just a few. It's no sense using src-nat to map, say 254 private adressess to same range real ones.

Yes, I know that, but I look for some elegant way to solve the problem.

ICQ? A? :)

When I use src-nat to hide all my private network 192.168.x.x/24 behind a range of real IP-adresses, say x.x.x.65 - x.x.x.69, strange things happen - some sites with loging/password (mail, bank-services) frequently loses connection and you must reconnect and loging again. Any suggestion or help? Tha...

Why don't you simply route the public IPs (subnet) inside the LAN?

I will like to know if there is a way to create a simple queue for a whole IP class on the 2.8 versions.
For example

10.10.10.0/32

For whole class C use 10.10.10.0/24

I will like to know if there is a way to create a simple queue for a whole IP class on the 2.8 versions.
For example

10.10.10.0/32