From owner-freebsd-net  Tue Jul 18  9:22:26 2000
Delivered-To: freebsd-net@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by hub.freebsd.org (Postfix) with ESMTP id 4372437BEEA
	for <freebsd-net@FreeBSD.ORG>; Tue, 18 Jul 2000 09:22:23 -0700 (PDT)
	(envelope-from wollman@khavrinen.lcs.mit.edu)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id MAA08180;
	Tue, 18 Jul 2000 12:22:14 -0400 (EDT)
	(envelope-from wollman)
Date: Tue, 18 Jul 2000 12:22:14 -0400 (EDT)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200007181622.MAA08180@khavrinen.lcs.mit.edu>
To: "Cyril A. Vechera" <cyril@main.piter.net>
Cc: <freebsd-net@FreeBSD.ORG>
Subject: some kind of policy rounting with large table needed
In-Reply-To: <004d01bff0cf$402498e0$df6abec3@piter.net>
References: <004d01bff0cf$402498e0$df6abec3@piter.net>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

<<On Tue, 18 Jul 2000 19:45:49 +0400, "Cyril A. Vechera" <cyril@main.piter.net> said:

> Is there way to make source address based routing/port
> forwarding for large tables - about 50K subnets with different
> sizes.

Without question you need a Real Data Structure.  Probably in order to
perform acceptably you will need a kernel cache (similar to how the
multicast code, which also examines both addresses, does it) which you
can refill as needed from a user process.

-GAWollman





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message