locky37 / eventlog-to-syslog

Automatically exported from code.google.com/p/eventlog-to-syslog
0 stars 0 forks source link

does not broadcast syslog information to 127.0.0.1 #51

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. set LogHost value to 127.0.0.1
2. restart the service
3. do something that generates an event log entry

What is the expected output? What do you see instead?
I expect a syslog entry to be generated. Instead I see nothing.

What version of the product are you using? On what operating system?
Tried the 32 bit 4.4.2 version on XP and the 64bit version on Windows 2008 
server

Please provide any additional information below.
I set up an stunnel listening on 127.0.0.1:514 to TLS encrypt the data being 
logged, but the only way any data gets sent to the pipe is if I change the ip 
address for evtsys to my network ip address. However, I do not want the log 
data broadcast across the network so I would like to use the local loopback ip.

Original issue reported on code.google.com by james.ki...@gmail.com on 3 Nov 2011 at 8:06

GoogleCodeExporter commented 9 years ago
Did you enable the TCP support in evtsys? Stunnel will not work with UDP out of 
the box.

Original comment by sherwin....@gmail.com on 4 Nov 2011 at 2:19

GoogleCodeExporter commented 9 years ago
EnableTcp is set to one in the registry. It works fine if I put my lan ip 
address. Just not the loopback ip. 

Original comment by james.ki...@gmail.com on 4 Nov 2011 at 2:01

GoogleCodeExporter commented 9 years ago
hmmm. I apologize. This must have been a problem with stunnel (or my stunnel 
configuration) because this is working today. The only thing I can think of 
that I changed was I started using ssh to forward my ports instead of stunnel.

Thanks for your help Sherwin.

Original comment by james.ki...@gmail.com on 8 Nov 2011 at 3:09

GoogleCodeExporter commented 9 years ago

Original comment by sherwin....@gmail.com on 15 Dec 2011 at 2:31