From: Stephen Hemminger <stephen@networkplumber•org>
To: jchapman@katalix•com, davem@davemloft•net
Cc: netdev@vger•kernel.org, Stephen Hemminger <stephen@networkplumber•org>
Subject: [PATCH net-next 2/3] l2tp: auto load IP modules
Date: Wed, 23 Sep 2015 21:33:35 -0700 [thread overview]
Message-ID: <20150924043502.352796402@networkplumber.org> (raw)
In-Reply-To: 20150924043333.231895827@networkplumber.org
[-- Attachment #1: l2tp-ip-alias.patch --]
[-- Type: text/plain, Size: 813 bytes --]
When creating a IP encapsulated tunnel the necessary l2tp module
should be loaded. It already works for UDP encapsulation, it just
doesn't work for direct IP encap.
Signed-off-by: Stephen Hemminger <stephen@networkplumber•org>
--- a/net/l2tp/l2tp_ip.c 2015-09-23 21:24:08.644656533 -0700
+++ b/net/l2tp/l2tp_ip.c 2015-09-23 21:24:08.640656514 -0700
@@ -655,3 +655,4 @@ MODULE_VERSION("1.0");
* enums
*/
MODULE_ALIAS_NET_PF_PROTO_TYPE(PF_INET, 2, IPPROTO_L2TP);
+MODULE_ALIAS_NET_PF_PROTO(PF_INET, IPPROTO_L2TP);
--- a/net/l2tp/l2tp_ip6.c 2015-09-23 21:24:08.644656533 -0700
+++ b/net/l2tp/l2tp_ip6.c 2015-09-23 21:24:08.640656514 -0700
@@ -801,3 +801,4 @@ MODULE_VERSION("1.0");
* enums
*/
MODULE_ALIAS_NET_PF_PROTO_TYPE(PF_INET6, 2, IPPROTO_L2TP);
+MODULE_ALIAS_NET_PF_PROTO(PF_INET6, IPPROTO_L2TP);
next prev parent reply other threads:[~2015-09-24 4:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 4:33 [PATCH net-next 0/3] l2tp: module autoloading Stephen Hemminger
2015-09-24 4:33 ` [PATCH net-next 1/3] l2tp: auto load type modules Stephen Hemminger
2015-09-24 4:33 ` Stephen Hemminger [this message]
2015-09-24 4:33 ` [PATCH net-next 3/3] l2tp: remove references to modprobe in documentation Stephen Hemminger
2015-09-24 6:45 ` [PATCH net-next 0/3] l2tp: module autoloading James Chapman
2015-09-25 19:28 ` David Miller
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=20150924043502.352796402@networkplumber.org \
--to=stephen@networkplumber$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=jchapman@katalix$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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