*** From dhcp-server -- To unsubscribe, see the end of this message. ***
> I.e., clients with odd addresses get routers .1 and .2, clients with
> even addresses get routers .2 and .1.
You can already do something like that on 3.0:
subnet 10.0.0.0 netmask 255.255.255.0 {
pool {
range 10.0.0.10 10.0.0.100;
option routers 10.0.0.1;
}
pool {
range 10.0.0.101 10.0.0.200;
option routers 10.0.0.2;
}
}
The bad news is that if you only have 90 clients on the net, you won't
get much load balancing, because they'll all get addresses from the
first pool. But if you make enough pools that they're sized to split
the load more evenly, you should be able to get some balancing out of
it.
A more general solution would be to maintain a monotonically-
increasing counter, and every time a lease is allocated, store the
value of that counter on the lease and increment it. Then whenever
the lease is renewed, use the stored value modulo the number of
addresses to order the address list.
_MelloN_
------------------------------------------------------------------------------
To unsubscribe from this list, please visit http://www.fugue.com/dhcp/lists
If you are without web access, or if you are having trouble with the web page,
please send mail to [EMAIL PROTECTED] Please try to use the web
page first - it will take a long time for your request to be processed by hand.
Archives for this mailing list are available at
http://www.webnology.com/list-archives/dhcp/dhcp-server
------------------------------------------------------------------------------
