From owner-freebsd-ipfw@FreeBSD.ORG Sat Jul 2 18:24:30 2011 Return-Path: Delivered-To: freebsd-ipfw@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 142271065778; Sat, 2 Jul 2011 18:24:30 +0000 (UTC) (envelope-from dima_bsd@inbox.lv) Received: from mgw1.apollo.lv (mgw1.apollo.lv [80.232.168.216]) by mx1.freebsd.org (Postfix) with ESMTP id C60248FC17; Sat, 2 Jul 2011 18:24:29 +0000 (UTC) Received: from [46.109.212.104] (unknown [46.109.212.104]) by mgw1.apollo.lv (Postfix) with ESMTP id 3D5893DF89F; Sat, 2 Jul 2011 21:07:20 +0300 (EEST) From: Dmitriy Demidov To: ae@FreeBSD.org, freebsd-ipfw@FreeBSD.org Date: Sat, 2 Jul 2011 18:07:18 +0000 User-Agent: KMail/1.9.10 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201107021807.18663.dima_bsd@inbox.lv> X-Brightmail-Tracker: AAAAAA== Cc: Subject: Re: kern/144187: [ipfw] deadlock using multiple ipfw nat and multiple limit statements X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jul 2011 18:24:30 -0000 > Synopsis: [ipfw] deadlock using multiple ipfw nat and multiple limit > statements State-Changed-From-To: open->feedback > State-Changed-By: ae > State-Changed-When: Tue Jun 28 05:29:45 UTC 2011 > State-Changed-Why: > Can you still reproduce this on a supported release? > Or maybe you can test your rules on head/ branch? > There were some changes related to ipfw_nat. > http://www.freebsd.org/cgi/query-pr.cgi?pr=144187 Hello, I have retested this configuration on today's build of FreeBSD 9-CURRENT i386. It seems that this problem is soved now! I am unable to reproduce deadlock anymore. All is working just fine. Thanks!