From owner-freebsd-questions Mon May 20 16:05:33 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA26966 for questions-outgoing; Mon, 20 May 1996 16:05:33 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id QAA26961 for ; Mon, 20 May 1996 16:05:29 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA28811; Mon, 20 May 1996 15:56:39 -0700 From: Terry Lambert Message-Id: <199605202256.PAA28811@phaeton.artisoft.com> Subject: Re: ip masquerading To: archie@whistle.com (Archie Cobbs) Date: Mon, 20 May 1996 15:56:39 -0700 (MST) Cc: terry@lambert.org, archie@whistle.com, dwhite@riley-net170-164.uoregon.edu, clintm@ICSI.Net, FreeBSD-Questions@FreeBSD.org, bmah@cs.berkeley.edu In-Reply-To: <199605202242.PAA01046@bubba.whistle.com> from "Archie Cobbs" at May 20, 96 03:42:46 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > Actually, the burden is on someone who wants a proxy facility to > > write one, and if they choose to go the long way around and go > > with "masquerading", to get it integrated. > > That's a different burden from the one I was talking about, but OK :-) > > I'll say it again, I'm not interested in getting this stuff into > the kernel any more than you are. I'm just saying that it is something > that some people out there would really like to do, and if it could > be facilitated somehow, those people would be very grateful. How about we provide them a working tunnel device, source code for SLiRP, which can be modified to be the type 1 socks proxy daemon, and source code for user mode PPP, which can be modified to be the type 2 socks proxy daemon? 8-) 8-) 8-). Seems to me that it would be less than 60 hours of work to do the whole thing -- ~2 full weekends. Doing the kernel code for a Linux-style implementation in such a way as to not screw anything up seems to be on the order of 120+ hours (both figures include testing and documentation and control software). Personally, I'm not going to blow all my uncommitted time for a month to code up something I'll never use, even if there are good, solid religious reasons for doing so. Two months is totally out of the question, especially since the result would be inferior. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.