Date: Tue, 29 Jan 2002 08:26:40 -0500 (EST) From: Scott Nolde <scott@smnolde.com> To: Richard <richard@drtvtim.ro> Cc: <questions@FreeBSD.org> Subject: Re: Problems with syslog ??????? Message-ID: <20020129082542.C1378-100000@bsd.smnolde.com> In-Reply-To: <000501c1a8c4$5cf10400$aa40a8c0@drtvtim.ro>
next in thread | previous in thread | raw e-mail | index | archive | help
Use syslog-ng in ports to log your cisco routers. I ran into a similar problem. It'll never miss a packet and it is very flexible. - Scott Thus sayeth the previous author: >Date: Tue, 29 Jan 2002 14:55:52 +0200 >From: Richard <richard@drtvtim.ro> >To: questions@FreeBSD.org >Subject: Problems with syslog ??????? > >Hi there! > >I'm running : FreeBSD 4.3 Stable > >I'm using syslog (besides the usual) to log from my Routers (Allied + >Cisco) the problem is that if I'm trying to limit the access to syslog >(from unwanted incoming UDP datagrams) by using the -a (allowed peer) >parameter (eg. -a 192.168.64.200/24:*) syslog is not logging the >incoming UDP datagrams (UDP datagrams reach the server, verified with >tcpdump), only if I run syslog simply (without -a parameter). > >Any idea or suggestion would be higly appreciated. This issue is of >great importance for me and my office (ISP domain). > >Thank you in advance, >Richard > Scott Nolde GPG Key 0xD869AB48 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020129082542.C1378-100000>