From owner-freebsd-net@FreeBSD.ORG  Mon Oct 13 22:37:26 2003
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 48CDC16A4B3
	for <freebsd-net@freebsd.org>; Mon, 13 Oct 2003 22:37:26 -0700 (PDT)
Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su
	[213.184.65.80])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1E20543F93
	for <freebsd-net@freebsd.org>; Mon, 13 Oct 2003 22:37:24 -0700 (PDT)
	(envelope-from eugen@kuzbass.ru)
Received: from kuzbass.ru (kost [213.184.65.82])h9E5bHs6051599;
	Tue, 14 Oct 2003 13:37:18 +0800 (KRAST)
	(envelope-from eugen@kuzbass.ru)
Message-ID: <3F8B8B8B.4D778985@kuzbass.ru>
Date: Tue, 14 Oct 2003 13:37:15 +0800
From: Eugene Grosbein <eugen@kuzbass.ru>
Organization: SVZServ
X-Mailer: Mozilla 4.8 [en] (Win98; U)
X-Accept-Language: ru,en
MIME-Version: 1.0
To: "Eric W. Bates" <ericx_lists@vineyard.net>
References: <02df01c391ec$ce67bbc0$3ee380cc@alice>
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: 7bit
cc: freebsd-net@freebsd.org
Subject: Re: Where do ipfw kern:emerg logs come from?
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Oct 2003 05:37:26 -0000

"Eric W. Bates" wrote:

> The messages actually appear to be truncated versions of the security.info
> messages:
> 
> Oct 13 14:11:26 <security.info> brock /kernel: ipfw: 400 UNKNOWN TCP
> 192.168.1.91:1104 208.172.16.132:80 out via de0
> Oct 13 14:11:26 <security.info> brock /kernel: ipfw: 500 SkipTo 10000 TCP
> 192.168.1.91:1104 208.172.16.132:80 out via de0
> Oct 13 14:11:26 <security.info> brock /kernel: ipfw: 10000 Divert 8668 TCP
> 192.168.1.91:1104 208.172.16.132:80 out via de0
> 
> I found ipfw logging code sys/netinet/in ip_fw.c; but there doesn't seem to
> be anything using LOG_KERN or LOG_EMERG.
> 
> Is this a bug?

I guess syslogd is guilty.

Eugene Grosbein