Anthony Metcalf wrote:
*That* depends on the exact specifics of what he is/isn't allowed to be showing....."They" may not even want the service to show as existing at that address for whatever reason.
Thanks for all your discussion... I'll try to clarify - the PPP over SSH approach does seem to offer the best compromise.
I've a development site which hosts https and http services for existing applications both remotely and locally. I'm developing an entirely new https service under Apache and want to be absolutely sure that I get no unexpected interactions between configurations for "live" services and the experimental in-development service - and I definitely don't want a random member of the public stumbling across the in-development site - which might expose unacceptable vulnerabilities as rough-cuts of code are trialled.
It is entirely acceptable for any host on my LAN to access the in-development service. I want to allow collaborators to access the in-development service remotely over a SSH tunnel from their LAN, too (where I'm also not concerned about abuse...)
The snag I'm finding at the moment I'm sure I'll overcome... and relates to access from my LAN. While I can sort-of see how to establish a new device with a new IP address on the remote LAN (with SSH and pppd) I'm not sure how to establish a second IP address for my single Ethernet adaptor to make this work on my LAN (though I'm sure it is do-able...)
I'm also curious to discover if there is a neat Gentooish way to establish my two instances of Apache. I'm broadly familiar to doing this a hackish way - but I'd prefer it plays nicely with any emerge updates.
