From: David Fernandez <david.fernandez.work@googlemail.com>
To: linux-ppp@vger.kernel.org
Subject: Re: kernel-mode PPPoE does not seem able to work with MPPE.
Date: Tue, 24 Oct 2017 15:13:32 +0000 [thread overview]
Message-ID: <0dc6e608-f91d-1c08-9dc1-69d114efa728@googlemail.com> (raw)
In-Reply-To: <158d6529-c9ae-a991-ca47-76e558a1209c@googlemail.com>
On 24/10/17 15:17, Christoph Schulz wrote:
> Hello!
>
> David Fernandez <david.fernandez.work@googlemail.com> schrieb am Di 24
> Okt 2017 10:52:46 CEST:
>
>> Hi there,
>>
>> I've tried to run MPPE in a PPPoE connection to my LEDE linux server.
>> The log is below.
>> [...]
>> Although it should not be needed, if I use the option require-mppe,
>> pppd complains of unrecognized option.
>
> As the sources only define (and understand) the "require-mppe" option
> iff the preprocessor symbol MPPE has been defined during compilation,
> I suspect that your (i.e. LEDE's) pppd has been compiled without MPPE
> support. You should check this first.
>
Hi Christoph,
The MPPE is defined, as I see code conditionally compiled with #ifdef
MPPE putting things in the log, like:
Feb 2 12:05:22 LEDE pppd[1580]: MPPE 128-bit stateful compression enabled
AFAICS the downloaded 2.4.7 sources in pppd/ccp.c define and understand
the option mppe or +mppe with special arguments
no40,no56,no128,stateless,required comma separated, as per int
setmppe(char **argv) function... unless I am getting something wrong,
obviously.
These are the options defined in ccp.c:
#ifdef MPPE
{ "mppc", o_bool, &ccp_wantoptions[0].mppc,
"request MPPC compression", 1, &ccp_allowoptions[0].mppc },
{ "+mppc", o_bool, &ccp_wantoptions[0].mppc,
"request MPPC compression", 1, &ccp_allowoptions[0].mppc,
OPT_ALIAS },
{ "nomppc", o_bool, &ccp_wantoptions[0].mppc,
"don't allow MPPC compression", OPT_PRIOSUB | OPT_A2CLR,
&ccp_allowoptions[0].mppc },
{ "-mppc", o_bool, &ccp_wantoptions[0].mppc,
"don't allow MPPC compression", OPT_ALIAS | OPT_PRIOSUB | OPT_A2CLR,
&ccp_allowoptions[0].mppc },
{ "mppe", o_special, (void *)setmppe,
"request MPPE encryption" },
{ "+mppe", o_special, (void *)setmppe,
"request MPPE encryption" },
{ "nomppe", o_special_noarg, (void *)setnomppe,
"don't allow MPPE encryption" },
{ "-mppe", o_special_noarg, (void *)setnomppe,
"don't allow MPPE encryption" },
#endif /* MPPE */
These are the download definitions:
PKG_NAME:=ppp
PKG_VERSION:=2.4.7
PKG_RELEASE:\x10
PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.gz
PKG_SOURCE_URL:=https://download.samba.org/pub/ppp/
PKG_HASH:\x02e0a3dd3e4799e33103f70ec7df75348c8540966ee7c948e4ed8a42bbccfb30
>
> Regards,
>
> Christoph Schulz
>
Regards
David
next prev parent reply other threads:[~2017-10-24 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-24 8:52 kernel-mode PPPoE does not seem able to work with MPPE David Fernandez
2017-10-24 12:09 ` David Fernandez
2017-10-24 14:17 ` Christoph Schulz
2017-10-24 15:13 ` David Fernandez [this message]
2017-10-24 20:00 ` Christoph Schulz
2017-10-25 17:45 ` David Fernandez
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=0dc6e608-f91d-1c08-9dc1-69d114efa728@googlemail.com \
--to=david.fernandez.work@googlemail.com \
--cc=linux-ppp@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).