From owner-freebsd-current Sat Jan 8 0:44:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 948B614D6D for ; Sat, 8 Jan 2000 00:44:28 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id JAA13117; Sat, 8 Jan 2000 09:42:39 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: "Rodney W. Grimes" Cc: luigi@info.iet.unipi.it (Luigi Rizzo), patrick@mindstep.com (Patrick Bihan-Faou), logix@foobar.franken.de (Harold Gutch), freebsd-current@FreeBSD.ORG, nate@mt.sri.com (Nate Williams) Subject: Re: ipfw optimizations In-reply-to: Your message of "Sat, 08 Jan 2000 00:34:31 PST." <200001080834.AAA14383@gndrsh.dnsmgr.net> Date: Sat, 08 Jan 2000 09:42:39 +0100 Message-ID: <13115.947320959@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001080834.AAA14383@gndrsh.dnsmgr.net>, "Rodney W. Grimes" writes : >handle packets as they traverse ip_forward? I know Poul's or someone >elses drawing of the H style firewall could be implemented if we had >a way to apply rules as they traverse the ip_forward code and an easy >way to expand your scheme to include that would be to add something >like ``via fwd, in via fwd, out via fwd''. Note that I _think_ but >am not certain that NAT tapping/injection occurs in ip_forward so this >could be of benefit to those doing NAT. I think the general syntax would be if you could say "for one of my own IP#" that would be very powerful: add allow tcp from any to me 22 add deny tcp from any to not me 22 -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message