bryantrv wrote:
Maybe I'm missing something, but I thought a private ip was not routable to the outside world, and any ip that can be accessed from the interwebs is, by definition, publicly accessible.
Thus the concept of a VPN - in this case the "private" device is not, in fact, accessible from outside the VPN.
In other words, the two endpoints of the VPN are directly connected by a virtual "wire", just as if they were directly connected as on a home or office network. Thus, they are then free to agree to use any addressing scheme, including private address space. While the VPN endpoints themselves will have to have a public address so the tunnel can make it across the public network, the traffic that traverses the VPN and the devices accessed on either side do not.
To the OP there's really no restriction on your address choices. And nothing to request, just configure whatever you like, on the devices that need to communicate.
If you are using private interfaces on your Linode, I believe they all come out of the 192.168/17 space, so you could either just select a non-overlapping portion of that space, or shift to 172.16/12 or 10/8 instead. (Technically you can really use any address that won't need to be otherwise accessible to the devices involved)
I'm assuming you've selected PPTP due to known support on whatever equipment you are using, but if you aren't wedded to it, you might also take a peek at OpenVPN.
To the question of periodic scp/rsync or whatever, for me, there comes a point, depending on the activities and protocols involved, where it's just so much easier to establish a proper network between two devices and not try to shoe-horn all activities through a single ssh-based pipe. Not that the latter isn't useful in all sorts of other cases.
-- David