From: Harry Putnam <reader@newsguy.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: [OT router advice] a router capable of detailed logs
Date: Wed, 20 Apr 2011 14:14:46 -0500 [thread overview]
Message-ID: <87k4eod9ax.fsf@newsguy.com> (raw)
In-Reply-To: F2756E4E-AC34-46D7-A8D3-D2C51491CD99@stellar.eclipse.co.uk
Stroller <stroller@stellar.eclipse.co.uk> writes:
> On 19/4/2011, at 4:31am, Harry Putnam wrote:
>> ...
>> So, cutting to the chase; can anyone recommend from actual use, a home
>> lan router that has gigabit lan ports and very configurable/
>> informative logging options?
>>
>> ps - I'm not interested in running an old linux or openbsd, machine as
>> router. Having a silent cool router the size and weight of a medium
>> book is too appealing.
>
> Consider OpenWRT. You can run it on something like the Netgear
> WNR2000, the Buffalo WZR-HP-G300NH, or something even cheaper if you
> don't need wifi.
All good, except then you have to muck around with iptables. I once
knew a bit about that when it first replaced ipchains in linux
distros... thats' been yrs ago, and I've completely forgotten whatever
I may have learned back then. I ended up switching to PF filter on
OpenBSD for firewall/router... and have now forgotten all about that too.
Are you using openWRT on a router yourself?
If so, is there a basic iptables script rigged up for numbskulls to be
able to add and subtract from it readily?
I actually wrote such a thing for myself way back when. (The part for
numbskulls, not iptables) but would not look forward to trying to
remaster what ever I need to know about iptables to use openWRT.
next prev parent reply other threads:[~2011-04-20 19:17 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-19 3:31 [gentoo-user] [OT router advice] a router capable of detailed logs Harry Putnam
2011-04-19 6:02 ` Mick
2011-04-20 15:56 ` [gentoo-user] " Harry Putnam
2011-04-21 5:55 ` Mick
2011-04-21 5:58 ` Mick
2011-04-22 19:28 ` Harry Putnam
2011-04-22 22:17 ` Mick
2011-04-25 17:37 ` Harry Putnam
2011-04-25 18:20 ` Paul Hartman
2011-04-25 19:04 ` Mick
2011-04-25 18:44 ` Mick
2011-04-25 22:23 ` Jake Moe
2011-04-26 6:08 ` Mick
2011-04-26 22:27 ` Harry Putnam
2011-04-27 6:23 ` Mick
2011-04-28 5:31 ` Harry Putnam
2011-04-28 14:36 ` Todd Goodman
2011-04-30 4:28 ` Harry Putnam
2011-04-30 15:02 ` Todd Goodman
2011-04-28 16:07 ` Mick
2011-04-19 6:54 ` [gentoo-user] " Joost Roeleveld
2011-04-20 16:16 ` [gentoo-user] " Harry Putnam
2011-04-19 9:15 ` [gentoo-user] " Peter Humphrey
2011-04-20 16:23 ` [gentoo-user] " Harry Putnam
2011-04-20 18:49 ` Dale
2011-04-20 19:38 ` Harry Putnam
2011-04-20 19:50 ` Dale
2011-04-20 22:36 ` Peter Humphrey
2011-04-20 22:36 ` Harry Putnam
2011-04-20 23:35 ` Dale
2011-04-21 5:37 ` Pandu Poluan
2011-04-19 10:17 ` [gentoo-user] " Pandu Poluan
2011-04-19 10:18 ` Stroller
2011-04-19 14:50 ` Paul Hartman
2011-04-20 2:01 ` W.Kenworthy
2011-04-20 18:50 ` [gentoo-user] " Harry Putnam
2011-04-20 18:15 ` Harry Putnam
2011-04-20 18:15 ` Todd Goodman
2011-04-20 19:01 ` Harry Putnam
2011-04-20 18:48 ` Paul Hartman
2011-04-20 19:28 ` Harry Putnam
2011-04-20 20:11 ` Paul Hartman
2011-04-20 22:41 ` Harry Putnam
2011-04-21 12:22 ` Todd Goodman
2011-04-22 20:25 ` Harry Putnam
2011-04-22 22:47 ` Todd Goodman
2011-04-20 19:14 ` Harry Putnam [this message]
2011-04-30 17:47 ` James
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=87k4eod9ax.fsf@newsguy.com \
--to=reader@newsguy.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