What I have works, but it was setup quite a while ago, so there maybe something I have missed here.
Now In dude:
In Notifications section
Add a Notification
Call it "log to syslog"
It is of type log
log prefix=syslog
Schedule should be active all the time
Advanced, sorry not sure, doesn't really seem relevant.
In Settings (Server Configuration) /Syslog Tab
Enabled
Port 514
Add an entry
Action=accept Notification="log to syslog"
# testing
In winbox, system logging
change rule with script topic (created above) to action=dudeSyslog
then
With luck you should get 2 messages in log again,
but now one message should be dude, event, and have syslog: prefix in front of it.
Change script rule action back to dudeLog (or disable it)
Edit: Also need to firewall rule to allow udp port 514 input.
Code:
/system logging actionadd disk-file-count=10 disk-file-name=disk1/dudeLog/dudeLogNew disk-lines-per-file=4000 name=dudeLog target=\ disk# for testing (later) add name=dudeSyslog remote=127.0.0.1 target=remote/system loggingadd action=dudeLog topics=dudeadd action=dudeLog topics=script# testing# Should get 2 entries, one sent to memory, second to dudeLog./log info message="testing"Now In dude:
In Notifications section
Add a Notification
Call it "log to syslog"
It is of type log
log prefix=syslog
Schedule should be active all the time
Advanced, sorry not sure, doesn't really seem relevant.
In Settings (Server Configuration) /Syslog Tab
Enabled
Port 514
Add an entry
Action=accept Notification="log to syslog"
# testing
In winbox, system logging
change rule with script topic (created above) to action=dudeSyslog
then
Code:
/log info message="testing"but now one message should be dude, event, and have syslog: prefix in front of it.
Change script rule action back to dudeLog (or disable it)
Edit: Also need to firewall rule to allow udp port 514 input.
Statistics: Posted by rplant — Sat Feb 03, 2024 8:43 am