Date: Thu, 5 Feb 2004 20:38:25 -0000 From: "Jimmy Firewire" <trigonometric@softhome.net> To: "Jimmy Firewire" <trigonometric@softhome.net>, "Kris Kennaway" <kris@obsecurity.org> Cc: freebsd-current@freebsd.org Subject: Re: RSA/DSA Host key generation didn't happen (because sshd wasn't enabled on boot) Message-ID: <01ae01c3ec28$00f4b530$0601a8c0@SPECULUSHX1THE>
next in thread | raw e-mail | index | archive | help
> 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 but the gateway flags are still UGS instead of UGSc under netstat -r so I tried to reboot but the same thing happened. So I tried to have the interface configure automatically at boot, but it won't ping external hosts but it resolves the hostnames. Something really strange something happened on this boot: It hung on Configuring syscons: keymap keyrate blanktime for about a minute, but this only happened after I tried to automatically enable dhcp on an interface at boot. So I just tried taking it out the ifconfig_rl0="DHCP" line again and rebooted, and it did not hang (this was also when I had enabled sshd_enable, so it two changes to rc.conf). I realised why it doesn't start sshd; sshd_enable="YES" wasn't in the rc.conf, I presume this is the new default behaviour? If one puts this back in, it generates the keypair, so I was probably just being stupid. But now I just took it out, and the machine hangs on: Starting sshd for about 2 minutes then carries on OK, I understand now. If I put in the ifconfig_rl0="DHCP" the machine pauses for about 1-2mins at the point just beyond Configuring syscons: keymap keyrate blanktime, which is also the same place as sshd. So now I suspect that this isn't a hang but DHCP doing its job? anonymousPseudonym
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?01ae01c3ec28$00f4b530$0601a8c0>