From owner-freebsd-questions@FreeBSD.ORG  Fri Jan  7 22:36:05 2005
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
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 1181E16A4CE
	for <freebsd-questions@freebsd.org>;
	Fri,  7 Jan 2005 22:36:05 +0000 (GMT)
Received: from smtp9.wanadoo.fr (smtp9.wanadoo.fr [193.252.22.22])
	by mx1.FreeBSD.org (Postfix) with ESMTP id C935043D2F
	for <freebsd-questions@freebsd.org>;
	Fri,  7 Jan 2005 22:36:04 +0000 (GMT)
	(envelope-from atkielski.anthony@wanadoo.fr)
Received: from me-wanadoo.net (localhost [127.0.0.1])
	by mwinf0903.wanadoo.fr (SMTP Server) with SMTP id 4E6941C001D5
	for <freebsd-questions@freebsd.org>;
	Fri,  7 Jan 2005 23:36:03 +0100 (CET)
Received: from pix.atkielski.com (ASt-Lambert-111-2-1-3.w81-50.abo.wanadoo.fr
	[81.50.80.3])
	by mwinf0903.wanadoo.fr (SMTP Server) with ESMTP id 352401C001D1
	for <freebsd-questions@freebsd.org>;
	Fri,  7 Jan 2005 23:36:03 +0100 (CET)
Date: Fri, 7 Jan 2005 23:36:02 +0100
From: Anthony Atkielski <atkielski.anthony@wanadoo.fr>
X-Priority: 3 (Normal)
Message-ID: <343219484.20050107233602@wanadoo.fr>
To: freebsd-questions@freebsd.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: 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 <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jan 2005 22:36:05 -0000

Is there any kind of problem with syslogd and the -a option? I've tried
all sorts of variations (-a 10.0.0.x, -a 10.0.0.x/24, -a
myrouter.mydomain, -a myrouter.mydomain/24, etc.) and it just doesn't
seem to let anything through. Starting syslogd without any option works
(my router can write to the system log--both are on my internal LAN);
starting it with the -a option for a little more security prevents
anything at all from being written. Am I doing something wrong, or is
there a bug? I don't necessarily need the extra security (no syslog UDP
traffic can enter the LAN from the outside, anyway), but it would be
nice if I could get this option to work.

--
Anthony