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: Sat, 6 Jan 2007 08:21:38 -0600 [thread overview]
Message-ID: <200701060821.38269.bss03@volumehost.net> (raw)
In-Reply-To: <200701061006.36892.michaelkintzios@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2699 bytes --]
On Saturday 06 January 2007 04:06, Mick <michaelkintzios@gmail.com> wrote
about 'Re: [gentoo-user] [OT] Router for ssh tunnel/SOCKS proxy':
> On Saturday 06 January 2007 04:32, Boyd Stephen Smith Jr. wrote:
> > 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:
> > > > 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.
> > Or you could forward X over the ssh tunnel, and run your web browser
> > on your router. >:)
> Thanks, I also thought of running FreeNX on the router, if only the
> router were capable of running apps. It seems that openwrt is not
> (yet?) covering the netgear DG834. The wireless version DG834G is shown
> as WIP on the openwrt website. I'll keep an eye on it, or one day
> upgrade my router.
There may be another project out there that works with your router -- I
know there was one specifically targeting D-Links for a while... search
around. You might also see if anyone has tested OpenWRT on your firmware,
WIP might mean that it just takes some massaging (which could mean
anything from a few minor config file changes, to a custom build of
Kamikaze), but is still available an an option.
> > 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.
>
> How do you set firewall rules using opewrt? Through a script?
Well, you can use the WIP web interface, or you can get a shell and edit
the firewall rules. It's standard linux, so you can use iptables directly
for simple one-off changes that last until you reboot. IIRC, there is
also an /etc/init.d/20firewall script that reads iptables rules out
of /etc/firewall or somesuch. (Haven't messed with the OpenWRT since I
moved in May.) I believe shorewall is also available as an ipkg from the
WRT developers.
--
"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 --]
next prev parent reply other threads:[~2007-01-06 14:26 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.
2007-01-06 10:06 ` Mick
2007-01-06 14:21 ` Boyd Stephen Smith Jr. [this message]
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=200701060821.38269.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