public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sascha Hlusiak <saschahlusiak@arcor.de>
To: gentoo-user@lists.gentoo.org
Cc: Steve <gentoo_sjh@shic.co.uk>
Subject: Re: [gentoo-user] A networking question...
Date: Tue, 5 May 2009 23:51:03 +0200	[thread overview]
Message-ID: <200905052351.07728.saschahlusiak@arcor.de> (raw)
In-Reply-To: <4A00AF76.9010509@shic.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1262 bytes --]

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 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?
# /usr/sbin/pppd pty "ssh root@remoteserver pppd notty local 
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 
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 
proper routing and maybe NAT for that separate subnet, but it will be a tunnel 
into your home network.

- Sascha


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-05-05 21:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-05 20:32 [gentoo-user] A networking question Steve
2009-05-05 21:23 ` Sascha Hlusiak
2009-05-05 21:28   ` Steve
2009-05-05 21:51     ` Sascha Hlusiak [this message]
2009-05-05 22:07       ` Mick
2009-05-06  0:24     ` Mike Kazantsev
2009-05-06  7:54       ` Neil Bothwick
2009-05-06 10:09         ` Anthony Metcalf
2009-05-06 10:42           ` Neil Bothwick
2009-05-06 12:08             ` Anthony Metcalf
2009-05-07 18:38               ` Steve
2009-05-07 22:34                 ` Mick
2009-05-08 12:38                   ` Steve
2009-05-08 14:43                     ` Mick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200905052351.07728.saschahlusiak@arcor.de \
    --to=saschahlusiak@arcor.de \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=gentoo_sjh@shic.co.uk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox