[jpgreen3]

I'm looking for feedback on syslog software to run under Windows - something that will receive syslog messages created by dd-wrt, as configured on the Services - Services tab.

I've just installed Syslog Watcher (https://syslogwatcher.com) for which a free license is available for home use. It is receiving syslog messages from dd-wrt, so far so good.

Anybody have comments, or suggestions regarding this or other syslog packages?

[ATHF]

I've tried a few of the others like Kiwi etc, I find that syslogwatcher is great. I've got it logging routers, switches, a NAS, and forwarding the logs to a secondary syslogwatcher on an old laptop.

[Alozaros]

used to have KIWISyslog but they screw it
now i have Visual Syslog its not great as Kiwi was but it works ok and its clean
just for the record and why i didn't get SyslogWatcher Virus-total reports a VIRUS_UNKNOWN

also you can find online Syslogs that are good as well

[Dr_K]

I can vouch SyslogWatcher4.8.6 only has worked very well for me for many years


Be forewarned


The companie's changed tactics are beyond questionable/shady

If you install any newer version....(which also initially claims to be free for personal use)

It hides something somewhere in your registry or somewhere?
So that if you don't shamelessly/unethically advertise for them on a public forum...& prove it (or pay for what they said was free for personal use) within X number of days

It will disable any/all previous versions of SyslogWatcher

I played in the registry on & off for more than a month trying to get v4.8.6 to work again....with NO success

Only solution I found was to redo a clean install of Windows 10

Now v4.8.6 works (more than adequately) again....but never will I ever again look to for any solution of any kind from them or
EZ5 Systems Ltd.
170-422 Richards Street
Vancouver, BC, V6B 2Z4
Canada
in the future...…..Shady Shit to say the least

Just my 2 cents

[Alozaros]

well i do posses 32bit 4.8.6 & 4.8.3 both virus total virus reported i can send you in a PM if so... just give us a note do have visualsyslog too at least its clean...

[Dr_K]

Not arguing I know everything for sure

But maybe more information should be put out there

On VirusTotal only one out of fifty-eight claim "VIRUS_UNKNOWN"... by Kingsoft

A closer look at Kingsoft Antivirus showed that the current version available was released back in 2012...and it's anyone's guess what version VirusTotal uses...or with what settings?

Makes me think of a time I put a current well used copy of CCleaner on an old WinXP pc that was using an old version of AVG Antivirus...
It barked and barked about CCleaner being a malicious virus & damaging to the pc, quarantining it at every move.

Am I really the only one to have seen an antivirus package produce a false positive just to justify its use or purchase?

I stand behind my comments in regards to v4.8.6 & v.4.8.3 for that matter as they have worked well for several years, with NO odd or otherwise issues, except what I explained earlier in regards to newer versions.

But hey...one can never be too sure...I guess..

[Alozaros]

[Dr_K]

Boy...you seem to like picking an arguement with me for some unknown reason...

Makes me wounder how you could have run out of off/misguided responses in the erase nvram thread??

Not an arguement....but curious...

In your CCleaner test....did you go through the settings and disable auto check for updates....share unanimous usage data statics etc prior?

Strange how you are the first I've seen to flag it as malicious...other than a 15+ year old copy of AVG, that no doubt was just confused.

Also, about not being able to controle syslog's net usage because of it's nature...

Could you not easily neuter it's network usage to be limited to where you specify through Windows firewall? If you had concerns.

Let me be clear to everyone here
I am not trying to scare you or trick you to do something you do not want to do.

Just sharing my thoughts & good experiences about something originally inquired about.

[Alozaros]

[ezfive]

My name is Sergey. I am the founder of EZ5 Systems (the developer of Syslog Watcher). Yes, there was an unintentional interference between licensing in Syslog Watcher 4 and first releases of SW version 5. We fixed it in 5.0.2.

Version history here:
https://support.syslogwatcher.com/support/solutions/articles/8000069110-syslog-watcher-5-0-release-notes

We were not going to force our users to upgrade to version 5 this way

[yodamin]

PFsense was setup for the past 2-3 years.

DDWRT is a recent experiment when I found I needed a more flexible firmware on my WiFi routes -received LOTS of help from this community setting up bridge WiFi connection - THANK YOU again!

Graylog Server is my recent addition to the home network - just finished install/config and all is working just fine - all logs being sent to my Linux box running Xubuntu 18.04 LTS and Graylog Server 3.0. I used a bunch of so-called tutorials on the web (nothing specific to MY situation - but learned LOTS from reading/doing them, messing it all up, starting over - apt purge is a dear friend now -, trying this and that, etc,etc,etc...) and over the past five days got this working, then that working, but the other thing was borked - I'm sure you know all know the feeling.

Found the actual Graylog tutorial for the install and basic config of a stand alone Graylog server here: http://docs.graylog.org/en/3.0/pages/installation/os/ubuntu.html

So I purged all three applications needed for Graylog Server once again (including any left overs you'll find in /var/lib/(elasticsearch), /etc/(elasticsearch) and /var/log and had to do apt autoremove to get rid of the mongo-db (mongodb-org) - but after that and a reboot I followed the tutorial exactly and was up and running Graylog within 10 minutes, another 10 minutes to configure pfsense and both ddwrt routers to send their logs to the Graylog server and I now have a fully working syslog server accepting inputs from three devices.

- about 8-10 hrs total from reading/experiment to completed/fully functional.

Now I am experimenting with various ways to pretty up the input before displaying it to me. Fun, fun,fun!


The biggest obstacle I ran into was knowing that this version of elasticsearch will NOT work EVER with that version of graylog or vice versa...the graylog/mongodb/elasticsearch MUST all be compatible and one has to be very careful afterward when updating/upgrading those components or - borked!!

Hope this helps someone, sometime, somewhere.

[yodamin]

Added nxlog to the mix in order to get WinSrv logs into Graylog last night - took about 15 minutes total to get the input up and running - Windows config of nxlog to forward event logs to Graylog is pretty straight forward; likewise the input configuration on Graylog itself.

So, for a remote syslogger I would say graylog/nxlog will have you covered for all your systems, for free (other than about 10hrs of reading/experimenting that is:-) - not to shabby. Now to see how long it lasts without going borked on me.......