=?iso-8859-1?B?UulmLiA6IFJlOiBJU0MgREhDUCAzLjAuNHJjMSBpcyBub3cgYXZhaWxhYmx lISA?=

[Simon Hobson]

JVNC04 Yahoo wrote:

>I'm using DHCP 3.0.3-2 Intregrated on SUSE 10.
>
>The problem is that when I want to configure a pool out or range of the
>network PC, the SuSE GUI refuse to configure it (because out of range).

Sounds like a GUI problem specific to Suse.

>The only purpose is to to configure as following:
>
>Adminrf4:~ # more /etc/dhcpd.conf
>Option domain-name-servers 202.87.129.35;
>Option routers 202.87.145.1;
>Ddns-update-style none;
>Default-lease-time 14400;
>Subnet 202.87.129.64 netmask 255.255.255.224 {
>   Default-lease-time 14400;
>   Max-lease-time 172800;
>}
>Adminrf4:~ #
>
>My DHCP Server is ont the pool 202.87.129.64/27. Note that Option routers
>accept any IP value (out of range).
>
>
>When I try to modify manually the dhcpd.conf file as following:
>
>Adminrf4:~ # more /etc/dhcpd.conf
>Option domain-name-servers 202.87.129.35;
>Option routers 202.87.145.1;
>Ddns-update-style none;
>Default-lease-time 14400;
>Subnet 202.87.145.0 netmask 255.255.255.224 {
>   Range 202.87.145.2 202.87.145.5;
>   Default-lease-time 14400;
>   Max-lease-time 172800;
>}
>Adminrf4:~ #
>
>I can't start dhcp service.

At a rough guess, there are messages in the logs somewhere that you 
must have a subnet definition for the local interface.

>* is it possible with ISC to configure and to use IP pool NOT on same range
>as DHCP Server ?

Yes. What you want is something like :

Ddns-update-style none;
Option domain-name-servers 202.87.129.35;
Default-lease-time 14400;
Max-lease-time 172800;
Subnet 202.87.129.64 netmask 255.255.255.224 {
   Option routers 202.87.129.65;
   Range 202.87.129.66 202.87.129.70;
}
Subnet 202.87.145.0 netmask 255.255.255.224 {
   Option routers 202.87.145.1;
   Range 202.87.145.2 202.87.145.5;
}

If you don't want to actually give out any leases in the local 
subnet, then just omit the range statement - but you MUST still have 
the subnet definition.

>* is possible with ISC to work with MORE than one DHCP server instance on
>same linux BOX (i.e.. Different pool)?

Not really, but that's not an ISC issue, it's because clients will 
expect to reach the DHCP server at a specific port - if you run a 
separate instance on a different port then the clients would not know 
how to access it.

Simon