linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: linux-ppp@vger.kernel.org
Subject: Re: PPP compression
Date: Sun, 21 Dec 2014 18:37:43 +0000	[thread overview]
Message-ID: <18176.1419187063@sandelman.ca> (raw)
In-Reply-To: <3b4526880d737ed5094d632636e6fef8@great.ufc.br>


James Carlson <carlsonj@workingcode.com> wrote:
    >> I tried to use pppdump with -p and -d. The input file I used was the
    >> pcap file (packets.pcap) generated by tcpdump.

    > As I said, pppdump and pcap formats are not at all the same.  You'll
    > have to convert to go this route.

    > Attached is a quick-and-dirty program I wrote to convert from the Linux
    > libpcap variant and PPTP encapsulation you seem to be using and simple
    > pppdump format.  I didn't bother with timestamps or other bits.  Maybe
    > it'll work for you.

Do you think it would be worth having a tcpdump DLT type for pppdump stuff,
and just wrap it all up into a pcap container?

--
]               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    [


  parent reply	other threads:[~2014-12-21 18:37 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 [this message]
2014-12-22 12:34 ` James Carlson
2014-12-22 18:06 ` arthurpaulino
2014-12-22 19:09 ` James Carlson

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=18176.1419187063@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 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).