about concept "group", "shared-network", and "subnet", thanks.

Marc Perea marccp at srttel.com
Wed Apr 20 14:45:00 UTC 2011


I'm going to pipe in here because I'm still a bit confused about the proper use of shared-network. What's the use case for it's proper use?
 
I'm currently configured with 2 shared-network statements, and I'm guessing it's wrong. My DHCP server resides on a single vlan, single interface. The interface is on our server VLAN, where it is not authoritative and I want to ignore booting. I made that one shared-network (ignore-me). Our BRAS is a L3 relay and directs all DHCP broadcast to unicast by IP to the server. I made this a 2nd shared-network. I originally had it all as one S-N, but dhcpd was still responding to requests on the server VLAN, so I moved it out to actually ignore booting. My configuration snip:
 
shared-network "ignore me" {
        subnet 1.2.3.4 netmask 255.255.255.128 { #SERVER VLAN
                ignore booting;
        }
}
shared-network "vlan 2" {
        subnet 10.1.0.0 netmask 255.255.255.224 { #TEST ISG-10K
                authoritative;
                ...
        }
        subnet 10.170.0.0 netmask 255.255.0.0 { #LOAD TEST
                authoritative;
                ...
        }
        subnet 10.2.0.0 netmask 255.255.192.0 { #PRODUCTION ISG-10K
                authoritative;
                ...
        }
        subnet 10.3.0.0 netmask 255.255.255.128 { #ASR1
                authoritative;
                ...
        }
}
Does this appear right or wrong? If it's wrong, any explanation of why moving the server subnet into the vlan-2 S-N would cause it to hand out IPs from one of the other subnets, instead of ignoring booting?
 
Thanks!
 
--Marc
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20110420/f114961b/attachment.html>


More information about the dhcp-users mailing list