public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
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:01:37 -0500	[thread overview]
Message-ID: <87oc40d9wu.fsf@newsguy.com> (raw)
In-Reply-To: 20110420181540.GA11297@ns1.bonedaddy.net

Todd Goodman <tsg@bonedaddy.net> writes:

> OpenWRT is running the BusyBox syslogd by default.  I doubt it would take
> much to build a syslog-ng (or whatever other logger you prefer) if there
> isn't already a package for it.
>
> Oh, I see that there already are syslog-ng (1.6.12-2) and syslog-ng3
> (3.0.5-1) packages
>
> You have iptables support so you can do pretty much anything you like
> with regards to logging.

Ahh, thanks.  

I just posted again about logging and mentioned I couldn't tell much
about it at the dd-wrt wiki.   

However, now I see a lot more info at the dd-wrt wiki than I saw
at first too .... er... I take it all back.

http://www.dd-wrt.com/wiki/index.php/Logging_with_DD-WRT




  reply	other threads:[~2011-04-20 19:03 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 [this message]
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
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=87oc40d9wu.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