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 ) id 1M1SXN-0007sk-Ot for garchives@archives.gentoo.org; Tue, 05 May 2009 21:50:54 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CC030E0407; Tue, 5 May 2009 21:50:52 +0000 (UTC) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by pigeon.gentoo.org (Postfix) with ESMTP id 76691E0407 for ; Tue, 5 May 2009 21:50:52 +0000 (UTC) Received: from sascha.localnet ([78.52.63.163]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0MKv5w-1M1SWz1mbq-0000sK; Tue, 05 May 2009 23:50:29 +0200 From: Sascha Hlusiak To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] A networking question... Date: Tue, 5 May 2009 23:51:03 +0200 User-Agent: KMail/1.11.2 (Linux/2.6.29-gentoo-r2; KDE/4.2.2; i686; ; ) Cc: Steve References: <4A00A266.9070102@shic.co.uk> <200905052324.07892.saschahlusiak@arcor.de> <4A00AF76.9010509@shic.co.uk> In-Reply-To: <4A00AF76.9010509@shic.co.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1745408.4SbCydpnXr"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200905052351.07728.saschahlusiak@arcor.de> X-Provags-ID: V01U2FsdGVkX18mmfws/J4HmdE2y1hOV2OLmqRvBKdVm2kn+KL 6g//kEIuuSk2+L0tr/3JXxm0P+Q/n0s9MnOeaQkc4ozC7xypZu HxHrWuqKn2qVLpVq2Ua7yQVpwAAPa9t X-Archives-Salt: d21c0e1d-1dcc-4ca8-8ecf-0872ecfb2d1d X-Archives-Hash: b80ac878dc1819be325ee444f0b41238 --nextPart1745408.4SbCydpnXr Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Am Dienstag 05 Mai 2009 23:28:22 schrieb Steve: > 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 simp= le > > > > 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? # /usr/sbin/pppd pty "ssh root@remoteserver pppd notty local=20 10.0.0.1:10.0.0.2" noipdefault nodefaultroute noauth updetach You can also just create a file in /etc/ppp/peers/ with the following lines= =20 and then call 'pon': pty "ssh root@remoteserver pppd notty local 10.0.0.1:10.0.0.2" noipdefault nodefaultroute noauth updetach You'll get the IP 10.0.0.2 and on the server 10.0.0.1. You need to setup=20 proper routing and maybe NAT for that separate subnet, but it will be a tun= nel=20 into your home network. =2D Sascha --nextPart1745408.4SbCydpnXr Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEABECAAYFAkoAtMsACgkQOyDtNneHFrMJBgCgiZI8LyGweveP1MF08YLEmcWU ag4AmwRwoV/uqApP54SS9cobRiXBKphT =mM2D -----END PGP SIGNATURE----- --nextPart1745408.4SbCydpnXr--