From owner-freebsd-ipfw@freebsd.org Fri May 25 13:42:54 2018 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 057C3EB199F for ; Fri, 25 May 2018 13:42:54 +0000 (UTC) (envelope-from lantw44@gmail.com) Received: from mail-pl0-x229.google.com (mail-pl0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6C82282115; Fri, 25 May 2018 13:42:53 +0000 (UTC) (envelope-from lantw44@gmail.com) Received: by mail-pl0-x229.google.com with SMTP id 30-v6so3190143pld.13; Fri, 25 May 2018 06:42:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:cc:date:in-reply-to:references :mime-version:content-transfer-encoding; bh=95qi+BUujhDruN567DGzuHva/ghz34wdSomJn3N8s+0=; b=Yz/vz7NdM6hPktlgmAFr8HvACVypKp7E7YGn0oI84JiWw4zufO6VJHrwSXy0CbYsee tSjjmDe04fPBUWKaZDTlMs9j/Axe4UUMLwxMfK/NyqBHze71PMT0f+cKW+wOan+EQbhi oIMWAK1GwET/NZwwqFjEFOlZv2N+b2m5ltttH6v6Fszfw4sBDsVdUFkd+yeBRIeMDM/U ChZfsFwEx3HGm1Fk6b7cfyPA5LQiVHIg1YzvaNZ7D3sEq/tK0+kGX5ogzIouoF4oMf3G NCd3QqvoQcT/lXu8EyHsj5UXiUPsgy6JFv82HcnHsy0I+O9oQtHqsZO2sbZF5fIO+UZ6 LR3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:mime-version:content-transfer-encoding; bh=95qi+BUujhDruN567DGzuHva/ghz34wdSomJn3N8s+0=; b=AnQ7y+VWWPfJf472PGZCh7vmG/KcI5rQDMH4C6Dq3vMzn85AgJliJeXbYKj7gH1znv lNGEfxKM6C3sp/aiWVgDiz+ndg6lsNNLMLIO4HCxfZug/Xt6HzPCi74T/wDAJd/9TU4n G8UtqFMuAOHXgdPsZOMfvhWt/gaxvggKOxIxgOTeQaK1q2qP4dZuFi7YVWEPNaGV0s+e w7JaMbiEWeEO/OR32h+NHSa4Ar/ZTZbOI47wumYhsOjvEu/ojfqlsxfdxKkqL6M7H5Lo 1z7JCPUsHKeEB5PawddTCDw1iRp21VBQ83zOgBueuVV1lvNq/CB8cxBdG0RMY47gavH3 ow6Q== X-Gm-Message-State: ALKqPwe637u1De3L0dPFWCj0lGPFLBza2hofum08POGLYMiUQaUEiJfW lny167zfGaDT9TdeF2F/YfByyXM9 X-Google-Smtp-Source: AB8JxZp7M5NMqP4pLJ7QTTXFpGkWqOF+xUOZIhtAafacOscyzoEre0TjAfwdoM1TYod3UrRb+43lRA== X-Received: by 2002:a17:902:aa03:: with SMTP id be3-v6mr2695287plb.61.1527255772387; Fri, 25 May 2018 06:42:52 -0700 (PDT) Received: from [192.168.1.92] (123-204-232-139.adsl.dynamic.seed.net.tw. [123.204.232.139]) by smtp.gmail.com with ESMTPSA id 65-v6sm47840385pgj.22.2018.05.25.06.42.50 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Fri, 25 May 2018 06:42:51 -0700 (PDT) Message-ID: <001c64d4ba91726229d1139fd1331f09e80d0c68.camel@gmail.com> Subject: Re: Missing sysctl net.inet.ip.fw.dyn_keep_states on FreeBSD 11.2 From: =?Big5?Q?=C2=C5=AE=BC=DE=B3?= To: "Rodney W. Grimes" Cc: ae@freebsd.org, freebsd-ipfw@freebsd.org Date: Fri, 25 May 2018 21:42:14 +0800 In-Reply-To: <201805241518.w4OFIm64041005@pdx.rh.CN85.dnsmgr.net> References: <201805241518.w4OFIm64041005@pdx.rh.CN85.dnsmgr.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.29.3 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Fri, 25 May 2018 13:52:35 +0000 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2018 13:42:54 -0000 於 星期四，2018-05-24 於 08:18 -0700，Rodney W. Grimes 提到： > > Hello, > > > > I upgraded my desktop system from FreeBSD 11.2-BETA1 last week, and I found > > the > > sysctl 'net.inet.ip.fw.dyn_keep_states' got removed. I upgraded it again to > > FreeBSD 11.2-BETA2 today, and I still could not find it. Currently I rely on > > both 'net.inet.ip.fw.default_to_accept=1' and > > 'net.inet.ip.fw.dyn_keep_states=1' > > to be able to reload firewall rules with 'service ipfw restart' without > > breaking > > existing TCP connections. As this sysctl variable is still mentioned in > > ipfw(8) > > man page, will it be brought back in future versions, or there will be an > > alternative solution for firewall rules reload? > > As a follow up to this discusion, there has been a merge of code > into the stable/11 branch that should be in the 11.2-BETA3 build > that corrects this missing sysctl, It is nice to know this! > could you please test this > build when it comes out and provide feed back to how it works > for you. Yes, I will test it. I already tested it on 11.2-BETA2 by manually applying patches from r333986 and 334039, and it worked fine for me. > > Thanks,