From owner-freebsd-security  Thu Jan 16 03:03:53 1997
Return-Path: <owner-security>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id DAA16207
          for security-outgoing; Thu, 16 Jan 1997 03:03:53 -0800 (PST)
Received: from shadows.aeon.net (bsdsec@shadows.aeon.net [194.100.41.1])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA16199
          for <security@freebsd.org>; Thu, 16 Jan 1997 03:03:42 -0800 (PST)
Received: (from bsdsec@localhost)
          by shadows.aeon.net (8.8.4/8.8.3) id NAA22995;
          Thu, 16 Jan 1997 13:02:34 +0200 (EET)
From: mika ruohotie <bsdsec@shadows.aeon.net>
Message-Id: <199701161102.NAA22995@shadows.aeon.net>
Subject: Re: Firewall and FreeBSD CIDR
To: black@squid.gage.com (Ben Black)
Date: Thu, 16 Jan 1997 13:02:33 +0200 (EET)
Cc: security@freebsd.org
In-Reply-To: <9701151714.AA29561@squid.gage.com> from Ben Black at "Jan 15, 97 11:14:16 am"
X-Mailer: ELM [version 2.4ME+ PL22 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-security@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> CIDR has nothing to do with this.  the term for what you are doing is  
> subnetting.  CIDR is the aggregation of large blocks of class C networks to  
> reduce routing table size.

actually, CIDR number can point to a subnet of C-class too... and it can
be non C-class also... as rfc1878 says...

/25 - /31 (yes, yes, /32 too) are subnets, /1 - /8 As, /9 - /16 Bs, and
between those (/17 - /24) full Cs

but we knew it... =)

> b3n


mickey