From owner-freebsd-questions@FreeBSD.ORG Sun Nov 9 06:54:58 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 9B39016A4CE for ; Sun, 9 Nov 2003 06:54:58 -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 037A543FDF for ; Sun, 9 Nov 2003 06:54:56 -0800 (PST) (envelope-from lukek@meibin.net) Received: (qmail 87473 invoked by uid 89); 9 Nov 2003 14:54:55 -0000 Received: from unknown (HELO ?127.0.0.1?) (192.168.10.35) by 192.168.20.5 with SMTP; 9 Nov 2003 14:54:55 -0000 Date: Sun, 09 Nov 2003 23:53:45 +0900 From: Luke Kearney To: Marty Landman In-Reply-To: <6.0.0.22.0.20031109091603.04503b68@pop.face2interface.com> References: <20031109170045.8858.LUKEK@meibin.net> <6.0.0.22.0.20031109091603.04503b68@pop.face2interface.com> Message-Id: <20031109235155.8861.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 14:54:58 -0000 On Sun, 09 Nov 2003 09:49:54 -0500 Marty Landman granted us these pearls of wisdom: > At 03:00 AM 11/9/2003, you wrote: > > >If the correct information is not there then something like > > > ># route add default -interface ep0 > > Ok I did this (there's no router). Now I can still ping my own ip and > localhost as before and when I try pinging another node on the lan it seems > to hang, i.e. > > PING 192.168.0.1 (192.168.0.1): 56 data bytes > > until ^c out of it. > > Ok so I let it sit like that for a couple of minutes and after interrupting > it got back > > 600 packets transmitted, 0 packets received, 100% packet loss > > >If you can see the correct routing information the next likely culprit > >is the firewall. Try turning off the firewall for starters. > > #ipfw disable firewall > #ping 192.168.0.1 > ^C > 7 packets transmitted, 0 packets received, 100% packet loss > # > > Hmm, any other ideas? > > Marty Landman Face 2 Interface Inc 845-679-9387 > Sign On Required: Web membership software for your site > Make a Website: http://face2interface.com/Home/Demo.shtml please make a rough ascii sketch of your network and post the output to the following :- netstat -rn ifconfig -a in your rc.conf firewall_enable="yes" HTH LukeK