DHCP Problems

[mtlengel]

I emerged dhcp and set it up. I am using the sample dhclient-script file located in /sbin/
and this is my dhcpd.conf file located in /etc/dhcp

# dhcp.conf

# option definitions common to all supported networks...
# option domain-name "internal";
option domain-name-servers 192.168.100.2, 192.168.100.1;
option routers 192.168.100.100;
ddns-update-style none;

default-lease-time 600;
max-lease-time 7200;

subnet 192.168.100.0 netmask 255.255.255.0 {
range 192.168.100.10 192.168.100.190;
}

# example for a address that will be given to a fixed hardware (mac)

# host HPDesignJet500 {
# hardware ethernet 00:30:C1:C1:E7:99;
# fixed-address 192.168.100.99;
# option routers 192.168.100.100;
# option broadcast-address 192.168.100.255;

The printer already has a fixed IP so I have commented this out for now.

Dhcp starts up fine, but when I run dhclient to see what addresses have been assigned, the entire box crashes.

I read on another forum to change the dhcpclient-script to dhcpclient.script and it prevents the crash assigns an IP address, but I cant ping that address.

here is my if config

eth0 Link encap:Ethernet HWaddr 00:0E:0C:74:9D:16
inet addr:192.168.100.3 Bcast:192.168.100.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1689 errors:0 dropped:0 overruns:0 frame:0
TX packets:1978 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:174845 (170.7 Kb) TX bytes:926693 (904.9 Kb)
Base address:0xa400 Memory:ed800000-ed820000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Any ideas what the problem may be?

[1clue]

One thing that jumps out is that your router is in the middle of your dynamic IP pool. It's probably not what is giving you problems right now, but it will eventually cause you much grief. When the DHCP server assigns some box the same address as your router, you'll probably wind up with a client that can't network for some reason and you won't figure it out, or if for some reason the client comes up when the router is down, the entire network will no longer have outside access even though you can ping the router.

Another thing, I'd move the routers statement into the subnet it applies to.