James wrote:
>
> Mike if I understand you correctly I need to add.
> default-lease-time 7200;
> max-lease-time 82400;
> option subnet-mask 255.255.255.0;
> option broadcast-address 12.234.130.255;
> option routers 12.234.130.1;
> option domain-name-servers ;
> option domain-name "linuxpda.biz";
> subnet 12.234.130.0 netmask 255.255.255.0{}
>
> Now the question comes. What happens if the subnet I'm on from my ISP
> changes? Gateway and subnet have changed twice since the @home fiasco.
>
> James
>
> Now to sorta answer my own question the dhcpd -q eth1 solved the problem
> it starts and only looks at the internal nic. Thanks loads for the help.
>
> James
>
James,
Sorry it's taken me so long to respond - I've been out.
I'll include our config file for you to look at - but you've
pretty much got it. Note the last couple of lines. If your
ISP changes the network you're on then you would have to
update this file to reflect the change. I would hope though
that there wouldn't be too many @home type messes and that
this wouldn't be needed very often. Or, you can use the
solution which you've already found by starting it at the
command line though that would appear to preclude the use of
your distributions startup scripts for the DHCP server
service.
# Dynamic Host Configuration Protocol
# DHCPd Daemon Configuration File
# MHR last updated July 2001
# dlt=43200sec=12hours, mlt=259200sec=72hours
#
default-lease-time 43200;
max-lease-time 259200;
option domain-name-servers 192.168.1.1, 207.73.196.250;
option domain-name "ourdomain.local";
# wins server - hybrid type (wins - broadcast)
option netbios-name-servers 192.168.1.1;
option netbios-node-type 8;
# ddns-update-style can be 'none', 'ad-hoc', or 'interim'
ddns-update-style ad-hoc;
ddns-domainname "ourdomain.local";
ddns-rev-domainname "in-addr.arpa";
# primary LAN - we leases addresses here
subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.20 192.168.1.250;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
option routers 192.168.1.1;
# dynamically update DNS records for the local zone
key DHCP_UPDATER {
algorithm HMAC-MD5.SIG-ALG.REG.INT;
secret qz<munged>I==;
};
zone OURDOMAIN.LOCAL. {
primary 127.0.0.1;
key DHCP_UPDATER;
}
zone 1.168.192.in-addr.arpa. {
primary 127.0.0.1;
key DHCP_UPDATER;
}
}
# our gateway LAN - we do not lease addresses here
subnet 10.8.24.0 netmask 255.255.255.0 {
}
Hope this helps.
--
Mike Rambo
[EMAIL PROTECTED]
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
