From owner-freebsd-pf@FreeBSD.ORG  Thu Jun 11 17:29:20 2015
Return-Path: <owner-freebsd-pf@FreeBSD.ORG>
Delivered-To: freebsd-pf@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 93299220
 for <freebsd-pf@FreeBSD.org>; Thu, 11 Jun 2015 17:29:20 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 7D53B1D4E
 for <freebsd-pf@FreeBSD.org>; Thu, 11 Jun 2015 17:29:20 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t5BHTKb2018445
 for <freebsd-pf@FreeBSD.org>; Thu, 11 Jun 2015 17:29:20 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-pf@FreeBSD.org
Subject: [Bug 200330] panic: pf_addr_cmp: unknown address family 0 when scrub
 fragment drop-ovl is used
Date: Thu, 11 Jun 2015 17:29:20 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: danilo@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: kristof@freebsd.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-200330-17777-yB27ZgvInV@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-200330-17777@https.bugs.freebsd.org/bugzilla/>
References: <bug-200330-17777@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-pf@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: "Technical discussion and general questions about packet filter
 \(pf\)" <freebsd-pf.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Thu, 11 Jun 2015 17:29:20 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=200330

--- Comment #14 from Danilo Egea Gondolfo <danilo@FreeBSD.org> ---
I was using this option in a low traffic network. The last panic happened after
some hours of uptime. Nothing special. My use case for "drop-ovl" is just
"testing", I don't need to use this option actually, I was just testing when I
discovered the problem. Does the "fragment reassemble" option do the same work?
After the last panic I've deactivated the option, I'm using it again to try to
reproduce the panic. Thanks for your work!

-- 
You are receiving this mail because:
You are on the CC list for the bug.