Date: Fri, 03 Sep 2004 11:25:00 -0700 From: Mark Vasquez <mrvasquez@cox.net> To: David Syphers <dsyphers@u.washington.edu> Cc: freebsd-questions@freebsd.org Subject: Re: getting ssh to work Message-ID: <4138B6FC.3080006@cox.net> In-Reply-To: <200409030449.05336.dsyphers@u.washington.edu> References: <200409030123.35778.dsyphers@u.washington.edu> <20040903084307.GA63597@happy-idiot-talk.infracaninophile.co.uk> <200409030256.52955.dsyphers@u.washington.edu> <200409030449.05336.dsyphers@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4138B6FC.3080006>