Date: Fri, 12 Jan 2001 06:41:10 -0600 (CST) From: Steve <vandena@ispchannel.com> To: David Schultz <vvortex1@home.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: ssh inop - UPDATE...problem solved. Message-ID: <Pine.BSF.4.21.0101120637400.299-100000@testbed.com> In-Reply-To: <000b01c07aff$1764b920$0100a8c0@mshome.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Just a quick update for everyone... For S&G's, I decided to install OpenSSH from the ports.. Viola! Everything works extremely well. I have no idea what was causing the problems with using ssh, but everything appears to be working normally at this time. David Schultz, thanks for your help. I'd be interested to hear if anyone else has had problems between Openssh and ssh. (I'd also like to know how much (if any) of a difference there is between the two.) On Wed, 10 Jan 2001, David Schultz wrote: > > Running FBSD 4.2-RELEASE with ipfw and natd. Installed ssh without any > > problems. Tried to access my FBSD machine from any system on either side > > of the firewall and was unable to connect...timeout error. I specified my > > IP address on each side of the firewall in /etc/ssh/sshd_config. Still > > unable to log in via ssh (timeout error). Looked in /var/log/messages and > > found the following error: > > > > sshd[260]: error: Bind to port 22 on :: failed: Address already in use. > > sshd[260]: error: Bind to port 22 on 0.0.0.0 failed: Address already in > > use. > > sshd[260]: fatal: Cannot bind all addresses. > > It somehow seems wrong that sshd would be trying to listen on 0.0.0.0. I > suspect that (a) you specified an invalid ListenAddress in sshd_config or > (b) you uncommented the "#ListenAddress 0.0.0.0" and "#ListenAddress ::" > examples in the file without actually changing the addresses. (The latter is > just a null IPv6 address.) It's usually best to leave it on the default > setting (i.e. comment out ListenAddress), which is to listen on all local > interfaces. OpenSSH has created a very secure daemon, and I doubt there is > any justifiable security concern to warrant blocking logins from certain > interfaces. > > If you've still got trouble, see if "ps -ax |grep sshd" turns up anything. > If so, try to connect to the box locally. You could also try disabling the > firewall temporarily, but I doubt that it is to blame. Just make sure you > actually are loading a ruleset--- unless you changed it in the kernel > configuration, the default is to deny everything. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0101120637400.299-100000>