Date: Fri, 6 Feb 2004 21:54:11 -0800 (PST) From: Doug White <dwhite@gumbysoft.com> To: Jimmy Firewire <trigonometric@softhome.net> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: RSA/DSA Host key generation didn't happen (because sshd wasn't enabled on boot) Message-ID: <20040206215241.W20729@carver.gumbysoft.com> In-Reply-To: <01ae01c3ec28$00f4b530$0601a8c0@SPECULUSHX1THE> References: <01ae01c3ec28$00f4b530$0601a8c0@SPECULUSHX1THE>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040206215241.W20729>