From owner-freebsd-pf@FreeBSD.ORG  Mon Jun  4 11:52:06 2012
Return-Path: <owner-freebsd-pf@FreeBSD.ORG>
Delivered-To: freebsd-pf@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id B109B106564A;
	Mon,  4 Jun 2012 11:52:06 +0000 (UTC)
	(envelope-from Joerg.Pulz@frm2.tum.de)
Received: from mailhost.frm2.tum.de (mailhost.frm2.tum.de [129.187.179.12])
	by mx1.freebsd.org (Postfix) with ESMTP id 3CDE88FC0A;
	Mon,  4 Jun 2012 11:52:06 +0000 (UTC)
Received: from mailhost.frm2.tum.de (localhost [127.0.0.1])
	by mailhost.frm2.tum.de (8.14.4/8.14.4) with ESMTP id q54BooOF065328;
	Mon, 4 Jun 2012 13:50:50 +0200 (CEST)
	(envelope-from Joerg.Pulz@frm2.tum.de)
X-Virus-Scanned: at mailhost.frm2.tum.de
Received: from hades.admin.frm2 (hades.admin.frm2 [172.25.1.10])
	(authenticated bits=0)
	by mailhost.frm2.tum.de (8.14.4/8.14.4) with ESMTP id q54Bonf1065325
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);
	Mon, 4 Jun 2012 13:50:49 +0200 (CEST)
	(envelope-from Joerg.Pulz@frm2.tum.de)
Date: Mon, 4 Jun 2012 13:50:46 +0200 (CEST)
From: Joerg Pulz <Joerg.Pulz@frm2.tum.de>
To: Daniel Hartmeier <daniel@benzedrine.cx>
In-Reply-To: <20120604102544.GC13069@insomnia.benzedrine.cx>
Message-ID: <alpine.BSF.2.00.1206041346570.89783@unqrf.nqzva.sez2>
References: <201205271830.q4RIU9fA039893@freefall.freebsd.org>
	<20120529064910.GA12508@insomnia.benzedrine.cx>
	<alpine.BSF.2.00.1206011015290.89783@unqrf.nqzva.sez2>
	<20120604065344.GA13069@insomnia.benzedrine.cx>
	<20120604100829.GB13069@insomnia.benzedrine.cx>
	<20120604102544.GC13069@insomnia.benzedrine.cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.6
	(mailhost.frm2.tum.de [129.187.179.12]);
	Mon, 04 Jun 2012 13:50:49 +0200 (CEST)
Cc: bug-followup@freebsd.org, freebsd-pf@freebsd.org
Subject: Re: kern/168190: [pf] panic when using pf and route-to (maybe: bad
 fragment handling?)
X-BeenThere: freebsd-pf@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Technical discussion and general questions about packet filter
	\(pf\)" <freebsd-pf.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-pf>,
	<mailto:freebsd-pf-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-pf>
List-Post: <mailto:freebsd-pf@freebsd.org>
List-Help: <mailto:freebsd-pf-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-pf>,
	<mailto:freebsd-pf-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 04 Jun 2012 11:52:06 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Mon, 4 Jun 2012, Daniel Hartmeier wrote:

> Here's a patch that directly tests this theory.
>
> If correct, it will replace the panics with simple log messages that
> show when ipfilter left an m_len==0 mbuf.

Daniel,

thanks for all your help and the detailed informations.
The system is now running with your latest patches.
I was unable to reproduce the panics with netstat(1). Will take a look at 
dnet later.

I will keep you informed about new panics or log messages out of 
fr_check_wrapper().

Kind regards
Joerg

- -- 
The beginning is the most important part of the work.
 				-Plato
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)

iD8DBQFPzKEZSPOsGF+KA+MRAufHAKCJO7tHOUr1tcHEzxarTkQaGdnZfgCguqOP
1eFhcJJ5y8KSc0jxK25TIX8=
=3EA1
-----END PGP SIGNATURE-----