From: "Lennart Sorensen" <lsorense@csclub.uwaterloo.ca>
To: Len Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: netdev@vger.kernel.org, James Chapman <jchapman@katalix.com>
Subject: [PATCH V2] Fix misspelling of defrag in ip-l2tp.8
Date: Wed, 25 Feb 2015 13:59:42 -0500 [thread overview]
Message-ID: <20150225185942.GA22050@csclub.uwaterloo.ca> (raw)
Somehow defrag was spelled degrag everywhere it occoured in the ip-l2tp
man page. nf_degrag_ipv4 seemed like an odd name for the module and
couldn't be located, so better fix the man page.
Signed-off-by: Len Sorensen <lsorense@csclub.uwaterloo.ca>
---
man/man8/ip-l2tp.8 | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/man/man8/ip-l2tp.8 b/man/man8/ip-l2tp.8
index 2efda9f..1738035 100644
--- a/man/man8/ip-l2tp.8
+++ b/man/man8/ip-l2tp.8
@@ -356,16 +356,16 @@ the recipient expects to receive ethernet frames exactly as
transmitted. In such cases, it is important that frames leaving the
tunnel are reassembled back into a single frame before being
forwarded on. To do so, enable netfilter connection tracking
-(conntrack) or manually load the Linux netfilter degrag modules at
+(conntrack) or manually load the Linux netfilter defrag modules at
each tunnel endpoint.
.PP
.nf
-site-A:# modprobe nf_degrag_ipv4
+site-A:# modprobe nf_defrag_ipv4
-site-B:# modprobe nf_degrag_ipv4
+site-B:# modprobe nf_defrag_ipv4
.fi
.PP
-If L2TP is being used over IPv6, use the IPv6 degrag module.
+If L2TP is being used over IPv6, use the IPv6 defrag module.
.SH INTEROPERABILITY
.PP
Unmanaged (static) L2TPv3 tunnels are supported by some network
--
1.7.10.4
next reply other threads:[~2015-02-25 18:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-25 18:59 Lennart Sorensen [this message]
2015-02-25 22:43 ` [PATCH V2] Fix misspelling of defrag in ip-l2tp.8 Jeremiah Mahler
2015-02-26 16:28 ` Lennart Sorensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150225185942.GA22050@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=jchapman@katalix.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox