public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] Router for ssh tunnel/SOCKS proxy
Date: Fri, 5 Jan 2007 22:32:45 -0600	[thread overview]
Message-ID: <200701052232.45814.bss03@volumehost.net> (raw)
In-Reply-To: <200701052244.22150.shrdlu@unlimitedmail.org>

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

On Friday 05 January 2007 15:44, Etaoin Shrdlu <shrdlu@unlimitedmail.org> 
wrote about 'Re: [gentoo-user] [OT] Router for ssh tunnel/SOCKS proxy':
> On Friday 5 January 2007 21:25, Mick wrote:
> > OK.  I don't think I need to run a full VPN.  I just want to securely
> > connect to my router at home while I am out & about using public wifi
> > hot spots and thereby to be able to connect to the internet using my
> > ISP for browsing & email.  The only ports I should need to forward via
> > ssh to the router/server are those serving http/https for browsing and
> > 110/995/143/25/587 for email.
>
> If I understand correctly then, you need ssh (and a public IP address)
> running on the router.
[snip: and then forward a ton of ports]

Or you could forward X over the ssh tunnel, and run your web browser on 
your router. >:)

Finally, if your email program and browser are SOCKS aware, you could 
simply set them up to use your ssh connection as a SOCKS proxy.  There's 
specific support for this in OpenSSH, so that you don't have to open ports 
individually, it can be done dynamically on-demand.

> Never used it myself, but take a look at the openwrt project.
> From what I understand, it seems that it lets you put linux into the
> firmware of many popular routers, and manage it using a web interface.

While there has been some work done on a web interface, it's not a priority 
for the core OpenWRT team.  For me, manging my router from a command 
prompt worked better anyway.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-01-06  4:37 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 12:22 [gentoo-user] [OT] Router for ssh tunnel/SOCKS proxy Mick
2007-01-05 13:20 ` Uwe Thiem
2007-01-05 14:17   ` Arturo 'Buanzo' Busleiman
2007-01-05 15:53     ` Mick
2007-01-05 17:00       ` Etaoin Shrdlu
2007-01-05 20:25         ` Mick
2007-01-05 21:44           ` Etaoin Shrdlu
2007-01-05 22:00             ` kashani
2007-01-06  0:07               ` Mick
2007-01-06  0:35                 ` kashani
2007-01-08 15:53                 ` Dan
2007-01-08 17:29                   ` Boyd Stephen Smith Jr.
2007-01-08 17:43                     ` Dan
2007-01-08 18:00                       ` Boyd Stephen Smith Jr.
2007-01-06 11:01               ` Etaoin Shrdlu
2007-01-06  4:32             ` Boyd Stephen Smith Jr. [this message]
2007-01-06 10:06               ` Mick
2007-01-06 14:21                 ` Boyd Stephen Smith Jr.
2007-01-06 11:03               ` Etaoin Shrdlu

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=200701052232.45814.bss03@volumehost.net \
    --to=bss03@volumehost.net \
    --cc=gentoo-user@lists.gentoo.org \
    /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