Date: Sat, 10 Sep 2022 10:58:24 GMT From: Gordon Bergling <gbe@FreeBSD.org> To: src-committers@FreeBSD.org, dev-commits-src-all@FreeBSD.org, dev-commits-src-main@FreeBSD.org Subject: git: 11bc6be152e5 - main - ipf-howto: Remove a double word Message-ID: <202209101058.28AAwOdE064169@gitrepo.freebsd.org>
next in thread | raw e-mail | index | archive | help
The branch main has been updated by gbe (doc committer): URL: https://cgit.FreeBSD.org/src/commit/?id=11bc6be152e5572e289824d381c812fe90458607 commit 11bc6be152e5572e289824d381c812fe90458607 Author: Gordon Bergling <gbe@FreeBSD.org> AuthorDate: 2022-09-10 10:56:48 +0000 Commit: Gordon Bergling <gbe@FreeBSD.org> CommitDate: 2022-09-10 10:56:48 +0000 ipf-howto: Remove a double word - s/to to/to/ MFC after: 3 days --- share/examples/ipfilter/ipf-howto.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/share/examples/ipfilter/ipf-howto.txt b/share/examples/ipfilter/ipf-howto.txt index e15ae0fb2931..ca14538f1b67 100644 --- a/share/examples/ipfilter/ipf-howto.txt +++ b/share/examples/ipfilter/ipf-howto.txt @@ -1260,7 +1260,7 @@ your firewall. keep frags keyword. With it, IPF will notice and keep track of packets that are fragmented, allowing the expected frag- -ments to to go through. Let's rewrite the 3 rules to log +ments to go through. Let's rewrite the 3 rules to log forgeries and allow fragments: pass in quick on tun0 proto tcp from any to 20.20.20.1/32 port = 23 flags S keep state keep frags
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?202209101058.28AAwOdE064169>