why does dhcpd keep dying? kbdrate setting keeps getting reset?
I have a router susefirewall2 setup on machine w/dhcpd. Dhcpd keeps dying on me here is the .conf: authoritative ; ddns-update-style none; ddns-updates off; default-lease-time 36000; # 10 days log-facility local7; max-lease-time 72000; subnet 192.168.0.0 netmask 255.255.255.0 { option domain-name-servers 67.92.213.165, 64.200.255.12; option routers 192.168.0.1; option time-servers ntp.ucsd.edu; range 192.168.0.101 192.168.0.199; } also where to set the interface? i see in yast2, but where is it in the real world? And my kbdrate -r 30 keeps getting reset back to 10.3 cps ! how do i make this stay?? i have many machines and some work w/sysconfig, others not. -- Arden Bohanec Rosn.net (760) 726-2265 services@rosn.net Quality, Value, Service Support Freedom == Support Open Source The information contained in this transmission is privileged and confidential and intended only for the use of the individual or entity to whom it is addressed. If you are not the intended recipient, you are hereby notified that any distribution, copying, disclosure or taking of any action in reliance on the contents of this transmission is strictly prohibited and review by any individual other than the intended recipient shall not constitute waiver of privilege. If you have received this transmission in error, please notify us immediately and completely remove the original transmission.
On Tuesday 24 February 2004 09:51, acsab1@cox.net wrote:
I have a router susefirewall2 setup on machine w/dhcpd. Dhcpd keeps dying on me here is the .conf: authoritative ; ddns-update-style none; ddns-updates off; default-lease-time 36000; # 10 days log-facility local7; max-lease-time 72000;
subnet 192.168.0.0 netmask 255.255.255.0 { option domain-name-servers 67.92.213.165, 64.200.255.12; option routers 192.168.0.1; option time-servers ntp.ucsd.edu; range 192.168.0.101 192.168.0.199; } also where to set the interface? i see in yast2, but where is it in the real world?
The interface isn't configureable in the configuration file! Yucko eh? dhcpd is a painful piece of software, but it works. It's set on the command line when dhcpd is invoked. In Suse this is controlled by /etc/sysconfig/dhcpd. Either edit it directly or through yast2:System:Editor for /etc/sysconfig Files. Once you have the correct interface set, run /etc/init.d/dhcpd start It picks up the settings direct from that file, (and arranges the chroot jail if you've asked for that) You should see the requests and offers in /var/log/messages (unless your "local7" line puts them elsewhere) michaelj -- Michael James michael.james@csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166
participants (2)
-
acsab1@cox.net
-
Michael James