Some devices require logging to function. When using tcp and a problem develops on the syslog server the device sending syslogs will stop functioning, Cisco PIX firewall is one such device. -----Original Message----- From: Mikael Olsson [mailto:mikael.olssonat_private] Sent: Friday, January 03, 2003 8:51 AM To: Rainer Gerhards Cc: loganalysisat_private Subject: Re: [logs] Syslog over TCP (Was: Re: Syslog payload format) Rainer Gerhards wrote: > > > 2) output, send the formatted message to > > - local syslogd > > - RFC3164 via UDP > > - RFC3164 via TCP > > Hey, are you anticipating a standard on 3164 over TCP ;-). Well, I'd > agree to this as long as there can be consensus reached on how to do > this. Andrew's suggestion might be a good thing to go... Honestly, I > don't care if it'll be an RFC or not, but I would like to see at least > 4 implementors promising they will implement it this year (yes, this > now again leaves us much time ;)). *hand raised and waving eagerly* I for one would love to start sending syslog data via TCP. What's the technical low-down of this suggestion you're talking about? (Sorry, recently subscribed) > - RFC3195 via TCP BEEP gives me nervous twitches every time I look at the specs. -- Mikael Olsson, Clavister AB Storgatan 12, Box 393, SE-891 28 ÖRNSKÖLDSVIK, Sweden Phone: +46 (0)660 29 92 00 Mobile: +46 (0)70 26 222 05 Fax: +46 (0)660 122 50 WWW: http://www.clavister.com _______________________________________________ LogAnalysis mailing list LogAnalysisat_private http://lists.shmoo.com/mailman/listinfo/loganalysis _______________________________________________ LogAnalysis mailing list LogAnalysisat_private http://lists.shmoo.com/mailman/listinfo/loganalysis
This archive was generated by hypermail 2b30 : Fri Jan 03 2003 - 18:56:50 PST