From owner-freebsd-net@FreeBSD.ORG  Wed Mar 31 00:59:15 2004
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 361CC16A4CE
	for <net@freebsd.org>; Wed, 31 Mar 2004 00:59:15 -0800 (PST)
Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0D93743D55
	for <net@freebsd.org>; Wed, 31 Mar 2004 00:59:15 -0800 (PST)
	(envelope-from rizzo@icir.org)
Received: from xorpc.icir.org (localhost [127.0.0.1])
	by xorpc.icir.org (8.12.9p1/8.12.8) with ESMTP id i2V8xEgd009626;
	Wed, 31 Mar 2004 00:59:14 -0800 (PST)
	(envelope-from rizzo@xorpc.icir.org)
Received: (from rizzo@localhost)
	by xorpc.icir.org (8.12.9p1/8.12.3/Submit) id i2V8xE71009625;
	Wed, 31 Mar 2004 00:59:14 -0800 (PST)
	(envelope-from rizzo)
Date: Wed, 31 Mar 2004 00:59:14 -0800
From: Luigi Rizzo <rizzo@icir.org>
To: net@freebsd.org
Message-ID: <20040331005914.A6934@xorpc.icir.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
Subject: do we support non contiguous netmasks ?
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 31 Mar 2004 08:59:15 -0000

Hi,
i was wondering if anyone knows what kind of support we have
in FreeBSD networking code, for non contiguous netmasks.
While it is trivial to support them for interface addresses,
managing them in the routing table is probably far from trivial
and I believe also mostly useless... and anyways, i have no
idea how our kernel code deals with them


cheers
luigi