From: James Chapman <jchapman@katalix.com>
To: Sam Protsenko <semen.protsenko@linaro.org>
Cc: Tom Parkin <tparkin@katalix.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Sumit Semwal <sumit.semwal@linaro.org>
Subject: Re: problems with L2TP
Date: Thu, 09 Jul 2015 11:33:41 +0100 [thread overview]
Message-ID: <559E4E05.3090902@katalix.com> (raw)
In-Reply-To: <CAKaJLVvft6HjFH+qAr4taD4bEis4SCtTSbvmDYuGz9=1boQvJA@mail.gmail.com>
On 09/07/15 10:16, Sam Protsenko wrote:
>> Tom and I discussed this and we're not clear what you are running. Have
>> you changed create_pppox() in mtpd with the code fragment from your
>> original mail?
> Here is the commit for mtpd where I'm changing Android L2TP
> implementation to mainline implementation:
> http://git.linaro.org/people/semen.protsenko/mtpd.git/blobdiff/27a25e28b7c84d3f49c50a3e7b1fc3a46ac4ff51..01265f20617e7f3ca041e55dbf557912a0ecebd5:/l2tp_up.c
>
>> Are you sure that your modified mtpd gets the correct
>> local/remote tunnel-id and session-id to make its connect() call?
> Judging from xl2tpd and mtpd logs, they are actually different. Seems
> like this is actual issue. But I still didn't figured why it's
> happening.
> As I understand, mtpd should have the same values for remote
> tunnel-id/session-id as xl2tpd has for local ones, but it's not the
> case for my code.
That's correct. This is a control protocol implementation issue, not a
kernel issue.
--
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development
prev parent reply other threads:[~2015-07-09 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 13:49 problems with L2TP Sam Protsenko
2015-07-03 15:41 ` Tom Parkin
2015-07-06 16:16 ` Sam Protsenko
2015-07-08 10:02 ` James Chapman
2015-07-09 9:16 ` Sam Protsenko
2015-07-09 10:33 ` James Chapman [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=559E4E05.3090902@katalix.com \
--to=jchapman@katalix.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=semen.protsenko@linaro.org \
--cc=sumit.semwal@linaro.org \
--cc=tparkin@katalix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.