From: Michael Richardson <mcr@sandelman.ca>
To: linux-ppp@vger.kernel.org
Subject: Re: PPP connection corruption with Windows client, MPPE, and RDP
Date: Thu, 09 Oct 2014 14:20:04 +0000 [thread overview]
Message-ID: <16672.1412864404@sandelman.ca> (raw)
In-Reply-To: <CALas-ij41eAabeTrq+VVPoBc2eZwnPyj0vdKPDBvWKQ5LU0NPQ@mail.gmail.com>
Francesco Pretto <ceztko@gmail.com> wrote:
>> I suspect that RDP triggers it with a full-sized TCP packet.
> [...]
>> Do you have appropriate patches/things-enabled, so that the
>> esp/l2tp/ppp packets all stay in the kernel? If not, then you might
>> also get some debug from xl2tp.
>>
> I am not sure what esp is. PPP and MPPE are in the kernel. xl2tpd log
ESP is IPsec.
>> MPPE and IPsec are not related. AFAIK, MPPE provides for encryption
>> within PPP. you would be double encrypting.
> Yes, I knew. In fact I was more than satisfied with the reliability I
> get with "nomppe". But maybe MS-CHAP v2 use MPPE for authentication
> encryption? I don't know.
No.
>> Does other traffic continue to function? Is one end Windows?
> No, other traffic stops as well. VPN traffic is Windows-Windows.
> ipsec-ppp-l2tp endpoints are Windows-Linux.
Do you continue to see raw packets transmitted in both directions, if you
tcpdump the wire? I'm wondering if one end is broken and does not transmit,
or if one is broken, and receives incorrectly.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
prev parent reply other threads:[~2014-10-09 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 21:16 PPP connection corruption with Windows client, MPPE, and RDP Francesco Pretto
2014-10-08 22:53 ` Michael Richardson
2014-10-09 0:10 ` Francesco Pretto
2014-10-09 14:20 ` Michael Richardson [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=16672.1412864404@sandelman.ca \
--to=mcr@sandelman.ca \
--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 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.