Hi Bray
What do the logs say?
Also, try running dhcpd with -d -f
-d Force dhcpd to log to stderr. This can be useful for
debugging,
and also at sites where a complete log of all dhcp
activity must
be kept, but syslogd(8) is not reliable or otherwise
cannot be
used. Normally, dhcpd will log all output using the
syslog(3)
function with the log facility set to LOG_DAEMON.-f Run dhcpd as a foreground process, rather than allowing
it to run
as a daemon in the background. This is useful when
running dhcpd
under a debugger, or when running it out of inittab on
System V
systems.On 26 Feb 2007, at 00:45, Bray Mailloux wrote:
> I've been toying with the DHCP server options but cannot seem to
| KOSAKI Motohiro | [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
| Faik Uygur | Re: Linux 2.6.21-rc1 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Trent Piepho | [PATCH] [POWERPC] Improve (in|out)_beXX() asm code |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
