From owner-freebsd-questions  Mon Dec 15 10:35:31 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA23181
          for questions-outgoing; Mon, 15 Dec 1997 10:35:31 -0800 (PST)
          (envelope-from owner-freebsd-questions)
Received: from gdi.uoregon.edu (cisco-ts8-line16.uoregon.edu [128.223.150.80])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA23167
          for <freebsd-questions@FreeBSD.ORG>; Mon, 15 Dec 1997 10:35:27 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.7/8.8.8) with SMTP id KAA00375;
          Mon, 15 Dec 1997 10:35:06 -0800 (PST)
          (envelope-from dwhite@gdi.uoregon.edu)
Date: Mon, 15 Dec 1997 10:35:05 -0800 (PST)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: VPM Support Staff <staff@vpm.com>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: Can't get network to work
In-Reply-To: <01bd04e3$72aeaf60$0c983cd1@snews.vpm.com>
Message-ID: <Pine.BSF.3.96.971215103353.292I-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 9 Dec 1997, VPM Support Staff wrote:

> I've read the docs, FAQ, Handbook, searched  the mailling and newsgroups and
> have not found what I need to resolve this problem.  So here I am...
> 
> I just installed 2.2.5-Release from CD-ROM.  Everything installed fine.  But
> I'm having problems with the ipfw stuff.  Even though it's not enabled, ipfw
> is still 'deny all from any to any', which denies access to ping,
> traceroute, route etc. 

And telnet, ftp, and all other networking.  The default rule is to block
everything.

> Enabling 'allow all from any to any' as a rule fixes
> this problem, but now I can't ping the router even though netstat -rn shows
> it to be the default gateway.  I want to keep the firewall stuff enabled in
> the kernel and control it from ipfw, but it appears I'm missing something.

That rule should re-enable all network functions.  It depends on your
routing tables and such being correct of course.  

Does the network work if you boot with a non-ipfw'd kernel?

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major