From owner-freebsd-ipfw@FreeBSD.ORG  Wed May 22 13:50:02 2013
Return-Path: <owner-freebsd-ipfw@FreeBSD.ORG>
Delivered-To: freebsd-ipfw@smarthost.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id A363617C
 for <freebsd-ipfw@smarthost.ysv.freebsd.org>;
 Wed, 22 May 2013 13:50:02 +0000 (UTC)
 (envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2001:1900:2254:206c::16:87])
 by mx1.freebsd.org (Postfix) with ESMTP id 951D8238
 for <freebsd-ipfw@smarthost.ysv.freebsd.org>;
 Wed, 22 May 2013 13:50:02 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
 by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r4MDo1BM002964
 for <freebsd-ipfw@freefall.freebsd.org>; Wed, 22 May 2013 13:50:01 GMT
 (envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
 by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r4MDo178002963;
 Wed, 22 May 2013 13:50:01 GMT (envelope-from gnats)
Date: Wed, 22 May 2013 13:50:01 GMT
Message-Id: <201305221350.r4MDo178002963@freefall.freebsd.org>
To: freebsd-ipfw@FreeBSD.org
Cc: 
From: Ian Smith <smithi@nimnet.asn.au>
Subject: Re: kern/178482: [ipfw] logging problem from vnet jail
X-BeenThere: freebsd-ipfw@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: Ian Smith <smithi@nimnet.asn.au>
List-Id: IPFW Technical Discussions <freebsd-ipfw.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ipfw>,
 <mailto:freebsd-ipfw-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ipfw>
List-Post: <mailto:freebsd-ipfw@freebsd.org>
List-Help: <mailto:freebsd-ipfw-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
 <mailto:freebsd-ipfw-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2013 13:50:02 -0000

The following reply was made to PR kern/178482; it has been noted by GNATS.

From: Ian Smith <smithi@nimnet.asn.au>
To: bug-followup@FreeBSD.org, fbsd8@a1poweruser.com
Cc:  
Subject: Re: kern/178482: [ipfw] logging problem from vnet jail
Date: Wed, 22 May 2013 23:44:40 +1000

   > 9.1-RELEASE kernel with modules and vimage plus ipfw compiled in.
   > vnet jails running ipfw are logging to the host security file and
   > don't log any ipfw log messages to the hosts message file. Secondly
   > the vnet jails security and messages files never get populated with
   > ipfw log messages.
 
 Logging to the host's syslog rather than the jail's appears to be the
 main/real issue here, confirmed and demonstrated by Anders Hagman, see
 http://lists.freebsd.org/pipermail/freebsd-ipfw/2013-May/005398.html
 
   > logger command works. logged msg in both security and messages on
   > host
   > vnet jail can ping the public internet.
   > Hosts security file has log messages from both jail and host.
   > ipfw log messages are not being put into the hosts messages file.
 
 Apart from certain admin messages such as ipfw initialisation, 'limit N 
 reached on rule X' and 'Entry X logging count reset.' ipfw log messages 
 are never written to /var/log/messages but only to /var/log/security. 
 Since you set verbose_limit=0, you shouldn't expect to see anything from 
 ipfw in /var/log/messages, on either host or jail.
 
   > # /root >/var/log/security
   > empty file
   >
   > # /root >cat /var/log/messages
   > empty file
 
 Strange that there were not even normal bootup messages on the host?
 
 The rest serves to demonstrate the vnet jail logging-to-host issue.
 
 Ian