On Sun, 2011-02-06 at 12:35 -0400, Optimum Wireless Services wrote: > > > > I think that you should forget the per-user stuff as per my other email > > and classify traffic. Just my personal opinion - I'd be interested to > > hear what others think. > > I just need a way that would allow users to experience a reliable > connection that would always be 15% +- the contracted bandwidth. > You could buy some more upstream bandwidth ;-) Have you tried the scripts that Marek posted? That's your answer to limit per user. > This turned to be more complicated than what I first thought. > > After adding the new ruleset, I added this little script to try to > prioritize some traffic, just installed it so, don't know yet how would > traffic behave: <snip> Herein lies your problem. If you want to prioritise traffic *and* limit per user, then it starts to get complicated. The rules that you posted will indeed rate limit different types of traffic, but you would need to do these in conjunction with your other HTB rules for the different users. So you would need separate classes for users and traffic type. They'd have to be parents/children of each other, but which way round and how you would do it I do not know. All I'm saying is that you need to take this one step at a time. Getting a magic solution that does everything is not going to happen straight away (unless somebody tells me otherwise). So, try the per user stuff on its own first. Maybe try the traffic prioritisation on its own as well. Check the results and take it from there. BTW - I don't think the traffic prioritisation scripts you posted will have much affect anyway: they are only really looking at DNS lookups and SSH, which isn't going to solve your problems. Andy -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
