From owner-freebsd-questions Mon Jan 11 11:13:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14018 for freebsd-questions-outgoing; Mon, 11 Jan 1999 11:13:44 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from java.dpcsys.com (java.dpcsys.com [206.16.184.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14013 for ; Mon, 11 Jan 1999 11:13:41 -0800 (PST) (envelope-from dan@dpcsys.com) Received: from localhost (dan@localhost) by java.dpcsys.com (8.9.1a/8.9.1) with SMTP id LAA12447; Mon, 11 Jan 1999 11:14:08 -0800 (PST) Date: Mon, 11 Jan 1999 11:14:08 -0800 (PST) From: Dan Busarow To: Praying Mantis cc: freebsd-questions@FreeBSD.ORG Subject: Re: routing problem? solution? In-Reply-To: <009401be3d95$96932640$276f14ce@divine> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 11 Jan 1999, Praying Mantis wrote: > Thanks for the reply. Yes I do have a default route, which points to the > isp's gateway. The gateway's ip below has been edited for e-mail, but it's > correct when I check it. And I am on an ethernet connection. > > $ netstat -rn > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif > Expire > default 123.456.789.3 UGSc 2 73 ed0 How about the full output from netstat -rn followed by a traceroute to a site you cannot connect to. Be consistent with your IP munging if you have an internal network to hide. Dan -- Dan Busarow 949 443 4172 Dana Point Communications, Inc. dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message