request for advice / building dhcpd infraestructure
Leandro
ingrogger at gmail.com
Tue Jun 23 17:00:03 UTC 2015
Thank you Bob , I will try !!
Leandro.
On 23/06/15 13:14, Bob Harold wrote:
>
>
> On Tue, Jun 23, 2015 at 11:54 AM, Leandro <ingrogger at gmail.com
> <mailto:ingrogger at gmail.com>> wrote:
>
> Hello dhcpd users:
> Im planning to manage a /17 network using isc dhcpd. I would like
> to briefly describe my plan so I can get any comments/advices
> from the list.
> My dhcp server will receive requests from approximately 20 relay
> agents from 3 different access technology.
> I dont know in advance behind wich relay will be most ip usage
> since I can not predict witch service will grown over the others.
> In order to be able to be flexible with ip pools management, Im
> thinking on:
>
> Create a class per each agent.circuit-id
> Subneting the /17 in /24 subnets
> Create a pool declaration per each subnet.
> Add / Delete "allow members of" statements within the pool
> declaration to bind a relay-agent with one or multiple pool
>
> I also would like to create a default class just in case I can not
> get the option 82 info from some relay-agent, I dont know how to
> do it yet.
> It would be for example with 3 class and 3 pools:
>
> #########################################
> class "fth_clients" {
> match if option agent.circuit-id = "fth_relay";
> }
>
> class "adsl_clients" {
> match if option agent.circuit-id = "adsl_relay";
> }
>
> class "default_clients" {
> match if option agent.circuit-id = ""; #need to
> confirm
> }
>
>
> If it does not work as written, then maybe you could try:
> match if not( option agent.circuit-id = "fth_relay" or option
> agent.circuit-id = "adsl_relay" );
> (That does not scale well, but should work for a small number of classes.)
>
> --
> Bob Harold
>
>
>
> shared-network my_pool {
> subnet 1.1.1.0 netmask 255.255.128.0 {
>
> #1.1.1.0/24 <http://1.1.1.0/24> for all clases
> pool {
> range 1.1.1.2 1.1.1.254;
> option broadcast-address 1.1.1.255;
> option subnet-mask 255.255.255.0;
> option routers 1.1.1.1;
> allow members of "fth_clients"
> allow members of "adsl_clients"
> allow members of "default_clients"
> }
>
> #1.1.2.0/24 <http://1.1.2.0/24> only for adsl_clients
> pool {
> range 1.1.2.2 1.1.2.254;
> option broadcast-address 1.1.2.255;
> option subnet-mask 255.255.255.0;
> option routers 1.1.2.1;
> allow members of "adsl_clients"
> }
>
> }
> }
>
> ###################################33
> Any comment / Advice will be accepted,
> Thanks!!!
> Leadro.
>
>
>
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20150623/304da6f2/attachment.html>
More information about the dhcp-users
mailing list