DHCP setup problems for development board connection on Fedora10

Hi all,
I'm still fairly new to Linux so please forgive me if my description of my problem leaves out important information. My problem is centered around using a AT91SAM9G45 development board (DB)on Fedora 10. I have directions on how to setup on my host machine a DHCP server to connect to the development board. I have installed an additional network card (eth1) that will be used exclusively to communicate with my DB.

The DB has been setup with an ethaddr=12:34:56:78:9a:bc and an ipaddr=192.168.251.191.

The following is info from ifconfig for eth1:

eth1 Link encap:Ethernet HWaddr 00:0A:5E:1A:46:1C
inet addr:192.168.251.190 Bcast:192.168.251.255 Mask:255.255.255.0
inet6 addr: fe80::20a:5eff:fe1a:461c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:38 errors:0 dropped:0 overruns:0 frame:0
TX packets:4031 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2432 (2.3 KiB) TX bytes:1076162 (1.0 MiB)
Interrupt:17

Using the above info, I have setup my dhcpd.conf file as follows:
#
lease-file-name "/var/lib/dhcpd/dhcpd.leases";
ddns-update-style ad-hoc;
subnet 192.168.251.0 netmask 255.255.255.0
{
host AT91SAM9G45-EK
{
fixed-address 192.168.251.191;
hardware ethernet 12:34:56:78:9a:bc;
option root-path "/tftpboot/3DX_rfs";
next-server 192.168.251.190;
filename "uImage-2.6.36-ts-armv5l";
}

}

When I test the DHCP server using: /usr/sbin/dhcpd -d eth1, I get the following output:

Internet Systems Consortium DHCP Server 4.0.0
Copyright 2004-2007 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
WARNING: Host declarations are global. They are not limited to the scope you declared them in.
Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not specified in the config file
Wrote 0 deleted host decls to leases file.
Wrote 0 new dynamic host decls to leases file.
Wrote 0 leases to leases file.
Listening on LPF/eth1/00:0a:5e:1a:46:1c/192.168.251.0/24
Sending on LPF/eth1/00:0a:5e:1a:46:1c/192.168.251.0/24
Sending on Socket/fallback/fallback-net

The function never returns. In addition it appears to be listening and sending on the wrong ip, 192.168.251.0/24. Does anybody have any ideas, corrections, advice?

Thanks,
Joe

The -d flag also implies the -f flag which prevents the daemon from forking to the background. Therefore it never returns to a command prompt.
At first glance it appears to be working correctly. You can get rid of the warning message if you move the host declaration outside the subnet declaration. Does the development board acquire an IP address?

michelk,
I wasn't aware of the side affect of using the -d flag, that's good to know. I only setup my host declaration inside the subnet because that is how the example I was given showed it. I will move it outside to avoid the message. As for the board acquiring an IP address, up to this point it hasn't, at least not that I can tell. But yesterday I finally got TFTP and NFS working on the board using a fixed IP address, so DHCP is not as important as it originally was. I can now at least move forward, but I still at some point in the future would like to understand and get the DHCP working. Thanks for the response.