*** From dhcp-server -- To unsubscribe, see the end of this message. ***
"Roderick B. Greening" wrote:
>
> According to the version I am using (dhcp-2.0b1pl6-2) you cannot give a
> group a name. This is mute of course, unless there is a way to associate
> the group with a given subnet by using a name (not in version 2).
>
> I guess the bottom line is that I need version 3 for my situation.
Not necessarily. If you enclose the group within a subnet statement,
you get the same effect as associating the group by name to a subnet,
e.g
subnet 10.1.3.0 netmask 255.255.255.0 {
range 10.1.3.10 10.1.3.100;
option routers 10.1.3.1;
option option-67 basic.cfg;
group {
option option-67 gold.cfg;
host { hardware ethernet de:ad:be:ef:ca:fe; }
}
group {
option option-67 silver.cfg;
host { hardware ethernet ca:fe:de:ad:be:ef; }
}
}
All clients receive basic.cfg except dead.beef.cafe which receives
gold.cfg and cafe.dead.beef which receives silver.cfg. However, ALL
clients will receive addresses from the range 10.1.3.10 to 10.1.3.100
and they also receive the routers option 10.1.3.1.
As far as I can tell, the only advantage of naming a group and then
including the group name in the subnet statement is that you wouldn't
have to worry about nesting rules and you could place your group
statement anywhere outside of subnet statements. This could be a good
thing though, since you could put your groups at the top of your config
file to make managing exceptions (groups) to the rule (subnets) easier
to find since its the exceptions that usually require more attention.
Cheers,
Matthew
- Matthew
>
> On Tue, 27 Apr 1999, Matthew Levine wrote:
>
> > Ted, correct me if I'm wrong.
> >
> > I believe options are options and wherever they exist they will be used
> > UNLESS you override them in a subnet, host, or group stanza. I'm not
> > familiar with pools which is why I won't include them in this
> > discussion.
> >
> > Anyway...
> >
> > subnet
> > This is obvious, configure subnet specific options in subnet statements
> > - things like routers, subnet mask, broadcast address, address range,
> > etc.
> >
> > host
> > This is how you can single out a device in a subnet but I believe you
> > can write a host statement outside a subnet statement which has the
> > effect of a one fixed address pool. You use host statements to override
> > options on a per host basis. In your case, you'd be interested in
> > option-67 depending on who paid for what services you want to be sure
> > their modem gets the config file they deserve.
> >
> > group
> > This is how you could group hosts together so for all the customers who
> > paid for the kitchen sink level of services, you can group all those
> > hosts into the kitchen sink group and then serve them all the same
> > configuration file, e.g.
> >
> > group kitchen-sink {
> > option option-67 "kitchensink.cfg";
> >
> > host { hardware ethernet de:ad:be:ef:ca:fe; }
> > host { hardware ethernet ca:fe:de:ad:be:ef; }
> > }
> >
> > You'll note that I left off the fixed-address option. If you enclose
> > this group statement in a subnet statement, you give these hosts
> > addresses out of the subnet range but they will get the kitchen sink
> > config file whereas the rest may only get the basic configuration file,
> > e.g.
> >
> > subnet 10.20.30.0 netmask 255.255.255.0 {
> > range 10.20.30.100 10.20.30.200;
> > option routers 10.20.30.1;
> > option option-67 "basic.cfg";
> >
> > group kitchen-sink {
> > option option-67 "kitchensink.cfg";
> >
> > host { hardware ethernet de:ad:be:ef:ca:fe; }
> > host { hardware ethernet ca:fe:de:ad:be:ef; }
> > }
> > }
> >
> >
> > How did I do Ted?
> >
> > Cheers,
> > Matthew
> >
> > PS Did you try 'man dhcpd.conf'? Just had to ask.
> >
> > "Roderick B. Greening" wrote:
> > >
> > > *** From dhcp-server -- To unsubscribe, see the end of this message. ***
> > >
> > > Is there a document somewhere that describes what the conf relationships
> > > are between groups, pools, subnets, hosts and shared networks?
> > >
> > > For example,
> > >
> > > group ---> shared-network
> > > subnet
> > > host
> > >
> > > shared-network ---> subnet
> > > host
> > > pool
> > >
> > > The idea is to show what a group, etc, can contain. From my read of the
> > > docs, I cannot seem to get an absolutely clear picture of the
> > > relationships.
> > >
> > > If anyone can shed some light on this, I would appreciate it, as I am sure
> > > others would.
> > >
> > > Thanks in advance.
> > > [Lost in the tangle]
> > >
> > > Roderick B. Greening, BSc. |
> > > Network Specialist | [EMAIL PROTECTED]
> > > Cable Atlantic Inc. |
> > >
> > > ------------------------------------------------------------------------------
> > > 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
> > >
> > > ------------------------------------------------------------------------------
> >
> > --
> > ---
> > ------
> > Matthew Levine
> > Quality Assurance (SW Initiatives - Broadband)
> > Cisco Systems, Santa Cruz http://www.cisco.com/
> > [EMAIL PROTECTED] (831) 457 - 5431
> >
>
> Roderick B. Greening, BSc. |
> Network Specialist | [EMAIL PROTECTED]
> Cable Atlantic Inc. |
--
---
------
Matthew Levine
Quality Assurance (SW Initiatives - Broadband)
Cisco Systems, Santa Cruz http://www.cisco.com/
[EMAIL PROTECTED] (831) 457 - 5431
------------------------------------------------------------------------------
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
------------------------------------------------------------------------------
