I have to agree with Girish. Take some time and find out the average bandwidth for your link. Then set the higher priority users a higher percentage of the total amount than the other users.
You could also use a script. If you know what the current upload bandwidth amount is then you could vary the "altq on $ExtIf bandwidth 744Kb" line to reflect this. If the rest of the queues are setup to use a percentage of the primary bandwidth amount then every thing will fall into line. Lastly, refresh pf for the new settings to take effect. Reference: http://calomel.org/pf_hfsc.html -- Calomel @ http://calomel.org Open Source Research and Reference On Fri, Nov 16, 2007 at 12:15:29PM +0530, Girish Venkatachalam wrote: >On 08:00:08 Nov 16, Jonathan Stewart wrote: > >> I though about doing something like that but the usable upload is so >> variable that 60% could completely knock the normal_folk off when it >> gets congested. I have 256kbit up right now and get anywhere from as >> low as 64kbit to 160kbit+ actual throughput depending on how busy the >> system is. If PF had a weighted round robin queuing system that would >> be almost perfect because then it would scale with the amount of >> bandwidth available. Ideally something that says if one queue has >> priority 5 and another 3 for every 5 packets sent from the first one 3 >> are sent from the other, unless there is something wrong with that I'm >> missing (other than increased jitter.) > >What is stopping you from using the priority field with HFSC? > >And why don't you determine the average uplink bandwidth statistically? > >If you measure it for a week or so and mark out the variance and figure >out the standard deviation or some such thing...then you can do what you >want. > >>From my experience with ADSL links I find that there is >usually not much variance in the uplink path. > >Is my reasoning correct? > >regards, >Girish
