From: Manish Kambdur <manish.kambdur@gmail.com>
To: linux-ppp@vger.kernel.org
Subject: Re: Problem: How to force(?) pcomp and accomp
Date: Mon, 03 Oct 2016 16:51:12 +0000 [thread overview]
Message-ID: <CAAAUBLT2Scup_ZjZQNo2fLPvqJFiNH61jEt5iTYnmOJVSg-fSg@mail.gmail.com> (raw)
In-Reply-To: <CAAAUBLR3EqnpES7FrcABVZWB1j-NeOyH7_MoTH-iVYFJD14_XQ@mail.gmail.com>
I wasn't sure my diagnosis was right till you confirmed it was, thanks a lot.
I was able to get the setup working!
> Assuming you can't find those options present in /etc/ppp/options
I had misunderstood how the command line option "file" works as I was
thinking that it override all other options.
I was starting pppd as `pppd call gprs` (with gprs in /etc/ppp/peers/)
and didn't think that pppd reads both the /etc/ppp/options and gprs
file.
> For what it's worth, I think the peer you're talking to is garbage. At
> a minimum, any reasonable implementation of PPP should accept the
> defaults, which means that dropping the link just because your end
> doesn't want to do ACFC and PFC is pure nonsense. How could any
> competent implementation fail to operate without header compression?
> How much do you trust that peer if they can't get the basics of PPP right?
The "peer" here refers to the serial modem or the remote server?
pppd succeeds when I use a modem from a different brand, with the same
SIM and with 'noaccomp' and 'nopcomp'
next prev parent reply other threads:[~2016-10-03 16:51 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 [this message]
2016-10-03 16:52 ` James Carlson
2016-10-04 4:41 ` Manish Kambdur
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=CAAAUBLT2Scup_ZjZQNo2fLPvqJFiNH61jEt5iTYnmOJVSg-fSg@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).