Using an IP from remote server on home computer

OK, what I want to do is use an IP address I have on a remote server on a
computer based at home.

I want the IP to be fully connectable from the outside world, via the
server.

This is what I have running at the moment:

Server - Linux
Main IP:193.201.200.212
IP I want at home: 193.201.200.242

Home - Windows
Main IP: 82.43.99.151

How would I go about getting 193.201.200.242 to work on a home computer?

I've had a look at a few VPN sites, but not sure exactly how I want to set
it up, anyone got any ideas?

Cheers,
Peter Verrill

On Thu, 06 May 2004, Peter Verrill <peter_verill@_remove_blueyonder.co.uk>
wrote:
> OK, what I want to do is use an IP address I have on a remote server on a
> computer based at home.
>
> I want the IP to be fully connectable from the outside world, via the
> server.
>
> This is what I have running at the moment:
>
> Server - Linux
> Main IP:193.201.200.212
> IP I want at home: 193.201.200.242
>
> Home - Windows
> Main IP: 82.43.99.151
>
> How would I go about getting 193.201.200.242 to work on a home computer?
>
> I've had a look at a few VPN sites, but not sure exactly how I want to set
> it up, anyone got any ideas?

You do not say what Win version, but XP has native ipsec and I have used
SSHSentinal trial version (maybe no longer available) to VPN a Win98se box
on dialup to freeswan (ipsec) on Linux connected via adsl. But a hole
needs to be opened in the Linux firewall (by root) for the ipsec
connection (which can be done with from freeswan related scripts).

It may be easier to use ssh with port forwarding to just tunnel specific
ports (does not require root access on remote server). But I have not
tried ssh port forwarding with a Windows ssh client like Putty. Instead I
connected ssh Linux2Linux with gatewayed ports so I could connect a Win
terminal client on my end to HP3000 (computer) on distant LAN.

--
David Efflandt - All spam ignored http://www.de-srv.com/

On Thu, 06 May 2004 17:45:01 +0000, David Efflandt wrote:
> You do not say what Win version, but XP has native ipsec and I have used
> SSHSentinal trial version (maybe no longer available) to VPN a Win98se box
> on dialup to freeswan (ipsec) on Linux connected via adsl. But a hole
> needs to be opened in the Linux firewall (by root) for the ipsec
> connection (which can be done with from freeswan related scripts).

The windows computer is Windows 2000

> It may be easier to use ssh with port forwarding to just tunnel specific
> ports (does not require root access on remote server). But I have not
> tried ssh port forwarding with a Windows ssh client like Putty. Instead I
> connected ssh Linux2Linux with gatewayed ports so I could connect a Win
> terminal client on my end to HP3000 (computer) on distant LAN.

I'll try to explain what I want in a little more detail. The main reason
for this is that I wish to host 2-3 IRCXPRO servers, a windows IRC server.
But, all my colocated servers are linux based, so I host them at home.
Unfortunatly my home ISP only assigns one IP address to me, so I wish to
some how tunnel the IPs from my colocated servers to home. I'm not sure
about VPNs and the like so am not sure what software I need to use.

The reason I dont want to use port forwarding is that all connections will
appear to originate from the server forwarding the connection, this isn't
useful for operating IRC.

I've taken a quick look at http://openvpn.sourceforge.net/ it supports
both Linux and Windows, but im not sure if it will allow me to do what I
wish.

Peter Verrill

On Thu, 06 May 2004 17:45:01 +0000, David Efflandt wrote:

> On Thu, 06 May 2004, Peter Verrill <peter_verill@_remove_blueyonder.co.uk>
> wrote:
>> OK, what I want to do is use an IP address I have on a remote server on a
>> computer based at home.

>>
>> I want the IP to be fully connectable from the outside world, via the
>> server.
??? what do you mean fully connectable???
>>
>> This is what I have running at the moment:
>>
>> Server - Linux
>> Main IP:193.201.200.212
>> IP I want at home: 193.201.200.242
>>
are you saying that packets bound for IP address 193.201.200.242 should
wind up at your house? this is not possible in a literal sense. Unless
you can get access to your CoLo's routers. (evil grin)
>> Home - Windows
>> Main IP: 82.43.99.151
>>
>> How would I go about getting 193.201.200.242 to work on a home
computer?
you would have to reshape your CoLo's network

>>
>> I've had a look at a few VPN sites, but not sure exactly how I want to set
>> it up, anyone got any ideas?
>
> You do not say what Win version, but XP has native ipsec and I have used
> SSHSentinal trial version (maybe no longer available) to VPN a Win98se box
> on dialup to freeswan (ipsec) on Linux connected via adsl. But a hole
> needs to be opened in the Linux firewall (by root) for the ipsec
> connection (which can be done with from freeswan related scripts).

>
> It may be easier to use ssh with port forwarding to just tunnel specific
> ports (does not require root access on remote server). But I have not
> tried ssh port forwarding with a Windows ssh client like Putty. Instead I
> connected ssh Linux2Linux with gatewayed ports so I could connect a Win
> terminal client on my end to HP3000 (computer) on distant LAN.

On Thu, 06 May 2004, Peter Verrill <peter_verill@_remove_blueyonder.co.uk>
wrote:
> On Thu, 06 May 2004 17:45:01 +0000, David Efflandt wrote:
>> You do not say what Win version, but XP has native ipsec and I have used
>> SSHSentinal trial version (maybe no longer available) to VPN a Win98se box
>> on dialup to freeswan (ipsec) on Linux connected via adsl. But a hole
>> needs to be opened in the Linux firewall (by root) for the ipsec
>> connection (which can be done with from freeswan related scripts).
>
> The windows computer is Windows 2000
>
>> It may be easier to use ssh with port forwarding to just tunnel specific
>> ports (does not require root access on remote server). But I have not
>> tried ssh port forwarding with a Windows ssh client like Putty. Instead I
>> connected ssh Linux2Linux with gatewayed ports so I could connect a Win
>> terminal client on my end to HP3000 (computer) on distant LAN.
>
> I'll try to explain what I want in a little more detail. The main reason
> for this is that I wish to host 2-3 IRCXPRO servers, a windows IRC server.
> But, all my colocated servers are linux based, so I host them at home.
> Unfortunatly my home ISP only assigns one IP address to me, so I wish to
> some how tunnel the IPs from my colocated servers to home. I'm not sure
> about VPNs and the like so am not sure what software I need to use.
>
> The reason I dont want to use port forwarding is that all connections will
> appear to originate from the server forwarding the connection, this isn't
> useful for operating IRC.

I could see possibly doing it with a VPN tunnel between the colo and your
home LAN. Then use 1to1 NAT on the colocated server to map each public IP
to each home LAN IP. To the outside world, the traffic from your home
boxes would appear to come from your colo public IPs. However, those home
boxes may need to route all their internet access through the VPN, unless
you do more advance routing to determine which public traffic should go
through the VPN and which could go directly out your internet connection.

To have colo public IP's actually on your home machines I believe would
require bridging over VPN, which is beyond my knowledge.

> I've taken a quick look at http://openvpn.sourceforge.net/ it supports
> both Linux and Windows, but im not sure if it will allow me to do what I
> wish.
>
> Peter Verrill


--
David Efflandt - All spam ignored http://www.de-srv.com/
http://www.autox.chicago.il.us/ http://www.berniesfloral.net/