From owner-freebsd-stable Mon Mar 27 17:55:19 2000 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id A63CD37B7F1 for ; Mon, 27 Mar 2000 17:55:17 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id RAA70782; Mon, 27 Mar 2000 17:48:07 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 27 Mar 2000 17:48:06 -0800 (PST) From: Doug White To: Mike Nowlin Cc: Andreas Klemm , stable@FreeBSD.ORG Subject: Re: HEADS-UP please: syslogd problems in 4.0: rejected in rule 0 due to port mismatch. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 27 Mar 2000, Mike Nowlin wrote: > > > What port is the cisco sending the syslog updates from? The default -a > > requires it to be sent *from* the syslogd port. A tcpdump is probably in > > order. > > Is this "the right way" to do it? I'm just wondering why the requirement > that the messages come from the syslog port. My Linux & DEC UNIX machines > don't require this, although they're not using any kind of allowed_peer > restrictions - just "remote logging enabled". You'll have to ask Joerg, he wrote the patch :) rev 1.25 in src/sys/usr.sbin/syslogd.c Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message