From owner-freebsd-net Sat Apr 6 18:27:30 2002 Delivered-To: freebsd-net@freebsd.org Received: from measurement-factory.com (measurement-factory.com [206.168.0.5]) by hub.freebsd.org (Postfix) with ESMTP id 605FA37B404 for ; Sat, 6 Apr 2002 18:27:26 -0800 (PST) Received: (from rousskov@localhost) by measurement-factory.com (8.11.6/8.11.6) id g372RFP09208; Sat, 6 Apr 2002 19:27:15 -0700 (MST) (envelope-from rousskov) Date: Sat, 6 Apr 2002 19:27:15 -0700 (MST) From: Alex Rousskov To: Nick Rogness Cc: freebsd-net@FreeBSD.ORG Subject: Re: Forcing packets to the wire In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 6 Apr 2002, Nick Rogness wrote: > I had a brief thought of using an upstream device that could route > the appropriate nat'd addresses to each interface. This is not an option, unfortunately. The required functionality has to be implemented inside one PC (appliance). No external devices. I want to ship that PC to a customer with one NIC labeled "client side", the other NIC labeled "server side". The customer should be able to plug in the wires and test their "explicit" proxies (works now because client packets are addressed to the proxy), their transparent (aka TCP hijacking) proxies (does not work because client packets are addressed to servers and do not leave the appliance), and their networking gear (does not work for the same reason). Thank you, Alex. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message