Mailing List ArchiveSupport open source code!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]Re: syslog by remote ip
- To: tlug@example.com
 - Subject: Re: syslog by remote ip
 - From: Darren Cook <darrenj@example.com>
 - Date: Wed, 31 Jan 2001 15:48:41 +0900
 - Content-Transfer-Encoding: 7bit
 - Content-Type: text/plain; charset=iso-2022-jp
 - References: <3A6C28ED.AAA3CC63@example.com> <20010123165011.B887@example.com>
 - Reply-To: tlug@example.com
 - Resent-From: tlug@example.com
 - Resent-Message-ID: <e03b6D.A.kNH.hU7d6@example.com>
 - Resent-Sender: tlug-request@example.com
 
> than "user"? You could tell your MN-128-SOHO to use a > different facility: > ip syslog facility 21 > (which /usr/include/sys/syslog.h tells me is facility local5). > And then filter local5.* off to /var/log/router. Thanks Jim (and Scott), Finally got back to this, and now have it working this way (and "ip rip off"). While I poking around the help files I noticed this router has quite a few more features than my earlier model, e.g. giving certain addresses/ports priorities. I might have to play with that next time my wife is trying to do some Net Shopping ;-). Darren
- References:
 
- syslog by remote ip
 
- From: Darren Cook <darrenj@example.com>
 - Re: syslog by remote ip
 
- From: Jim Tittsler <jwt-tlug@example.com>
 Home | Main Index | Thread Index
- Prev by Date: Re: gcc upgrade
 - Next by Date: Re: gcc upgrade
 - Prev by thread: Re: syslog by remote ip
 - Next by thread: ReiserFS patches
 - Index(es):
 
Home Page Mailing List Linux and Japan TLUG Members Links