Yes, sorry. Copy & paste worked bad. I just removed some unnecessary lines and re-ordered some directives. Now it works.
Sorry for the noise. Martin > -----Original Message----- > From: [email protected] [mailto:rsyslog- > [email protected]] On Behalf Of Rainer Gerhards > Sent: 24 February 2009 15:53 > To: rsyslog-users > Subject: Re: [rsyslog] Not logging TCP connections? > > Martin, on the client @ is udp while @@ is TCP (!) ;) > > Rainer > > > -----Original Message----- > > From: [email protected] [mailto:rsyslog- > > [email protected]] On Behalf Of Martin Mielke > > Sent: Tuesday, February 24, 2009 3:48 PM > > To: rsyslog-users > > Subject: [rsyslog] Not logging TCP connections? > > > > Hi, > > > > Sorry to sound a bit blonde here but... > > I need rsyslog to accept both TCP and UDP connections to port 514. > > > > I have the following relevant parts on the server side: > > -- > > ... > > $DefaultNetstreamDriver ptcp > > > > # UDP Syslog Server: > > $UDPServerRun 514 # start a UDP syslog server at standard port 514 > > > > > > $InputTCPServerStreamDriverAuthMode anon > > $InputTCPServerStreamDriverPermittedPeer *.mydomain > > $InputTCPServerStreamDriverMode 0 # run driver in no-TLS mode > > $InputTCPServerRun 514 > > ... > > -- > > > > ...also disabled all the certificates/keys files just in case > > > > > > And on the client side> > > -- > > # remote host is: name/ip:port, e.g. 192.168.0.1:514, port optional > > *.* @logserver.mydomain > > -- > > > > After restarting rsyslog on the server it only logs UDP traffic... > > > > Am I overseeing something the obvious? > > > > > > Regards, > > Martin > > > > > > This email and any attachments are confidential, and may be legally > > privileged and protected by copyright. If you are not the intended > > recipient dissemination or copying of this email is prohibited. If you > > have received this in error, please notify the sender by replying by > > email and then delete the email completely from your system. > > > > Any views or opinions are solely those of the sender. This > > communication is not intended to form a binding contract unless > > expressly indicated to the contrary and properly authorised. Any > > actions taken on the basis of this email are at the recipient's own > > risk. > > > > > > _______________________________________________ > > rsyslog mailing list > > http://lists.adiscon.net/mailman/listinfo/rsyslog > > http://www.rsyslog.com > _______________________________________________ > rsyslog mailing list > http://lists.adiscon.net/mailman/listinfo/rsyslog > http://www.rsyslog.com _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
