How to disable LCP extensions in pppd??
Michael V. Ferranti
>Change your connection authentication protocol from CHAP to PAP. If
>that does not do it or does not apply, look into a way to disable
>LCP extentsions on your PPPd. We do not use them.
Well, I'm definitely using PAP, and so far I've tried any and all for
the following pppd options: "silent", "passive", and "updetach" along with
"usepeerdns" (since their server now specifies DNS numbers at login.
Nothing is working for me, because everything still hangs right where LCP
negotiations are expected. I can't get in touch with anyone at my ISP with
enough network savvy to help. Anyone know how to disable LCP? I can't
find anything else in the man pages that refers to it, and for the options
that do mention LCP, I've tried using every combination there is.
I wonder if tech support is jerking my chains here...I've been working
on this damned problem for a month now and I *still* can't get Linux
reconnected...
- Michael V. Ferranti [blades&inreach*com]
GNUke The Planet!
The GNUclear NetworkŽ
ID# 177869 Registered with the Linux Counter. http://counter.li.org
Peter Colman
> Just got this info back from my ISP:
>
> >Change your connection authentication protocol from CHAP to PAP. If
> >that does not do it or does not apply, look into a way to disable
> >LCP extentsions on your PPPd. We do not use them.
> <snip>
LCP = Link Control Protocol. You cannot disable it, since this is the protocol
which the to machines speak in order to negotiate options for the ppp connection.
You don't say exactly what fails. If you enable debug optins (pppd -d) you will
get detail on how far the negotiations go. Post this info to the group & someone
should be able to diagnose the problem.
Clifford Kite
> Nothing is working for me, because everything still hangs right where LCP
> negotiations are expected. I can't get in touch with anyone at my ISP with
That very well could be a chat script problem. For instance, replacing
a CONNECT '' chat expect-send with CONNECT '\c' cure it. Check this
site for solving chat connection and PPP link negotitation problems:
http://axion.physics.ubc.ca/ppp-linux.html
> enough network savvy to help. Anyone know how to disable LCP? I can't
You can't, as another reply says. I'm not sure what the ISP means by
"extentions" but it's probably smoke to disguise the fact that they
don't know what to do for a Linux connection.
--
Clifford Kite <kite@inet% port.com> Not a guru. (tm)
/* Governments should be changed like diapers - often and for the
* same reason. */
Brooks
> You can't, as another reply says. I'm not sure what the ISP means by
> "extentions" but it's probably smoke to disguise the fact that they
IIRC, there is an option under NT's dial up networking properties for
'disable PPP LCP extensions'. :) God only knows... mebbe they think 'NT
= Server, *nix = server, server = server, therfore nt=*nix' (and god
only knows what the 'disable ppp lcp extensions' does in nt.. might ask
in a *.nt.* group..)
b
Michael V. Ferranti
Brooks <temp...@worldnet.att.net> just had to go and say:
>IIRC, there is an option under NT's dial up networking properties for
>'disable PPP LCP extensions'. :) God only knows... mebbe they think 'NT
>= Server, *nix = server, server = server, therfore nt=*nix' (and god
>only knows what the 'disable ppp lcp extensions' does in nt.. might ask
>in a *.nt.* group..)
Well, according to RFC-1661, LCP is a MUST for PPP operations, so I'm
thinking my tech support guys dunno jack, or M$ is trying to do it's own
thing again, or pppd is buggy. Ideally, I should handshake with the peer
and establish what's gonna happen from that point on, but that's not what's
happening, not according to what RFC-1661 states. I'm not even getting an
echo of my LCP xmissions back from the server. My Win95 logs (which DOES
connect) say:
>06-04-2000 16:40:09.28 - LCP : Callback negotiation enabled.
>06-04-2000 16:40:09.28 - LCP : Layer started.
>06-04-2000 16:40:09.47 - LCP : Received and accepted MRU of 1524.
>06-04-2000 16:40:09.49 - LCP : Received and accepted ACCM of 0.
>06-04-2000 16:40:09.49 - LCP : Received and accepted authentication
> protocol c023 (PAP).
No idea what "Callback negotiation" is, or what "ACCM" is for that
matter, but whatever they are, pppd ain't even makin' THAT happen. I'm
starting not to care, and I'm thinking maybe I should just give up and
change ISPs. July 4th is Independence Day, and if I haven't solved the
problem by then, I'm dumping these hosers for someone who works within the
system. I don't have time for this "Microshaft-Only" bullshit. It's not
Bill Gate's f'ing internet. Then again, maybe I won't wait...