port doubling (or...)?

[Cameron Laird]

In article <mailman.1011654031.25564.python-list at python.org>,
Cliff Wells  <logiplexsoftware at earthlink.net> wrote:
>On Mon, 21 Jan 2002 22:48:51 -0000
>maximilianscherr wrote:
>
>> > can you run the server on a diffrent port? you could filter 
>> incomming 
>> > requests on your server running on the original port and just pass 
>> along 
>> > the ones you not interested in to the original server.
>> > this could also be done with two machines, without changing ports.
>> > 
>> 
>> the uo client / server stuff works like this:
>> specify:
>> server: ip(s, yes ips,just checked), some port , mine: 5003
>> client: server ip, sertver port.
>> 
>> what can i do with this?,
>
>The logic is very simple, the implementation less so, but still not too
>difficult:
>
>- configure your uo server to listen on port A
>- configure your Python program to listen on port B
>- configure your uo client to transmit to port B
>- your Python server then accepts all packets on port B, and then forwards
>whatever ones it isn't interested in to port A
>- anything your Python program receives from port A it forwards to the
>client
>
>Basically, to the server, it looks like your Python program is the client,
>and to the client, it looks like the Python program is the server.
			.
			.
			.
sockspy <URL: http://mini.net/tcl/sockspy > is a
tool built for precisely this purpose.

It's not written in Python, though ...
-- 

Cameron Laird <Cameron at Lairds.com>
Business:  http://www.Phaseit.net
Personal:  http://starbase.neosoft.com/~claird/home.html