From owner-freebsd-ipfw@FreeBSD.ORG  Wed Dec  3 20:40:21 2003
Return-Path: <owner-freebsd-ipfw@FreeBSD.ORG>
Delivered-To: freebsd-ipfw@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0D8E116A4D2
	for <freebsd-ipfw@freebsd.org>; Wed,  3 Dec 2003 20:40:16 -0800 (PST)
Received: from mail2.northnetworks.ca (dev.eagle.ca [209.167.58.10])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E35EE43FDF
	for <freebsd-ipfw@freebsd.org>; Wed,  3 Dec 2003 20:40:14 -0800 (PST)
	(envelope-from iaccounts@northnetworks.ca)
Received: from [127.0.0.1] (dev.eagle.ca [209.167.58.10])
	hB44cPCn049748;	Wed, 3 Dec 2003 23:38:26 -0500 (EST)
	(envelope-from iaccounts@northnetworks.ca)
From: Steve Bertrand <iaccounts@northnetworks.ca>
To: Chris <racerx@makeworld.com>
In-Reply-To: <200312032120.30792.racerx@makeworld.com>
References: <200312032055.58158.racerx@makeworld.com>
	 <1070507627.416.90.camel@ptp.northnetworks.ca>
	 <200312032120.30792.racerx@makeworld.com>
Content-Type: text/plain
Organization: Northumberland Network Services
Message-Id: <1070512792.416.109.camel@ptp.northnetworks.ca>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Date: Wed, 03 Dec 2003 23:39:53 -0500
Content-Transfer-Encoding: 7bit
cc: freebsd-ipfw@freebsd.org
Subject: Re: ipfw and ssh example
X-BeenThere: freebsd-ipfw@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: iaccounts@northnetworks.ca
List-Id: IPFW Technical Discussions <freebsd-ipfw.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
	<mailto:freebsd-ipfw-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ipfw>
List-Post: <mailto:freebsd-ipfw@freebsd.org>
List-Help: <mailto:freebsd-ipfw-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
	<mailto:freebsd-ipfw-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Dec 2003 04:40:21 -0000


> How about this:
> # ipfw add 10 allow tcp from 192.168.1.3-10 to me 22 in via rl0 keep-state
> 

Sure, but the question was 1 IP. With IPFW2 (after July 2002), you can
even do this:

safenets="{ 192.168.1.0/24 or 192.168.2.0/24 or 10.0.2.0/24 }"

$cmd 20 allow tcp from $safenets to me 22 in via rl0 keep-state
$cmd 21 deny tcp from any to me 22 

Which would allow all computers from all three subnets, saving you from
writing rules for each subnet.

Steve

> Allowing a range of IP's?
> 
> BTW - Thank you everyone.
-- 

Steve Bertrand
President/CTO,
Northumberland Network Services

t: 905.352.2688
w: www.northnetworks.ca