From owner-freebsd-questions@FreeBSD.ORG Thu May 26 20:28:21 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 4152016A41C for ; Thu, 26 May 2005 20:28:21 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.87]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1383A43D4C for ; Thu, 26 May 2005 20:28:20 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from mac.com (smtpin08-en2 [10.13.10.153]) by smtpout.mac.com (Xserve/8.12.11/smtpout05/MantshX 4.0) with ESMTP id j4QKSKON020254; Thu, 26 May 2005 13:28:20 -0700 (PDT) Received: from [192.168.1.6] (pool-68-161-53-96.ny325.east.verizon.net [68.161.53.96]) (authenticated bits=0) by mac.com (Xserve/smtpin08/MantshX 4.0) with ESMTP id j4QKSIhx020814; Thu, 26 May 2005 13:28:19 -0700 (PDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v730) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4C877552-5BA1-4774-88E4-B9351FA3BDAB@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Thu, 26 May 2005 16:28:19 -0400 To: Diogo Della X-Mailer: Apple Mail (2.730) Cc: freebsd-questions Subject: Re: freebsd cable disconnected problem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 May 2005 20:28:21 -0000 On May 26, 2005, at 4:07 PM, Diogo Della wrote: > It is very strange: if a put the initial ip address of the > interface and disconnect the cable "ssh localhost" does not work. > But, if a let this running and put the cable again, "ssh localhost" > works. > > What is going on? FreeBSD need to be connected and with the same ip > address I set at installation for the network deamon to work? Does localhost actually go to IP 127.0.0.1? Do you have a localhost route, check "netstat -nr"...? You can also take a look at what your daemons are binding to via: "netstat -anp TCP | grep LISTEN". Are they binding to *.port or otherwise? -- -Chuck