All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Carlson <carlsonj@workingcode.com>
To: linux-ppp@vger.kernel.org
Subject: Re: PPP comression and extension info required...
Date: Thu, 24 Jun 2010 14:19:43 +0000	[thread overview]
Message-ID: <4C23697F.3070405@workingcode.com> (raw)
In-Reply-To: <4C2246C1.2000206@workingcode.com>

arun b wrote:
> Ok,
> as you said i can verify all compression types on PPPoE test...
> So i have pppoe-server available at my pc,  if you have come across
> related server configuration for this .... pls do know me.
> and running PPPoA - test running is not just easy to me as
> unavailability of the device.

I don't know what you're asking about, but pppd generally enables all
available compression modes by default (regardless of the underlying
communication mechanism), and will disable a compression mode either if
the peer disagrees with the request or if you specify one of the
documented options to turn off that mode (or to turn off compression
completely).

In other words, if your "server" is actually pppd, then there's nothing
that you need to do to enable compression.  If it's something other than
pppd, then this might not be the right mailing list.  You should consult
your server's documentation to find out what features it offers.

As for selectively turning off available compression types in pppd, I
still urge you to read the pppd man page.  It's pretty important.  For
data compression options, you'll find the following:

  noccp, bsdcomp, nobsdcomp, deflate, nodeflate, predictor1,
  nopredictor1

For header compression (again, _not_ data compression), you'll find:

  noaccomp, novj, novjccomp, vj-max-slots

There are also two that are sort of special -- mpshortseq and
nompshortseq -- that have to do with header compression when using MP.
You haven't mentioned MP yet, so I'll assume you're not using it.

The really short answer is this: PPP negotiates for everything.  If both
sides support something, then, great, it'll be enabled.  If either or
both sides don't support something, then it won't be enabled.  That's
pretty much the whole story.

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

  parent reply	other threads:[~2010-06-24 14:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-23 17:39 PPP comression and extension info required James Carlson
2010-06-23 17:41 ` arun b
2010-06-23 17:59 ` arun b
2010-06-23 18:17 ` James Carlson
2010-06-24  5:13 ` arun b
2010-06-24  7:23 ` James Cameron
2010-06-24 10:18 ` arun b
2010-06-24 10:22 ` arun b
2010-06-24 11:10 ` James Carlson
2010-06-24 11:24 ` James Carlson
2010-06-24 13:55 ` arun b
2010-06-24 14:19 ` James Carlson [this message]
2010-06-24 16:48 ` arun b
2010-06-24 17:49 ` James Carlson
2010-06-25  0:51 ` arun b

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=4C23697F.3070405@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 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.