From owner-freebsd-questions@FreeBSD.ORG Sun Nov 9 00:02:02 2003 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 042D516A4CE for ; Sun, 9 Nov 2003 00:02:02 -0800 (PST) Received: from p1028-ipbffx02marunouchi.tokyo.ocn.ne.jp (p1028-ipbffx02marunouchi.tokyo.ocn.ne.jp [220.111.132.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 170F243FB1 for ; Sun, 9 Nov 2003 00:02:00 -0800 (PST) (envelope-from lukek@meibin.net) Received: (qmail 85838 invoked by uid 89); 9 Nov 2003 08:01:59 -0000 Received: from unknown (HELO ?127.0.0.1?) (192.168.10.35) by 192.168.20.5 with SMTP; 9 Nov 2003 08:01:59 -0000 Date: Sun, 09 Nov 2003 17:00:54 +0900 From: Luke Kearney To: Marty Landman In-Reply-To: <6.0.0.22.0.20031109013452.01b06c50@pop.face2interface.com> References: <6.0.0.22.0.20031109013452.01b06c50@pop.face2interface.com> Message-Id: <20031109170045.8858.LUKEK@meibin.net> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.07.01 cc: freebsd-questions@freebsd.org Subject: Re: No route to host 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: Sun, 09 Nov 2003 08:02:02 -0000 On Sun, 09 Nov 2003 01:57:35 -0500 Marty Landman granted us these pearls of wisdom: > I'm new to FreeBSD and have the 4.8 mini-iso installed. Have tried to > install the nic and can ping my ip and localhost ok, but when I try to ping > other boxes on my LAN get > > ping: sendto: No route to host > > An ifconfig shows ep0 UP and RUNNING; ipfw list replies Protocol not available. > > FWIW I also tried pinging the FreeBSD box from two other (Windoz) boxes on > the LAN. > Hmm take a quick peek at your routing table - chances are you have not told the machine much about your network # netstat -rn If the correct information is not there then something like # route add default -interface ep0 ( or better yet if you have a router ) # route add default 192.168.1.1 <-- where this is the address of the router If you can see the correct routing information the next likely culprit is the firewall. Try turning off the firewall for starters. HTH Lukek