getting ssh to work
I recently tried to ssh into my desktop from another machine, and found that it doesn't work (it times out). I'm not sure what I need to do to make it work. I'm running 5-CURRENT from August 3 (back when 5 was still -CURRENT). I've confirmed that sshd is running (sshd_enable=YES is in rc.conf). I've checked /etc/ssh/sshd_config, and I haven't changed any of the defaults. My firewall should allow this sort of thing, and just to make absolutely sure, I told my firewall to (temporarily) let in _everything_ from the entire class B network the remote machine is on. netstat says that my machine is listening on port 22. And I can 'ssh localhost' from my desktop to itself (though it does say, socket: Protocol not supported before successfully asking for my password). The remote machine in question is running OpenSSH_3.6.1p2, and I'm running OpenSSH_3.8.1p1. I thought maybe for some odd reason ssh'ing out is blocked on the remote machine, but then I remembered that a friend tried to ssh in from his OS X laptop the other day, and that timed out the same way the current remote machine is. And I don't get a Permission denied sort of error on the remote machine, just a timeout. Any ideas? Thanks, -David -- +++ Divide By Cucumber Error. Please Reinstall Universe And Reboot. +++ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: getting ssh to work
On Friday 03 September 2004 01:43 am, Matthew Seaman wrote: One thing to check -- do you have the machine key for the remote machine cached somewhere No. Failing that, try running ssh and/or sshd in debug mode. On the client side you can run: % ssh -v -v -v [EMAIL PROTECTED] which will trace exactly what ssh is trying to do as you log in. Not much, it seems. Never makes contact: $ ssh -v -v -v [EMAIL PROTECTED] OpenSSH_3.6.1p2, SSH protocols 1.5/2.0, OpenSSL 0x0090701f debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Rhosts Authentication disabled, originating port will not be trusted. debug2: ssh_connect: needpriv 0 debug1: Connecting to [host] [host ip] port 22. debug1: connect to address [host] port 22: Connection timed out ssh: connect to host [host] port 22: Connection timed out The ssh_config has 'ForwardX11 yes' but is default apart from that. Unfortunately I don't have root access on the remote box. What's odd is that it never tries to contact me on port 22. I'm logging all packets from it to me, and I'm only seeing packets _from_ its port 22 to one of my unpriveledged ports (I should have added before that I'm first sshing to this computer, then trying to ssh back). I also just tried this from another remote computer (OpenSSH_3.7.1p2) on a completely separate network 2000 miles away, and got the exact same results. (For fun I tried sshing between these two remote computers, and that works fine.) I'd suggest that port 22 is being blocked upstream, but I just ssh'd to an old computer that sits right next to my desktop and is on the same network (it runs 5.2RC2). That computer can't ssh to mine either. -David -- +++ Divide By Cucumber Error. Please Reinstall Universe And Reboot. +++ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: getting ssh to work
On Friday 03 September 2004 02:56 am, David Syphers wrote: [a lot of stuff about how ssh doesn't work] Oh my, I feel silly. See, I have no experience with LANs, and foolishly though that I had a real IP, that computers off the LAN could use to find me... Didn't even realize I was _on_ a LAN, actually. So ssh works fine, I just need to figure out how to let other computers know where I am. *sigh* -David -- +++ Divide By Cucumber Error. Please Reinstall Universe And Reboot. +++ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: getting ssh to work
David Syphers wrote: On Friday 03 September 2004 02:56 am, David Syphers wrote: [a lot of stuff about how ssh doesn't work] Oh my, I feel silly. See, I have no experience with LANs, and foolishly though that I had a real IP, that computers off the LAN could use to find me... Didn't even realize I was _on_ a LAN, actually. So ssh works fine, I just need to figure out how to let other computers know where I am. *sigh* -David I had a similar problem with using SSH to connect to a FreeBSD box that I have. It turned out that the reason was that on the gateway that I use, I had IP forwarding disabled. My gateway is a box running Slackware Linux, and I am using Iptables to implement NAT (Network Address Translation). Your firewall is most likely something different, but I thought that you might find this info helpful in some way. Mark Vasquez ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
