Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 6 Apr 2002 19:27:15 -0700 (MST)
From:      Alex Rousskov <rousskov@measurement-factory.com>
To:        Nick Rogness <nick@rogness.net>
Cc:        freebsd-net@FreeBSD.ORG
Subject:   Re: Forcing packets to the wire
Message-ID:  <Pine.BSF.4.10.10204061919440.91712-100000@measurement-factory.com>
In-Reply-To: <Pine.BSF.4.21.0204061322160.12246-100000@cody.jharris.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.10204061919440.91712-100000>