From: Stephen Hemminger <shemminger@vyatta.com>
To: James Chapman <jchapman@katalix.com>
Cc: netdev@vger.kernel.org, Chris Elston <celston@katalix.com>
Subject: Re: [PATCH 1/2] iproute2: allow IPv6 addresses for l2tp local and remote parameters
Date: Wed, 25 Apr 2012 13:13:11 -0700 [thread overview]
Message-ID: <20120425131311.0de3b94f@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1334921383-32109-2-git-send-email-jchapman@katalix.com>
On Fri, 20 Apr 2012 12:29:42 +0100
James Chapman <jchapman@katalix.com> wrote:
> From: Chris Elston <celston@katalix.com>
>
> Adds support for parsing IPv6 addresses to the parameters local and
> remote in the l2tp commands. Requires netlink attributes L2TP_ATTR_IP6_SADDR
> and L2TP_ATTR_IP6_DADDR, added in a required kernel patch already submitted
> to netdev.
>
> Also enables printing of IPv6 addresses returned by the L2TP_CMD_TUNNEL_GET
> request.
>
> Signed-off-by: Chris Elston <celston@katalix.com>
> Signed-off-by: James Chapman <jchapman@katalix.com>
Accepted.
next prev parent reply other threads:[~2012-04-25 20:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 11:29 [PATCH 0/2] iproute2: add support for L2TP over IPv6, add manpage James Chapman
2012-04-20 11:29 ` [PATCH 1/2] iproute2: allow IPv6 addresses for l2tp local and remote parameters James Chapman
2012-04-25 20:13 ` Stephen Hemminger [this message]
2012-04-26 8:32 ` James Chapman
2012-04-26 15:11 ` Stephen Hemminger
2012-04-20 11:29 ` [PATCH 2/2] iproute2: add ip-l2tp man page James Chapman
2012-04-25 20:11 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2012-05-01 14:25 [PATCH 0/2] iproute2: add support for L2TP over IPv6, add manpage James Chapman
2012-05-01 14:25 ` [PATCH 1/2] iproute2: allow IPv6 addresses for l2tp local and remote parameters James Chapman
2012-05-22 21:26 ` Stephen Hemminger
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=20120425131311.0de3b94f@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=celston@katalix.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;
as well as URLs for NNTP newsgroup(s).