From owner-freebsd-net Wed Jul 21 1:55:50 1999 Delivered-To: freebsd-net@freebsd.org Received: from gw0.boostworks.com (gw0.boostworks.com [194.167.81.213]) by hub.freebsd.org (Postfix) with ESMTP id D8B7F14DBD for ; Wed, 21 Jul 1999 01:55:36 -0700 (PDT) (envelope-from root@synx.com) Received: from synx.com (rn.synx.com [192.1.1.241]) by rt2.synx.com (8.9.1/8.9.1) with ESMTP id SAA83507; Tue, 20 Jul 1999 18:35:24 +0200 (CEST) Message-Id: <199907201635.SAA83507@rt2.synx.com> Date: Tue, 20 Jul 1999 18:35:18 +0200 (CEST) From: Remy Nonnenmacher Reply-To: remy@synx.com Subject: RE: Tcp shadowing for use in HTTP proxy To: Milan.Kopacka@st.ms.mff.cuni.cz Cc: mkop5230@ss1000.ms.mff.cuni.cz, palo.adamec@tecton.sk, freebsd-net@FreeBSD.ORG, tpc-l@freebsd.cz In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 20 Jul, Milan Kopacka wrote: > On Tue, 20 Jul 1999, Pavol Adamec wrote: > >> It would be interesting to know the real purpose that led to the idea. >> Why is it so important for the server to see client's real IP or why >> is it so important for the proxy to have the server see client's real >> IP. > > Such feature is mainly academic - to try, if fully transparent proxying of > HTTP can be achieved, what must be done and where are the limitations. > Transparent means invisible - but how close can we get..? > Luigi's BRIDGE code + ipfw + forward + 1 line change in kernel (to allow an application for binding a 'foreign' local address) allows for relaying, fully invisible, any TCP/UDP connections. Lot of application area there. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message