From owner-freebsd-current@FreeBSD.ORG  Fri Feb  6 21:54:12 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A616316A4CE
	for <freebsd-current@freebsd.org>;
	Fri,  6 Feb 2004 21:54:12 -0800 (PST)
Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C2D7F43D1F
	for <freebsd-current@freebsd.org>;
	Fri,  6 Feb 2004 21:54:11 -0800 (PST)
	(envelope-from dwhite@gumbysoft.com)
Received: by carver.gumbysoft.com (Postfix, from userid 1000)
	id B5A3B72DC9; Fri,  6 Feb 2004 21:54:11 -0800 (PST)
Received: from localhost (localhost [127.0.0.1])
	by carver.gumbysoft.com (Postfix) with ESMTP
	id B344272DB5; Fri,  6 Feb 2004 21:54:11 -0800 (PST)
Date: Fri, 6 Feb 2004 21:54:11 -0800 (PST)
From: Doug White <dwhite@gumbysoft.com>
To: Jimmy Firewire <trigonometric@softhome.net>
In-Reply-To: <01ae01c3ec28$00f4b530$0601a8c0@SPECULUSHX1THE>
Message-ID: <20040206215241.W20729@carver.gumbysoft.com>
References: <01ae01c3ec28$00f4b530$0601a8c0@SPECULUSHX1THE>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-current@freebsd.org
cc: Kris Kennaway <kris@obsecurity.org>
Subject: Re: RSA/DSA Host key generation didn't happen (because sshd wasn't
 enabled on boot)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Feb 2004 05:54:12 -0000

On Thu, 5 Feb 2004, Jimmy Firewire wrote:

> > And also, using dhclient doesn't work properly. Touching /etc/resolv.conf
> > causes the file to be populated with the line:
> >
> > nameserver 192.168.1.23
>
> Something really strange something happened on this boot:
>
> It hung on
>
> Configuring syscons: keymap keyrate blanktime

What runs after that is probably blocking on a reverse DNS lookup.  If
resolv.conf isn't getting written properly for you, then that would be a
cause. Typically dhclient will hang around for a few seconds to make sure
it gets the lease before continuing to avoid this sort of problem.

You might want to see if you can run tcpdump or somesort of network trace
on your DHCP server (if you have control of it) and see what the
client/server communication looks like.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite@gumbysoft.com          |  www.FreeBSD.org