Hi,
I configured all my servers with to send all to a central server with
"*.* @192.168.0.10:2514" which works great.
For some test and proof-of-concepts, i'd like to have the syslog
messages also to a second logserver. However, adding "*.*
@192.168.0.22:514" on the central server 192.168.0.10 makes all messages
appear to originate from there instead of the original source ip.
Because we don't wanna go edit all servers, nor do we like to have all
messages to go twice over the wan, *IS* there a way to send the syslog
from the first syslog server to the second while preserving the original
source ip ??
Thnx, Ton
_______________________________________________
rsyslog mailing list
https://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
I configured all my servers with to send all to a central server with
"*.* @192.168.0.10:2514" which works great.
For some test and proof-of-concepts, i'd like to have the syslog
messages also to a second logserver. However, adding "*.*
@192.168.0.22:514" on the central server 192.168.0.10 makes all messages
appear to originate from there instead of the original source ip.
Because we don't wanna go edit all servers, nor do we like to have all
messages to go twice over the wan, *IS* there a way to send the syslog
from the first syslog server to the second while preserving the original
source ip ??
Thnx, Ton
_______________________________________________
rsyslog mailing list
https://lists.adiscon.net/mailman/listinfo/rsyslog
http://www.rsyslog.com/professional-services/
What's up with rsyslog? Follow https://twitter.com/rgerhards
NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.