From owner-cvs-sys Thu Aug 22 00:49:57 1996 Return-Path: owner-cvs-sys Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id AAA25015 for cvs-sys-outgoing; Thu, 22 Aug 1996 00:49:57 -0700 (PDT) Received: from ra.dkuug.dk (ra.dkuug.dk [193.88.44.193]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id AAA25010; Thu, 22 Aug 1996 00:49:54 -0700 (PDT) Received: (from sos@localhost) by ra.dkuug.dk (8.6.12/8.6.12) id JAA06215; Thu, 22 Aug 1996 09:49:37 +0200 Message-Id: <199608220749.JAA06215@ra.dkuug.dk> Subject: Re: cvs commit: src/sys/netinet in.h ip_fw.h ip_input.c ip_output.c To: julian@whistle.com (Julian Elischer) Date: Thu, 22 Aug 1996 09:49:37 +0200 (MET DST) Cc: sos@FreeBSD.org, fenner@parc.xerox.com, sos@freefall.freebsd.org, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-sys@freefall.freebsd.org In-Reply-To: <321C0DAE.695678E2@whistle.com> from "Julian Elischer" at Aug 22, 96 00:35:11 am From: sos@FreeBSD.org Reply-to: sos@FreeBSD.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-cvs-sys@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In reply to Julian Elischer who wrote: > > sos@FreeBSD.org wrote: > > > > These hooks are for a kernel level impl. of NAT which to my best judgement > > belongs in the kernel. > and we think it belongs out of the kernel.. > this way we can both have our way.. Exactly.. > (of course we are also using the divert stuff for packet encryption etc. > as well.) Ahh, maybe I should do one of those too.. :) Actually what I would have liked, was one function ptr, that one could grap, and redirect, eventually chain to what was there before, plus maybe some kind of registering functionality. THat way firewall, NAT, divert whatever code could have been kept out of the ip files. But the gods intended it differently :(, or could we now get to some higher level agreement on how to do this, or should we just go our own ways (as usual).. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team So much code to hack -- so little time.