shel

Has anyone gotten the DHCP daemon ronning in Fedora core 4? I have spent
hours trying to get it to work and can get the server going by some wierd
tactics, but not through the GUI or even by normal command-line methods.
Help would really be appreciated.

Shel

shel

Has anyone gotten the DHCP daemon ronning in Fedora core 4? I have spent
hours trying to get it to work and can get the server going by some wierd
tactics, but not through the GUI or even by normal command-line methods.
Help would really be appreciated.

Shel

tommy reynolds

1) In a separate window, as root, do this:

# tail -f /var/log/messages

and in another window do this:

# service dhcpd start

2) Send us a copy of the DHCP related messages you just got.

3) Do you have a correctly constructed "/etc/dhcpd.conf" file? What
does yours say?

Cheers

shel

Here are the files you requested;

from tail -f /var/log/messages, after doing a "service dhcpd start" that
failed,
__________________________________________________ __________________
Oct 27 11:53:46 localhost dhcpd: mailing list, please read the section on
the README about

Oct 27 11:53:46 localhost dhcpd: submitting bug reports and requests for
help.

Oct 27 11:53:46 localhost dhcpd:

Oct 27 11:53:46 localhost dhcpd: Please do not under any cir***stances send
requests for

Oct 27 11:53:46 localhost dhcpd: help directly to the authors of this
software - please

Oct 27 11:53:46 localhost dhcpd: send them to the appropriate mailing list
as described in

Oct 27 11:53:46 localhost dhcpd: the README file.

Oct 27 11:53:46 localhost dhcpd:

Oct 27 11:53:46 localhost dhcpd: exiting.

Oct 27 11:53:46 localhost dhcpd: dhcpd startup failed

__________________________________________________ __________________________

The dhcpd.conf file follows;

************************************************** **************************

ddns-update-style interim;

ignore client-updates;

subnet 192.168.1.0 netmask 255.255.255.0 {

range 192.168.1.200 192.168.1.225;

# --- default gateway

option routers 192.168.1.1;

option subnet-mask 255.255.255.0;

option nis-domain "sherman.com";

option domain-name "sherman.com";

option domain-name-servers 192.168.1.4, 151.164.14.201;

option broadcast-address 192.168.1.255;

option subnet-mask 255.255.255.0;

option time-offset -18000; # Eastern Standard Time

# option ntp-servers 192.168.1.1;

# option netbios-name-servers 192.168.1.1;

# --- Selects point-to-point node (default is hybrid). Don't change this
unless

# -- you understand Netbios very well

# option netbios-node-type 2;

# range dynamic-bootp 192.168.1.128 192.168.1.254;

default-lease-time 21600;

max-lease-time 43200;

# we want the nameserver to appear at a fixed address

# host ns {

# next-server beta.sherman.com;

# hardware ethernet 00:0f:ea:cc:ed:4c;

# fixed-address 192.168.1.4;

# }

}

************************************************** ****************************************

What is particularly confusing is that I can start the daemon by entering

/etc/rc.d/init.d/dhcpd start

and it will work. When I try to stop the daemon from this same shell it
fails. to turn it off I must start a new subshell by entering

bash /etc/rc.d/init.d/stop.

I am SO CONFUSED !

Shel

trog woolley

While stranded on the hard shoulder of the information super highway ssherm32@sbcglobal.net typed:

We use DHCP on FC4 without any problems. On our boxes dhcpd is started
at runlevel 5. Experience has shown that DHCP problems are caused by errors
in the dhcpd.conf file. Please state the exact nature of your problem.
What error messages are you seeing and where are you seeing them?

--
Trog Woolley | trog at trogwoolley dot com
(A Croweater back residing in Pommie Land with Linux)
Isis Astarte Diana Hecate Demeter Kali Inanna

ynotssor

Why not runlevel 3? Insisting that X be enabled on the dhcpd server seems a
bit absurd to me.

tommy reynolds

Hm.. how are you setting the IP address of the NIC that is listening
for the DHCP requests. Try configuring a fixed server address for
that NIC before attempting to start up the dhcpd daemon.

Cheers

shel

Thanks for the response everyone. I finally got things running. The original
install was dual boot, and when I reinstalled with only F4 on the hda drive
and reinstalled the dhcpd.conf file it worked fine in both command line and
gui modes. I am gonna go back to dual boot to verify that is the problem,
but I am pretty sure because the same thing happened on duplicate machines.

At least I am now off the side of the road on the information superhighway
:-)

Shel

trog woolley

While stranded on the hard shoulder of the information super highway ynotssor@example.net typed:

That's because we run the LTSP and that needs X to be of any use.
AFAIK when you configure the LTSP software it sets chkconfig to
run the dhcpd at runlevel 5. We could change it, but it ain't
broken so I'm not going to mend it.

--
Trog Woolley | trog at trogwoolley dot com
(A Croweater back residing in Pommie Land with Linux)
Isis Astarte Diana Hecate Demeter Kali Inanna

ynotssor

We use xvfb for any such applications, the X Virtual Frame Buffer in
runlevel 3. Far, far less overhead.