linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: PPP compression
Date: Mon, 22 Dec 2014 19:09:08 +0000	[thread overview]
Message-ID: <54986C54.5030707@workingcode.com> (raw)
In-Reply-To: <3b4526880d737ed5094d632636e6fef8@great.ufc.br>

On 12/22/14 13:06, arthurpaulino wrote:
> First, I appreciate all your support.
> 
> I tried to convert from .pcap to .pppdump and use pppdump (with -p and -d)
> to decompress the data.
> But again, the output contains the same data as the compressed packets.
> The files are attached.

Looking at the traces provided, it seems to be just a partial trace, so
there's no way anyone could decode it.

It's important to know that data compression is a stateful operation.
It retains an LZ string dictionary between packets.  As a result, if you
don't have all of the data from the very beginning of the connection,
any attempt to decode it is going to go terribly awry.

For that reason, pppdump won't attempt to decode unless it sees the
initial handshake and CCP negotiation.

That's why I said in the first place that the *SIMPLEST* option to debug
the higher-level data is to disable compression.  Any system built on
non-proprietary standards should work fine with data compression disabled.

> I have some questions:
> 
> 1 - I tried to use pppd with the recording option (pppd record
> output.pppdump), but all it did was print
> "~�}#�!}!}!} }4}"}&} } } } }%}&v��}<}'}"}(}">*~" over and over on the
> terminal. Also, no output file was saved. Am I doing something wrong?

That result indicates that no tty was provided for pppd to use, so it's
falling back to the default -- which is your current tty.  I don't know
what specific options you were using or what issues there are on your
system, so it's hard for me to tell what might be wrong here.

> 2 - How does pppdump know that he has to use deflate for decompression?

It watches the CCP negotiation.  See pppdump.c for details.  It's a
pretty simple program.

For what it's worth, I'd be at least mildly surprised if someone was
running Deflate with PPTP.  That'd be a weird combination of things --
Deflate comes from the open standards world, but PPTP is a Microsoft
proprietary thing that relies on a number of Microsoft proprietary
extensions.

Are you sure the data are compressed with Deflate as originally stated?

Note that pppdump knows only about the open standards -- BSD Compress
and Deflate algorithms.  If this link is using MPPC instead (Microsoft's
proprietary data compression algorithm), then you're sunk.  I don't know
of any simple tools that currently deal with that situation.

Assuming that's the problem, it's possible that there are third party
network analyzers out there that can handle MPPC over PPP over PPTP.  I
haven't researched the state of the art for commercial network
monitoring gear in many years now.

-- 
James Carlson         42.703N 71.076W         <carlsonj@workingcode.com>

      parent reply	other threads:[~2014-12-22 19:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 20:49 PPP compression arthurpaulino
2014-12-18 21:24 ` James Carlson
2014-12-19 17:28 ` Arthur Paulino
2014-12-20 21:24 ` James Carlson
2014-12-21 18:37 ` Michael Richardson
2014-12-22 12:34 ` James Carlson
2014-12-22 18:06 ` arthurpaulino
2014-12-22 19:09 ` James Carlson [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=54986C54.5030707@workingcode.com \
    --to=carlsonj@workingcode.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).