From owner-svn-doc-all@freebsd.org Tue Apr 7 10:02:51 2020 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 300CD2B1771; Tue, 7 Apr 2020 10:02:51 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48xNJC0KTsz4P8t; Tue, 7 Apr 2020 10:02:51 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id DDD9A7EB8; Tue, 7 Apr 2020 10:02:50 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id 037A2o9Y005018; Tue, 7 Apr 2020 10:02:50 GMT (envelope-from ale@FreeBSD.org) Received: (from ale@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id 037A2oVL005017; Tue, 7 Apr 2020 10:02:50 GMT (envelope-from ale@FreeBSD.org) Message-Id: <202004071002.037A2oVL005017@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ale set sender to ale@FreeBSD.org using -f From: Alex Dupre Date: Tue, 7 Apr 2020 10:02:50 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r54041 - head/en_US.ISO8859-1/books/handbook/firewalls X-SVN-Group: doc-head X-SVN-Commit-Author: ale X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/handbook/firewalls X-SVN-Commit-Revision: 54041 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Apr 2020 10:02:51 -0000 Author: ale Date: Tue Apr 7 10:02:50 2020 New Revision: 54041 URL: https://svnweb.freebsd.org/changeset/doc/54041 Log: Fix typo in IPFW page and s/reassamble/reassemble/g PR: 245396 Submitted by: wout@canodus.be Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Mon Apr 6 17:10:38 2020 (r54040) +++ head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Tue Apr 7 10:02:50 2020 (r54041) @@ -2256,18 +2256,18 @@ ipfw -q nat 1 config if $pif same_ports unreg_o The inbound NAT rule is inserted after the two rules which allow all traffic on the trusted and loopback interfaces and after the - reassamble rule but before the + reassemble rule but before the check-state rule. It is important that the rule number selected for this NAT rule, in this example 100, is higher than the first three rules and lower than the check-state rule. Furthermore, because of the behavior of in-kernel - NAT it is advised to place a reassamble + NAT it is advised to place a reassemble rule just before the first NAT rule and after the rules that allow traffic on trusted interface. Normally, IP fragmentation should not happen, but when dealing with IPSEC/ESP/GRE - tunneling traffic it might and the reassmabling of fragments + tunneling traffic it might and the reassembling of fragments is necessary before handing the complete packet over to the in-kernel NAT facility. @@ -2275,7 +2275,7 @@ ipfw -q nat 1 config if $pif same_ports unreg_o The reassemble rule was not needed with userland &man.natd.8; because the internal workings of the IPFW divert - action already takes care of reassambling packets before + action already takes care of reassembling packets before delivery to the socket as also stated in &man.ipfw.8;. The NAT instance and rule number used @@ -2287,7 +2287,7 @@ ipfw -q nat 1 config if $pif same_ports unreg_o $cmd 005 allow all from any to any via xl0 # exclude LAN traffic $cmd 010 allow all from any to any via lo0 # exclude loopback traffic -$cmd 099 reass all from any to any in # reassamble inbound packets +$cmd 099 reass all from any to any in # reassemble inbound packets $cmd 100 nat 1 ip from any to any in via $pif # NAT any inbound packets # Allow the packet through if it has an existing entry in the dynamic rules table $cmd 101 check-state