From: Eric Dumazet <eric.dumazet@gmail.com>
To: jpo234 <pommnitz@yahoo.com>
Cc: netdev@vger.kernel.org, James Chapman <jchapman@katalix.com>
Subject: Re: l2tpv3 support not yet in iproute2?
Date: Mon, 27 Sep 2010 18:23:16 +0200 [thread overview]
Message-ID: <1285604596.3017.80.camel@edumazet-laptop> (raw)
In-Reply-To: <loom.20100927T170521-559@post.gmane.org>
Le lundi 27 septembre 2010 à 15:22 +0000, jpo234 a écrit :
> Hello all,
> some time ago James Chapman sent patches that add L2TPv3 support to iproute2:
> http://kerneltrap.org/mailarchive/linux-netdev/2010/3/18/6272266/thread
> While the kernel support arrived in 2.6.35 the user space configuration support
> still seems to be missing:
> iproute2-2.6.35$ find . -type f -iname "*.c" | xargs fgrep -i l2tp
> doesn't find anything.
>
> Can somebody clarify the current situation?
Hmm, this reminds me l2tp locking is buggy and not yet fixed.
http://kerneltrap.org/mailarchive/linux-netdev/2010/4/20/6275106
James, any chance you could fix the locking ?
next prev parent reply other threads:[~2010-09-27 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-27 15:22 l2tpv3 support not yet in iproute2? jpo234
2010-09-27 16:23 ` Eric Dumazet [this message]
2010-09-27 17:26 ` James Chapman
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=1285604596.3017.80.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=jchapman@katalix.com \
--cc=netdev@vger.kernel.org \
--cc=pommnitz@yahoo.com \
/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