From owner-freebsd-questions Thu Jun 7 13: 3:50 2001 Delivered-To: freebsd-questions@freebsd.org Received: from cody.jharris.com (cody.jharris.com [205.238.128.83]) by hub.freebsd.org (Postfix) with ESMTP id D0BDA37B403 for ; Thu, 7 Jun 2001 13:03:46 -0700 (PDT) (envelope-from nick@rogness.net) Received: from localhost (nick@localhost) by cody.jharris.com (8.11.1/8.9.3) with ESMTP id f57LMcd13582; Thu, 7 Jun 2001 16:22:38 -0500 (CDT) (envelope-from nick@rogness.net) Date: Thu, 7 Jun 2001 16:22:38 -0500 (CDT) From: Nick Rogness X-Sender: nick@cody.jharris.com To: Ryan Thompson Cc: Josh Thomas , freebsd-questions@FreeBSD.ORG Subject: Re: IPFW rules and outward connections In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 7 Jun 2001, Ryan Thompson wrote: > Josh Thomas wrote to freebsd-questions@FreeBSD.ORG: > > > I am looking to set up a firewall to be closed to all incoming > > connections except for 20-22 (for ftp and ssh), and to allow all > > outward connections. However, I'm having trouble specifically keeping > > the dynamically assigned ports above 1024 for normal usage open. > ie, > http from other machines, ftp from other machines. > [snip] > > # OR, only allow connections to remote ports 1024-9999 > ipfw 1000 allow ip from ${network} to any 1024-9999 ^^ You need to be protocol specific, eg tcp,udp in order to specify ports or port ranges...unless that has changed. Nick Rogness - Keep on Routing in a Free World... "FreeBSD: The Power to Serve!" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message