Any progress? We 'd like to switch to relp (compressed, encrypted) but I
imagine I'll have the same issue, and I can't easily generate the
traffic needed to test. We have a work around for the regular issue.
Each syslog machine runs two rsyslog processes on a different port
(non-TLS). A local nginx instance takes the SSL traffic. terminates it,
and least_conn connects the data to the two syslog processes. This has
been working well for weeks.
This solution does not work for the relp case, as it appears with the
compression, it does not work to blindly decrypt, the nginx proxy would
have to understand the payload, which it does not.
--
Sent from Postbox
<https://www.postbox-inc.com/?utm_source=email&utm_medium=siglink&utm_campaign=reach>
_______________________________________________
rsyslog mailing list
http://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.
