throttling individual dhcpd clients
I have 2 multipathed external links and one internal link which has dhcpd on it and is masqueraded.
I have begun with ahu's script on the two external links and things look good there too.
At this point I am only using the ingress policer on each external, but want to use a tbf (or recommendation) on the internal interface instead.
The thing is, it is needed that each lease be given a certain amount of bandwidth with borrowing. I don't think there is any good way to do this other than building each of them their own qdisc.
I wonder if anyone has any tips one how to keep the rules in sync with the dynamic nature of the ip's? I suppose, one could just build for all possibilities. Also, I read somewhere that a script could be named dhcpd.exe which would run after each lease and thought that might be the way to go.
Thoughts? I'd especially like to hear someone call me an idiot for thinking it would have to be that complicated...
Signature · 6 lines
Regards, Paul Evans _______________________________________________ LARTC mailing list / [email protected] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
Quoted 6 lines · Paul Evans
I have 2 multipathed external links and one internal link which has dhcpd on it and is masqueraded.
I have begun with ahu's script on the two external links and things look good there too.
Quoted 6 lines
At this point I am only using the ingress policer on each external, but want to use a tbf (or recommendation) on the internal interface instead.
The thing is, it is needed that each lease be given a certain amount of bandwidth with borrowing. I don't think there is any good way to do this other than building each of them their own qdisc.
You have to add a htb qdisc and 1 class. That class holds all traffic leaving the box. You also have to create 1 class for each dhcp client and put it's traffic in that class.
Quoted 8 lines
I wonder if anyone has any tips one how to keep the rules in sync with the dynamic nature of the ip's? I suppose, one could just build for all possibilities. Also, I read somewhere that a script could be named dhcpd.exe which would run after each lease and thought that might be the way to go.
Thoughts? I'd especially like to hear someone call me an idiot for thinking it would have to be that complicated...
You can create for each ip a class and put the traffic to that ip in it's own class. If each dhcp client has the same bandwidth, you can create a set of static filter rules so each ip end up in it's class. If you have different bandwidth requirements you have to update the filter rules so traffic for a pc always end in the same class. I have no idea how you can trigger dhcpd to do this.
Stef
Signature · 8 lines
[email protected] "Using Linux as bandwidth manager" http://www.docum.org/ #lartc @ irc.oftc.net _______________________________________________ LARTC mailing list / [email protected] http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/