Date: Tue, 29 Apr 2003 23:05:29 +0300 From: Ruslan Ermilov <ru@freebsd.org> To: Max Khon <fjoe@iclub.nsu.ru> Cc: freebsd-net@freebsd.org Subject: Re: IPDIVERT Message-ID: <20030429200529.GA71528@sunbay.com> In-Reply-To: <20030430023640.A22257@iclub.nsu.ru> References: <20030430023640.A22257@iclub.nsu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--HcAYCG3uE/tztfnV Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 30, 2003 at 02:36:41AM +0700, Max Khon wrote: > hi, there! >=20 > I have a suggestion to build GENERIC and ipfw.ko with IPDIVERT by default > or change IPDIVERT to NOIPDIVERT and build boot kernels with NOIPDIVERT. > The main goal is to allow to use NAT with stock kernels and ipfw.ko. >=20 > Comments? >=20 Only if you succeed in making the ipdivert.ko module: IPDIVERT is not modularized currently, contrary to IPFIREWALL. What it means basically is that you will have to change lot of ``#ifdef IPDIVERT'' to ``if (IPDIVERT_LOADED)'', like with the IPFW_LOADED. I think this is worth doing. Cheers, --=20 Ruslan Ermilov Sysadmin and DBA, ru@sunbay.com Sunbay Software AG, ru@FreeBSD.org FreeBSD committer, +380.652.512.251 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --HcAYCG3uE/tztfnV Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+rtsJUkv4P6juNwoRAmC+AJ42iMrHhwJBqoz6YraMx2Bf2zKgcgCfTwnp RpChCLKjg3DTvlXeMcmXxuc= =NpE5 -----END PGP SIGNATURE----- --HcAYCG3uE/tztfnV--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030429200529.GA71528>