From: Guillaume Nault <g.nault@alphalink.fr>
To: Sorin Manolache <sorinm@gmail.com>
Cc: netdev@vger.kernel.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: Fw: [Bug 111771] New: deadlock in ppp/l2tp
Date: Thu, 4 Feb 2016 14:05:10 +0100 [thread overview]
Message-ID: <20160204130510.GD1267@alphalink.fr> (raw)
In-Reply-To: <56B2AA40.5090601@gmail.com>
On Thu, Feb 04, 2016 at 02:32:48AM +0100, Sorin Manolache wrote:
> On 2016-02-03 18:14, Guillaume Nault wrote:
> >
> >Sorin, it seems like one of your L2TP tunnels is routed to one of its upper PPP
> >devices. Most likely, the peer address of the PPP device is also the address of
> >the remote L2TP tunnel endpoint. So L2TP packets are sent back to the upper PPP
> >device, instead of leaving through the physical interface.
>
> Thank you. You are right. There's a host route to the peer over the ppp0
> interface in the routing table. I don't know how it gets there. I've checked
> the source code of pppd and no such route is added for kernels newer than
> 2.1.16. I've grepped /etc for "route" in order to detect a "post-up" script
> that would add that route. Nothing. I've double-checked by executing strace
> on xl2tpd and its children (i.e. pppd and the initialisation scripts) and I
> couldn't find any ioctl SIOCADDRT. So it's a total mystery for me where that
> route comes from. Could it come from the kernel?
>
If that's a /32 IPv4 route to the peer address of the PPP link and has
the "proto kernel" attribute, then yes, that's most likely the one
generated by the kernel.
prev parent reply other threads:[~2016-02-04 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-03 0:04 Fw: [Bug 111771] New: deadlock in ppp/l2tp Stephen Hemminger
2016-02-03 17:14 ` Guillaume Nault
2016-02-04 1:32 ` Sorin Manolache
2016-02-04 13:05 ` Guillaume Nault [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=20160204130510.GD1267@alphalink.fr \
--to=g.nault@alphalink.fr \
--cc=netdev@vger.kernel.org \
--cc=sorinm@gmail.com \
--cc=stephen@networkplumber.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).