On Thu, 2007-03-29 at 00:54 +0200, Paul wrote:

> >   
> Yes, I'm doing some work on this side already.
> > i felt that the issue with altq and queues qas you need a new parent
> > queue each time you add a new user this makes it far more complicated
> > than the dummynet method where you can still have differnet classes
> >   
> I'm under the impression that pfsense uses the hsfc classifier. In an 
> ISP grade server you would reserve more resources to higher-paying 
> customers by using different classes. Then in each class the customers 
> would be able to use their allocated bandwidth without interference from 
> customers in the lower or higher classes. Traffic will be borrowed only 
> if one class is not using it's resources. You would have a 2 level 
> limiter, where each ng channel is limited to the maximum up/down rate of 
> the customer and then a second limiter where you allocate more resources 
> where needed.
> 
> Example:
> 5 customers with 640k contract
> 5 customers with 2M contract
> If every customer is equal to the others, they will all go at the same 
> speed, but if you put the 10 customers in 1 class and the 5 customers in 
> another class and then give different speeds to each of them you'll be 
> able to keep the 640k customers at say 500k and the 2Mega customers at 
> say 1.5M.
> 

> > i was under the understanding that altq did not work well with multiple
> > interfaces or is this just an issue with the pfsense implementation
> >   
> I have no idea. My guess is that you need the max speed limiter on ng 
> and then a set of queues on the "wan" interface. Perhaps some packet 
> tagging can take place so that packets go to their queue.
max speed limit on the ng will only manage the ng one way i think. would
love some input from pfsense dev's on the possiblity of altq from radius
with pppoe pptp etc

> > this is the primary area that i would like to see worked on the
> > termination of aaa well is a real enterprise class thing and pfsense is
> > so close with ipsec openvpn and pppoe and pptp terminations intergrated
> > well it would be fantastic.
> >   
> One more thing will be needed for full AAA and this is a port of the 
> bpfinet and tcp_mss modules from bsd5 to 6. I'm not fluent enough with 
it looks like the tcp_mss is in the 6.2 P3 kernel correct me if i am
wrong. 

> the bsd kernel to do it myself....

i think the next step is to test this on pfsense again will download
your version and take a look be back to you soon
> 
> Btw all docs can be found here: http://www.foggy.ru/soft/mpd/
> 
> Paul.

Reply via email to