From owner-freebsd-questions@FreeBSD.ORG Wed May 5 20:44:28 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A33AB16A4CE for ; Wed, 5 May 2004 20:44:28 -0700 (PDT) Received: from pursued-with.net (adsl-66-125-9-242.dsl.sndg02.pacbell.net [66.125.9.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4082043D41 for ; Wed, 5 May 2004 20:44:28 -0700 (PDT) (envelope-from freebsd@pursued-with.net) Received: from [192.168.168.101] (fffinch [192.168.168.101]) by pursued-with.net (Postfix) with ESMTP id 336AD120C82; Wed, 5 May 2004 20:44:35 -0700 (PDT) In-Reply-To: <200405061224.06064.pwd8jmr22w@me.point.ne.jp> References: <200405061032.19742.pwd8jmr22w@me.point.ne.jp> <4099A21D.2030001@users.sourceforge.net> <200405061224.06064.pwd8jmr22w@me.point.ne.jp> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Kevin Stevens Date: Wed, 5 May 2004 20:44:28 -0700 To: pwd8jmr22w@me.point.ne.jp X-Mailer: Apple Mail (2.613) cc: freebsd-questions@freebsd.org Subject: Re: Need Advice in SSH X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 May 2004 03:44:28 -0000 On May 5, 2004, at 20:24, Bull TORS wrote: > My laptop in the office (laptop1.mydomain.org) has a static internal > network > address 192.168.1.35 from my company's (companydomain.org) LAN Server. > My laptop in my home has 192.168.1.x (I am not that sure if it changes > a lot > but I think not) as a DHCP client from my ISP (ispdomain.ne.jp). > So I think both gets internal network addresses from their respective > servers, > one as a static client and the other as a dynamic client from different > domains. Does this mean I can not use ssh from either both PC's? No, but you need more information. Some device on each end is translating those non-routable private addresses to public ones usable on the Internet. Almost certainly, at least one and probably both are blocking inbound SSH connections by default. It is more likely that you can initiate outbound connections from your company's network, and can configure your home network to permit inbound connections. It is much less likely that you will be able to have your company network configured to permit inbound connections initiated from your home computer. In either case, you need more detailed information on the configurations. Talk to the IT staff at your company and explain what you're trying to do and ask if they permit outbound SSH sessions. At your home, in my experience it's very uncommon for an ISP to provision either DHCP or private addresses directly - it's more common for there to be a local device in your home that is accomplishing that. But talk to your ISP, it could be different in Japan. Properly speaking, this has little or nothing to do with FreeBSD, BTW, it is general firewall, NAT and SSH information. KeS