Remote logging from one mikrotik to another mikrotik

Hi all,
I have some mikrotiks with USB ports used by flashdisks for logging purposes (logging to disk). Another mikrotiks do not have USB port, so logging is only possible to be saved on internal flash that I do not want (due to heavy overwriting and therefore damaging the memory cells).

As the mikrotik can act as syslog client, is it also possible to set it as syslog server? I would like to store logs remotely from one mikrotik to another.

Or is there some by-pass (e.g. by mounting remotely shared folder as disk) or whatever else that that could solve the remote logging from one mikrotik to another?

Hope you understand what I mean.

Hi,
I’m not a pro, I’m amateur but this is what I think:

Try the configure an action “Remote”..
WinBox: System - Logging tab Actions line Remote.
First, configure the action “Remote”, then on the Rules tab to configure the rules you need for this action.


Howto Save Mikrotik Logs to Remote SYSLOG Server (linux):
http://aacable.wordpress.com/2011/11/29/howto-save-mikrotik-logs-to-remote-syslog-server/
Manual:System/Log:
http://wiki.mikrotik.com/wiki/Manual:System/Log

Well,
the question is not about setting of remote logging client. The question is, how to set remote logging server on mikrotik.

Because, why to run additional server just to receive logs if there is another mikrotik that is already saving its own logs to USB disk?

Anyone interested in? None thinks it could be useful? None knows how to do it?

+1

I like that :smiley:
but i dont think MT would listen to port 514, hmm?

You said you don’t like that logs are stored to disk, but instead want to store them in built-in syslog. Syslog would also store them in the disk :slight_smile:

Anyway, thank you for the feature suggestion. What other features would you like? Syslog servers usually have advanced abilities to display the logs. We would need an entirely new log viewer then. Lots of things need to be added, it is not trivial

Yea, I understand. Actually I would not asked for this if the Dude package would be working well inside ROS. Because it already has sufficient logserver capabilities.

So the answer is: Make it to be working at least like in Dude.

But, if there is some decision making between the Dude development or syslog server development, HELL, MAKE THE DUDE!! and forget the syslog sever.