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 target=remote
This one works.


Mike Hammett wrote:
Maybe the problem lies with the MT, then, because torch doesn't show anything traveling that way on port 514.

[ad...@hammett Farms] > /system logging export
# jan/27/2010 14:24:56 by RouterOS 3.30
# software id = 79KJ-8EC6
#
/system logging action
set memory memory-lines=100 memory-stop-on-full=no name=memory target=memory set disk disk-file-count=2 disk-file-name=log disk-lines-per-file=100 disk-stop-on-full=no name=disk target=disk
set echo name=echo remember=yes target=echo
set remote bsd-syslog=no name=remote remote=10.1.5.143:514 src-address=0.0.0.0 syslog-facility=daemon syslog-severity=auto target=\
   remote
/system logging
add action=memory disabled=no prefix="" topics=info
add action=memory disabled=no prefix="" topics=error
add action=memory disabled=no prefix="" topics=warning
add action=echo disabled=no prefix="" topics=critical
add action=memory disabled=yes prefix="" topics=pppoe
add action=remote disabled=no prefix=HammettFarms topics=info,warning,critical,firewall,error



netstat -an shows the machine listening on 514, but nothing is showing up.


-----
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com



--------------------------------------------------
From: "Josh Luthman" <j...@imaginenetworksllc.com>
Sent: Wednesday, January 27, 2010 2:11 PM
To: "Mikrotik discussions" <mikrotik@mail.butchevans.com>
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-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 Einstein


On Wed, Jan 27, 2010 at 3:09 PM, Mike Hammett <butch-mikro...@ics-il.net>wrote:

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 scrubbed...
URL: <
http://www.butchevans.com/pipermail/mikrotik/attachments/20100127/dab5fdd8/attachment.html
>
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik
RouterOS

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.butchevans.com/pipermail/mikrotik/attachments/20100127/3edba2a7/attachment.html>
_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS

_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS


--
Scott Reed
Owner
NewWays Networking, LLC
Wireless Networking
Network Design, Installation and Administration
Mikrotik Advanced Certified
www.nwwnet.net
(765) 855-1060


_______________________________________________
Mikrotik mailing list
Mikrotik@mail.butchevans.com
http://www.butchevans.com/mailman/listinfo/mikrotik

Visit http://blog.butchevans.com/ for tutorials related to Mikrotik RouterOS

Reply via email to