From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
	by finch.gentoo.org with esmtp (Exim 4.60)
	(envelope-from <gentoo-user+bounces-94984-garchives=archives.gentoo.org@lists.gentoo.org>)
	id 1M1SBf-0003up-NS
	for garchives@archives.gentoo.org; Tue, 05 May 2009 21:28:27 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 9EC72E03AF;
	Tue,  5 May 2009 21:28:26 +0000 (UTC)
Received: from smtp.hotchilli.net (mta3.th.hotchilli.net [62.89.140.53])
	by pigeon.gentoo.org (Postfix) with ESMTP id 7FD0FE03AF
	for <gentoo-user@lists.gentoo.org>; Tue,  5 May 2009 21:28:26 +0000 (UTC)
Received: from static-87-243-200-80.adsl.hotchilli.net ([87.243.200.80] helo=[10.0.1.253])
	by smtp.hotchilli.net with esmtp (Exim 4.63)
	(envelope-from <gentoo_sjh@shic.co.uk>)
	id 1M1SBe-0006BZ-4s
	for gentoo-user@lists.gentoo.org; Tue, 05 May 2009 22:28:26 +0100
Message-ID: <4A00AF76.9010509@shic.co.uk>
Date: Tue, 05 May 2009 22:28:22 +0100
From: Steve <gentoo_sjh@shic.co.uk>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] A networking question...
References: <4A00A266.9070102@shic.co.uk> <200905052324.07892.saschahlusiak@arcor.de>
In-Reply-To: <200905052324.07892.saschahlusiak@arcor.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Archives-Salt: 48107ddc-ea83-44ce-9a6e-e4e4963a914f
X-Archives-Hash: 9d23ef343c5676c431a541bd060145ae

Sascha Hlusiak wrote:
> The easiest thing would probably be to just use ssh port forwarding because 
> you already have all the pieces running anyway. Wouldn't a simple
>
>   ssh -L 12345:secondapache:https user@remotessh
>
> and the browsing to https://localhost:12345 do the trick? Or you could use a 
> pppd over ssh vpn, yes, but that is a bit more complex.
>
> - Sascha
>
>   
I really want to avoid having to access a non-standard port from the 
URLs - I want to use the final URLs exactly as they will be once the 
in-development website is eventually deployed.

Can you recommend a 'how-to' for the pppd over ssh approach?