From owner-freebsd-questions Tue Jan 29 5:26:51 2002 Delivered-To: freebsd-questions@freebsd.org Received: from smnolde.com (att-98-60-141.atl.mediaone.net [24.98.60.141]) by hub.freebsd.org (Postfix) with ESMTP id 28C5E37B404 for ; Tue, 29 Jan 2002 05:26:42 -0800 (PST) Received: from bsd ([192.168.10.7]) by smnolde.com with esmtp (Exim 3.30 #1) id 16VYHZ-000OOm-00; Tue, 29 Jan 2002 08:26:41 -0500 Date: Tue, 29 Jan 2002 08:26:40 -0500 (EST) From: Scott Nolde To: Richard Cc: Subject: Re: Problems with syslog ??????? In-Reply-To: <000501c1a8c4$5cf10400$aa40a8c0@drtvtim.ro> Message-ID: <20020129082542.C1378-100000@bsd.smnolde.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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 >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