[prev in list] [next in list] [prev in thread] [next in thread] 

List:       inet-access
Subject:    RE: IP redirect question
From:       "Andrew Staples" <andrews () ltinet ! net>
Date:       2004-03-27 0:20:33
Message-ID: B0005237814 () lti-main ! ltinet ! net
[Download RAW message or body]

>> My customer wants to move his server to another network in another 
>> city, but he needs a way to reroute packets destined to the original 
>> public ip address to the new public ip address.  Tunnels are not an
option.
>
>If you're using Linux, the simplest solution is probably rinetd or
something work-alike.  It just listens on a port on >an IP, and forwards
connections to another port on another IP.  As long as your rinetd server
can get to the new IP, >you're set.  The only real problem is lack of
accountability, as all connections will come from your server, not the
>actual clients.  Oh well, he should have used a FQDN in the first place
>*8-)

This looks good...I'll give it a shot.

Andrew

_______________________________________________
"Eat sushi frequently". - Avi
inet@inet-access.net is the human contact address.
list@inet-access.net is the list posting address.
See below URL for subscribe/unsubscribe and list options:
http://inet-access.net/mailman/listinfo/list
[prev in list] [next in list] [prev in thread] [next in thread]