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 3/3] l2tp: remove references to modprobe in documentation
Date: Wed, 23 Sep 2015 21:33:36 -0700 [thread overview]
Message-ID: <20150924043503.713401180@networkplumber.org> (raw)
In-Reply-To: 20150924043333.231895827@networkplumber.org
[-- Attachment #1: l2tp-doc-modprobe.patch --]
[-- Type: text/plain, Size: 1018 bytes --]
No longer need explicit modprobe's and update to use ip instead
of deprecated ifconfig command.
Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
--- a/Documentation/networking/l2tp.txt 2015-05-21 15:13:01.421115881 -0700
+++ b/Documentation/networking/l2tp.txt 2015-09-07 12:18:07.672921513 -0700
@@ -213,15 +213,12 @@ To create an L2TPv3 ethernet pseudowire
and peer 192.168.1.2, using IP addresses 10.5.1.1 and 10.5.1.2 for the
tunnel endpoints:-
-# modprobe l2tp_eth
-# modprobe l2tp_netlink
-
# ip l2tp add tunnel tunnel_id 1 peer_tunnel_id 1 udp_sport 5000 \
udp_dport 5000 encap udp local 192.168.1.1 remote 192.168.1.2
# ip l2tp add session tunnel_id 1 session_id 1 peer_session_id 1
-# ifconfig -a
+# ip -s -d show dev l2tpeth0
# ip addr add 10.5.1.2/32 peer 10.5.1.1/32 dev l2tpeth0
-# ifconfig l2tpeth0 up
+# ip li set dev l2tpeth0 up
Choose IP addresses to be the address of a local IP interface and that
of the remote system. The IP addresses of the l2tpeth0 interface can be
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 ` [PATCH net-next 2/3] l2tp: auto load IP modules Stephen Hemminger
2015-09-24 4:33 ` Stephen Hemminger [this message]
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=20150924043503.713401180@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.