From owner-freebsd-ipfw@freebsd.org Fri Jun 14 19:13:19 2019 Return-Path: Delivered-To: freebsd-ipfw@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 1C97515AF438 for ; Fri, 14 Jun 2019 19:13:19 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Received: from uucp.dinoex.org (uucp.dinoex.sub.de [IPv6:2001:1440:5001:1::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "uucp.dinoex.sub.de", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 67FD775B56 for ; Fri, 14 Jun 2019 19:13:17 +0000 (UTC) (envelope-from pmc@citylink.dinoex.sub.org) Received: from uucp.dinoex.sub.de (uucp.dinoex.sub.de [194.45.71.2]) by uucp.dinoex.org (8.16.0.41/8.16.0.41) with ESMTPS id x5EJD4fu047755 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Fri, 14 Jun 2019 21:13:05 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Received: from citylink.dinoex.sub.org (uucp@localhost) by uucp.dinoex.sub.de (8.16.0.41/8.16.0.41/Submit) with UUCP id x5EJD4ep047754; Fri, 14 Jun 2019 21:13:04 +0200 (CEST) (envelope-from pmc@citylink.dinoex.sub.org) Received: from gate.oper.dinoex.org (gate-e [192.168.98.2]) by citylink.dinoex.sub.de (8.15.2/8.15.2) with ESMTP id x5EIk2Oi006335; Fri, 14 Jun 2019 20:46:02 +0200 (CEST) (envelope-from peter@gate.oper.dinoex.org) Received: from gate.oper.dinoex.org (gate-e [192.168.98.2]) by gate.oper.dinoex.org (8.15.2/8.15.2) with ESMTP id x5EIjufI006274; Fri, 14 Jun 2019 20:45:56 +0200 (CEST) (envelope-from peter@gate.oper.dinoex.org) Received: (from peter@localhost) by gate.oper.dinoex.org (8.15.2/8.15.2/Submit) id x5EIjuPA006273; Fri, 14 Jun 2019 20:45:56 +0200 (CEST) (envelope-from peter) Date: Fri, 14 Jun 2019 20:45:55 +0200 From: Peter To: Freddie Cash Cc: "freebsd-ipfw@freebsd.org" Subject: Re: ipfw: switching sets does stall the machine Message-ID: <20190614184555.GA5959@gate.oper.dinoex.org> References: <20190614153302.GA4503@gate.oper.dinoex.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.11.4 (2019-03-13) X-Milter: Spamilter (Reciever: uucp.dinoex.sub.de; Sender-ip: 194.45.71.2; Sender-helo: uucp.dinoex.sub.de; ) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.2 (uucp.dinoex.org [194.45.71.2]); Fri, 14 Jun 2019 21:13:08 +0200 (CEST) X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jun 2019 19:13:19 -0000 On Fri, Jun 14, 2019 at 10:21:52AM -0700, Freddie Cash wrote: ! > Details: ! > Machine : i386 ! > OS : FreeBSD 11.2-RELEASE-p10 ! > Command : ipfw set disable 1 2 3 4 5 6 7 8 9 10 11 12 13 14 enable 16 ! > 17 18 19 20 21 22 23 24 25 26 27 28 29 ! > ! ! Can't speak to this specific lockup, but I'm curious to know if it works ! when you enable first, then disable (it's how we've used sets here at work). Tried that already, it doesn't make a difference. And since the operation is said to be atomically, it should not make a difference. But now I have an idea what might be the actual issue. One more try for proof, and I send this message out first as otherwise it will be lost...