Skip site navigation (1)Skip section navigation (2)
Date:      08 Nov 2004 09:29:47 -0500
From:      Lowell Gilbert <freebsd-questions-local@be-well.ilk.org>
To:        Gary Kline <kline@magnesium.net>
Cc:        FreeBSD Mailing List <freebsd-questions@FreeBSD.ORG>
Subject:   Re: dhcpd (reprise)
Message-ID:  <44y8hcjtwk.fsf@be-well.ilk.org>
In-Reply-To: <20041108035806.GA54930@toxic.magnesium.net>
References:  <20041105233628.GA33632@toxic.magnesium.net> <44hdo16376.fsf@be-well.ilk.org> <20041107195036.GC30315@toxic.magnesium.net> <443bzlyufp.fsf@be-well.ilk.org> <20041108035806.GA54930@toxic.magnesium.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Gary Kline <kline@magnesium.net> writes:

> On Sun, Nov 07, 2004 at 08:56:58PM -0500, Lowell Gilbert wrote:
> > Gary Kline <kline@magnesium.net> writes:
> > 
> > > 	I'll add the -d flag to my rc.conf; are you using the latest
> > 
> > No; *disable* dhcpd from rc.conf, and start it by hand with the -d flag.
> > 
> > > 	version of the dhcp-server from ISC or something other?
> > 
> > I'm running the ISC dhcp server, as I mentioned in my message, and
> > it's fairly up-to-date, but I don't think the exact version matters
> > for you (at least not at this point).
> > 
> > > 	I looked for a 'debug' flag on the man page and didn't see it.
> > 
> > >From "man dhcpd":
> >        To have dhcpd log to the standard  error  descriptor,  specify  the  -d
> >        flag.  This can be useful for debugging, and also at sites where a com-
> >        plete log of all dhcp activity must be kept but syslogd 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.
> > 
> > > 	What should I loook for in th logfile?  or will it be 
> > > 	obvious :-)
> > 
> > Again, the approach I'm describing will *not* log into the logfile;
> > I'm suggesting you get the debug output on a console in real time.
> 
> 
> 	Okay. This is all that is output to stderr:
> 
> 
> No subnet declaration for dc0 (216.231.43.140).
> ** Ignoring requests on dc0.  If this is not what
>    you want, please write a subnet declaration
>    in your dhcpd.conf file for the network segment
>    to which interface dc0 is attached. **
> 
> Sending on   Socket/fallback/fallback-net
> 
> 	I've seen this before.  What does the last line mean?
> 	Or, how do I test this?  I've just tried ssh'ing
> 	around.  Nothing to the screen.


This is telling you that the machine doesn't know how to assign
addresses for DHCP requests that come in on the dc0 interface.  If
that's correct (i.e., you want it to assign addresses on some other
interface but not that one), then everything's fine so far.  If it's
not, then you need to modify your dhcpd.conf as it said.

If everything is okay on that front, then you need to get some of the
other machines (the ones to which this server should be assigning
addresses) to ask for leases.  How to do this depends on what OS they
are running, but rebooting should do it in any case.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44y8hcjtwk.fsf>