From owner-freebsd-questions@FreeBSD.ORG Sat Jan 8 07:21:09 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E60716A4CE for ; Sat, 8 Jan 2005 07:21:09 +0000 (GMT) Received: from smtp5.wanadoo.fr (smtp5.wanadoo.fr [193.252.22.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AEF143D31 for ; Sat, 8 Jan 2005 07:21:09 +0000 (GMT) (envelope-from atkielski.anthony@wanadoo.fr) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0506.wanadoo.fr (SMTP Server) with ESMTP id CC41B1C002A4 for ; Sat, 8 Jan 2005 08:21:07 +0100 (CET) Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr [81.50.80.3]) by mwinf0506.wanadoo.fr (SMTP Server) with ESMTP id B216C1C002A5 for ; Sat, 8 Jan 2005 08:21:07 +0100 (CET) Date: Sat, 8 Jan 2005 08:21:07 +0100 From: Anthony Atkielski X-Priority: 3 (Normal) Message-ID: <1883206833.20050108082107@wanadoo.fr> To: freebsd-questions@freebsd.org In-Reply-To: <41DF15F8.1070900@yahoo.com> References: <343219484.20050107233602@wanadoo.fr> <41DF15F8.1070900@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: Is there a problem with syslogd -a? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: freebsd-questions@freebsd.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jan 2005 07:21:09 -0000 Rob writes: R> On 5.3, I have following in rc.conf: R> syslogd_flags="-a 192.168.123.0/24 -b 192.168.123.254" R> R> on the machine that has IP 192.168.123.254. R> It serves a cluster of 192.168.123.X with X = 1 to 7 R> R> /etc/syslog.conf on the 192.168.123.X PCs has: R> *.* @192.168.123.254 R> R> and all syslog messages arrive on 192.168.123.254 and are stored there. Thanks. I had not used the -b argument, but I think I found the problem: I have to put -a 10.0.0.0/24:* in order to accept messages from something other than syslog. I'm not sure what the router is calling itself,but apparently syslog isn't it. When I use the wildcard, it works. -- Anthony