ttp://www.ics-il.com
--
From: "Butch Evans"
Sent: Tuesday, February 02, 2010 12:47 AM
To: "Mikrotik discussions"
Subject: Re: [Mikrotik] MT syslog
On Thu, 2010-01-28 at 00:17 -0600, Mike Hammett wrote:
That's what I get for just taking stuff off the wiki.
On Thu, 2010-01-28 at 00:17 -0600, Mike Hammett wrote:
> That's what I get for just taking stuff off the wiki. :-p
It's not "just taking stuff" that poses problems. It's taking stuff
that you don't fully understand that poses problems. I'm not "picking
on you", but just taking this chance to "
k"
Subject: Re: [Mikrotik] MT syslog
Ahh. There's your problem.
You are telling it to log messages that have "info AN warning AND
critical AND firewall AND error" topics. Which none will. Create one
for each, and you should be set.
This tripped me up too.
-Origi
rsyslog
-
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
--
From: "Corey Freeman"
Sent: Wednesday, January 27, 2010 3:45 PM
To: "Mikrotik discussions"
Subject: Re: [Mikrotik] MT syslog
What a
essage-
From: Josh Luthman [mailto:j...@imaginenetworksllc.com]
Sent: Wednesday, January 27, 2010 4:52 PM
To: Mikrotik discussions
Subject: Re: [Mikrotik] MT syslog
add action=remote disabled=no prefix=HammettFarms
topics=info,warning,critical,firewall,error
Those have the topics (all of them?)
Josh Luth
Message-
>> From: Josh Luthman [mailto:j...@imaginenetworksllc.com]
>> Sent: Wednesday, January 27, 2010 4:52 PM
>> To: Mikrotik discussions
>> Subject: Re: [Mikrotik] MT syslog
>>
>> add action=remote disabled=no prefix=HammettFarms
>> topics=info,warni
should be set.
> This tripped me up too.
>
>
> -Original Message-
> From: Josh Luthman [mailto:j...@imaginenetworksllc.com]
> Sent: Wednesday, January 27, 2010 4:52 PM
> To: Mikrotik discussions
> Subject: Re: [Mikrotik] MT syslog
>
> add action=remote disable
thman [mailto:j...@imaginenetworksllc.com]
Sent: Wednesday, January 27, 2010 4:52 PM
To: Mikrotik discussions
Subject: Re: [Mikrotik] MT syslog
add action=remote disabled=no prefix=HammettFarms
topics=info,warning,critical,firewall,error
Those have the topics (all of them?)
Josh Luthman
Office: 937-552-2340
eed [mailto:sr...@nwwnet.net]
> Sent: Wednesday, January 27, 2010 4:38 PM
> To: Mikrotik discussions
> Subject: Re: [Mikrotik] MT syslog
>
> Looks like mine
> set remote bsd-syslog=no name=remote remote=w.x.y.z:514 src-address=\
>0.0.0.0 syslog-facility=daemon syslog-severity=auto
>
>
> -
> Mike Hammett
> Intelligent Computing Solutions
> http://www.ics-il.com
>
>
>
> --
> From: "Josh Luthman"
> Sent: Wednesday, January 27, 2010 2:11 PM
> To: "Mikrotik discussions"
&g
thman"
Sent: Wednesday, January 27, 2010 2:11 PM
To: "Mikrotik discussions"
Subject: Re: [Mikrotik] MT syslog
Couldn't you just torch the MT itself and watch it send something? If
you're sending error to syslog type :log error "foo"
Josh Luthman
Office: 937-5
mett
Intelligent Computing Solutions
http://www.ics-il.com
--
From: "Josh Luthman"
Sent: Wednesday, January 27, 2010 2:11 PM
To: "Mikrotik discussions"
Subject: Re: [Mikrotik] MT syslog
Couldn't you just torch the MT itself and watch it send something?
Couldn't you just torch the MT itself and watch it send something? If
you're sending error to syslog type :log error "foo"
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
"The secret to creativity is knowing how to hide your sources."
--- Albert Ein
Does anyone know if MT sends out syslog information on TCP or UDP? I know it's
port 514. I've figured out how to have rsyslog listen to UDP 514, but not TCP.
-
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
-- next part --
An HTML attachment was
14 matches
Mail list logo
