From: Ben Hutchings <bhutchings@solarflare.com>
To: James Chapman <jchapman@katalix.com>
Cc: Jeff Loughridge <jeffl@alumni.duke.edu>, <netdev@vger.kernel.org>
Subject: Re: ip l2tp - suspected defect using IPv6 local/remote addresses
Date: Thu, 12 Sep 2013 14:19:01 +0100 [thread overview]
Message-ID: <1378991941.1531.5.camel@bwh-desktop.uk.level5networks.com> (raw)
In-Reply-To: <CAEwTi7Qo8=X=v51_1y3JMQnbG3xBQYRb9YRePFh6KfYmb_Y0-g@mail.gmail.com>
On Thu, 2013-09-12 at 11:20 +0100, James Chapman wrote:
> On 11 September 2013 19:52, Jeff Loughridge <jeffl@alumni.duke.edu> wrote:
> >
> > Using IPv6 address as L2TPv3 endpoints doesn't seem to work in
> > iproute2 3.11. I see a cosmetic defect in the output of 'ip l2tp show
> > tunnel'. In addition, I can't get tunnels to function with UDP or IP
> > encapsulation.
> >
> > root@debian:~# ip l2tp add tunnel tunnel_id 3000 peer_tunnel_id 4000
> > encap udp local a::1 remote a::2 udp_sport 5000 udp_dport 6000
> > root@debian:~# ip l2tp add session tunnel_id 3000 session_id 1000
> > peer_session_id 2000
> > root@debian:~# ip l2tp show tunnel
> > Tunnel 3000, encap UDP
> > From 127.0.0.1 to 127.0.0.1
> > Peer tunnel 4000
> > UDP source / dest ports: 5000/6000
> > root@debian:~#
>
> You'll need a 3.5 or later kernel for L2TP over IPv6. I see you are
> using 3.2. Are you using a version of iproute2 which is not matched to
> your kernel?
[...]
The iproute2 version number only indicates which kernel features it
supports; it is supposed to be backward-compatible. And it really
should not silently fail like this, although this may well be a bug in
the API that can't be fixed in userland...
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2013-09-12 15:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-11 18:52 ip l2tp - suspected defect using IPv6 local/remote addresses Jeff Loughridge
2013-09-12 10:20 ` James Chapman
2013-09-12 13:19 ` Ben Hutchings [this message]
2013-09-13 0:46 ` Jeff Loughridge
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=1378991941.1531.5.camel@bwh-desktop.uk.level5networks.com \
--to=bhutchings@solarflare.com \
--cc=jchapman@katalix.com \
--cc=jeffl@alumni.duke.edu \
--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