linux-ppp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manish Kambdur <manish.kambdur@gmail.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Problem: How to force(?) pcomp and accomp
Date: Tue, 04 Oct 2016 04:41:03 +0000	[thread overview]
Message-ID: <CAAAUBLRSZg=zWA2yjjwN=gNjG25mn+6d7QJnWCuiixBRzeRQMg@mail.gmail.com> (raw)
In-Reply-To: <CAAAUBLR3EqnpES7FrcABVZWB1j-NeOyH7_MoTH-iVYFJD14_XQ@mail.gmail.com>

> Yes, it does.  /etc/ppp/options sets the system-wide options required
> for all links.  The privileged "call" and unprivileged "file" options
> are there (along with the command line) to add options that are specific
> to an individual link.

I had assumed all three are equivalent and I had to choose one method.
The actual design makes much more sense.

> That information would have helped.  GPRS has a number of built-in
> design flaws.  One of them is that the LCP negotiation is done locally
> (not end-to-end) along with a completely faked-out authentication layer.
>  The "real" negotiation with the remote endpoint doesn't occur until the
> Network phase -- that is, during IPCP.
>
> So, yes, I'm referring to the device doing LCP negotiation.  It's not
> doing it right.

Thanks a lot for this explanation. My whole setup and situation is
much more clear to me now.
I kept wondering why the peer had different behaviour based on the
GPRS modem I was using. I was under the impression that the chat
script talks to the modem, and pppd talks to the remote server.

Thanks again!!

Regards,
Manish

      parent reply	other threads:[~2016-10-04  4:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-01 15:50 Problem: How to force(?) pcomp and accomp Manish Kambdur
2016-10-03 12:15 ` James Carlson
2016-10-03 16:51 ` Manish Kambdur
2016-10-03 16:52 ` James Carlson
2016-10-04  4:41 ` Manish Kambdur [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='CAAAUBLRSZg=zWA2yjjwN=gNjG25mn+6d7QJnWCuiixBRzeRQMg@mail.gmail.com' \
    --to=manish.kambdur@gmail.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).