public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] Router for ssh tunnel/SOCKS proxy
Date: Fri, 5 Jan 2007 20:25:54 +0000	[thread overview]
Message-ID: <200701052026.04236.michaelkintzios@gmail.com> (raw)
In-Reply-To: <200701051800.10572.shrdlu@unlimitedmail.org>

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

On Friday 05 January 2007 17:00, Etaoin Shrdlu wrote:
> On Friday 5 January 2007 16:53, Mick wrote:
> > > More about that here:
> > >
> > > "Why TCP over TCP is a Bad Idea"
> > > http://sites.inka.de/sites/bigred/devel/tcp-tcp.html
> >
> > Hmm, that explains why running VCN through ssh gets a bit ropy at
> > times?
>
> Do you mean VNC?

Yes, if only I could type properly!  ;-)

> > So, is port forwarding for browsing and emails through ssh a
> > bad idea then?
>
> No, because with ssh port forwarding you just forward the data coming
> from/going to the application (eg, mailreader) without stacking
> additional protocols (as in, for example, ppp or ip over ssh), for which
> you need some way of forwarding IP-or-lower-level data between
> interfaces (for example, using tun/tap).
> Some programs (like openvpn) overcome the issue by using tcp-over-udp by
> default.

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 the above assumptions are correct then what sort of a hardware router would 
I need?  (Either a straight off the shelf product, or one with modified 
firmware).

Friends and colleagues often ask me how to achieve this, but all I 
can think is running a PC on the LAN as a server for this purpose - isn't this 
effectively a SOCKS5 server or am I getting mixed up here?

No idea how to achieve the same functionality using the embedded OS of a 
hardware router.

Thank you for your help.
-- 
Regards,
Mick

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

  reply	other threads:[~2007-01-05 20:30 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 [this message]
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.
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=200701052026.04236.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --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