I like this "workaround".
Thanks,
Dalibor
On 03. 08. 20 15:06, Tod A Sandman via rsyslog wrote:
I'm watching this thread for a better solution, but the work-around I've used
for years is to use imptcp for non-TLS and imtcp for TLS:
## Plain TCP syslog reception:
module (load="imptcp")
## TCP syslog reception:
module (load="imtcp"
MaxListeners = "30"
MaxSessions = "1024"
StreamDriver.Name="ossl"
# StreamDriver.Name="gtls"
StreamDriver.Mode="1"
StreamDriver.AuthMode="x509/name"
# StreamDriver.AuthMode="anon"
PermittedPeer=.....
)
And when I need to open a new port or create a new ruleset, I tie it to
appropriate module depending on whether TLS or non-TLS is needed:
root@logs-n2:~> cat /etc/rsyslog.d/inputs/port514.conf
## Define port 514 listeners, bound to the appropriate ruleset:
input(type="imptcp" name="tcp-514" port="514" ruleset="port514")
input(type="imudp" name="udp-514" port="514" ruleset="port514")
root@logs-n2:~> cat /etc/rsyslog.d/inputs/port6514.conf
## Define port 6514 listener, bound to the appropriate ruleset:
input(type="imtcp" name="tcp-6514" port="6514" ruleset="port6514")
Tod A. Sandman
_______________________________________________
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.
_______________________________________________
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.
