Hello!, we’re dealing with some queue and priorization issues, I’ll explain my scenario:
I’m running a queue tree where I have defined two parents (one for upstream and one for downstream), each parent limited to my real bandwith assigned by my privoder (let’s say 1Mbps up/down), inside each parent I have defined some priorization rules based on protocols and other issues, for example low priority for p2p and heavy streammers (using connecting-bytes and connection-speed) and high pri for voip, http, etc.
All my actual clients (residential until now) go trought those queues and all works like a charm.
Now I’m trying to implement other profile of service for enterprises or corporations, let’s say Corporate Access, I want to keep my priorization structure by protocols (p2p, http, voip, etc) in each access profile (Residential and Corporate) but also I wan’t to priorize corporate traffic over residential traffic.
Here is where I come with questions about the best way to implement this functionality.
My first question is with the packet mark (mangle), at time I’m only marking packets based on protocols, now I’m think I need to mark packets based on protocols and source IP pools (I’m planning to use different IP pools to distinguish residential and corporate traffic), I guess if there is any way to mark those packets without writing each protocol mangle rule twice.
Then, the other big question is how to implement the queue tree. I think in a three level queue (download/upload, residential/corporate and the third level based on each protocol I wan’t to priorize)
PS: At the end of writing this email I’m thinking to use TOS bit at IP header to mark corporative traffic and then mangle it by protocol…
I will expend several weeks triying to doing work the priorities in simple queues at the same time I use pcq trees in the same rb to assign individual BW to each customer. I cannot. I read in this forum others triying the same, and they cannot too. Maybe I missing something, but I test all possible options.
Tired to try and nock my head to the wall I try the B Plan.
My next solution was divide the BW management in two parts (two devices): one rb with simple queues with mangle and prioritization to ip pools (or any other general mark: example: access list or pc bytes or speed, etc), in transparent bridge mode, connected to other rb with pcq trees to assign individual bw to each customer by ip.
After that everything goes like a charm.
The schema is:
customers → rb with simple queues to groups accordingly to her mangle marks (bridge mode) → rb with with pcq tree to assign bw individual to each customer (ip) in bridge mode too → router → internet
At the first level I assign priorities, and goes down heavy traffic or youtube or streamings, while prioritize web, mail, etc in simple queues. At the second level I limit the bw to each client. At the third level everybody are happy (me and my customers).
Yes, two rb are more expensive than only one, but, how much does cost the happiness???
I understand your scenario, is different from mine, I’m using PPPoE and radius.
In my network I have several PPPoE concentrators, bw limit of customers was limited with simple queue in each concentrator, those simple queues are created dynamically when ppp go up, then, traffic priorization based on protocol was done in my border router with mangle and queue tree.
