From owner-freebsd-ipfw@freebsd.org  Tue Nov 15 05:41:15 2016
Return-Path: <owner-freebsd-ipfw@freebsd.org>
Delivered-To: freebsd-ipfw@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id DA6E5C41CBD
 for <freebsd-ipfw@mailman.ysv.freebsd.org>;
 Tue, 15 Nov 2016 05:41:15 +0000 (UTC)
 (envelope-from smithi@nimnet.asn.au)
Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 57C6D188A
 for <freebsd-ipfw@freebsd.org>; Tue, 15 Nov 2016 05:41:14 +0000 (UTC)
 (envelope-from smithi@nimnet.asn.au)
Received: from localhost (localhost [127.0.0.1])
 by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id uAF5enlS082365;
 Tue, 15 Nov 2016 16:40:50 +1100 (EST)
 (envelope-from smithi@nimnet.asn.au)
Date: Tue, 15 Nov 2016 16:40:49 +1100 (EST)
From: Ian Smith <smithi@nimnet.asn.au>
To: wo0x <wo0x@c-base.org>
cc: freebsd-ipfw@freebsd.org
Subject: Re: [Bug 214419] ipfw coredump when try to add rule with table of
 IPv6 addresses
In-Reply-To: <CAPTxRTfsmrZobxUBGzh_gHPLCdfyYr5N94dOJde6va4hWmmw9Q@mail.gmail.com>
Message-ID: <20161115163121.D2342@sola.nimnet.asn.au>
References: <CAPTxRTfsmrZobxUBGzh_gHPLCdfyYr5N94dOJde6va4hWmmw9Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-BeenThere: freebsd-ipfw@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: IPFW Technical Discussions <freebsd-ipfw.freebsd.org>
List-Unsubscribe: <https://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: <https://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
 <mailto:freebsd-ipfw-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Nov 2016 05:41:16 -0000

On Mon, 14 Nov 2016 13:43:15 +0000, wo0x wrote:
 > Hi there,
 > 
 >    I just subscribed to this list due to the subjected bug--and I am quite
 > happy to find this trouble has yet been noted by others:
 > 
 > # fwcmd=/sbin/ipfw
 > # ${fwcmd} -f table dnssrv flush
 > # ${fwcmd}    table dnssrv create type addr
 > # ${fwcmd}    table dnssrv add 2a02:e00:fffd:139::9
 > added: 2a02:e00:fffd:139::9/128 0
 > # ${fwcmd}    table dnssrv add 2001:41D0:A:0028::1
 > added: 2001:41d0:a:28::1/128 0
 > # ${fwcmd}    table dnssrv add 2001:4860:4860::8844
 > added: 2001:4860:4860::8844/128 0
 > # ${fwcmd} add 20020 allow ip6 from any to "table(dnssrv)" out via gif0
 > setup keep-state
 > Segmentation fault (core dumped)
 > # uname -v
 > FreeBSD 11.0-STABLE #0 r308635: Mon Nov 14 08:55:15 UTC 2016
 > root@tunnel.example.vnet:/usr/obj/usr/src/sys/CUSTOM
 > 
 > When doing "ipfw list" all rules are with numbers lower to 20020 are listed
 > correctly. Then again SegFault is notified and processing of further rules
 > is interrupted, more precisely: The mandatory "65535 deny ip from any to
 > any" is also missing.

Since 'setup' only applies to TCP flows, I'm wondering if you may get a 
different result if you used 'allow tcp ...' instead of 'allow ip6 ...'?

cheers, Ian  (probably wildly guessing wrong ..)