From: Stephen Hemminger <shemminger@vyatta.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: James Chapman <jchapman@katalix.com>, netdev@vger.kernel.org
Subject: Re: iproute2: l2tp support
Date: Fri, 20 Jan 2012 11:06:04 -0800 [thread overview]
Message-ID: <20120120110604.1101991b@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20111229094214.238a1b8f@nehalam.linuxnetplumber.net>
On Thu, 29 Dec 2011 09:42:14 -0800
Stephen Hemminger <shemminger@vyatta.com> wrote:
> I updated the latest iproute2 in git to include support for L2TP.
> It is based on James's code but instead of using libnl, it uses netlink
> directly (like I asked when rejecting the original patch).
>
> In order to make netlink code in iproute2 cleaner, several libnetlink
> have been updated.
> * unused junk argument to rtnl_dump_filter and rtnl_talk have
> been removed.
> * addattr_xx functions for building attributes added.
> * rta_getattr_XXX inline functions for the common case of
> looking at basic type attributes
>
> This will show up in 3.2 version of iproute2 which is ready and
> waiting for kernel release.
The addition of l2tp broke the common syntax of 'ip l' since it would
match ip l2tp rather than ip link.
Just added the following patch:
commit 5aa08f6bf4107f8aec43c0678466a314dbd0d054
Author: Stephen Hemminger <shemminger@vyatta.com>
Date: Fri Jan 20 08:16:02 2012 -0800
ip: make 'ip l' be 'ip link'
Restore compatiablity for those lazy typists.
diff --git a/ip/ip.c b/ip/ip.c
index 7b4bacb..20dc3b5 100644
--- a/ip/ip.c
+++ b/ip/ip.c
@@ -72,8 +72,8 @@ static const struct cmd {
{ "neighbour", do_ipneigh },
{ "ntable", do_ipntable },
{ "ntbl", do_ipntable },
- { "l2tp", do_ipl2tp },
{ "link", do_iplink },
+ { "l2tp", do_ipl2tp },
{ "tunnel", do_iptunnel },
{ "tunl", do_iptunnel },
{ "tuntap", do_iptuntap },
prev parent reply other threads:[~2012-01-20 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 17:42 iproute2: l2tp support Stephen Hemminger
2012-01-20 19:06 ` Stephen Hemminger [this message]
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=20120120110604.1101991b@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--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