[2160] in linux-net channel archive
Re: LCP echo problems (again)
daemon@ATHENA.MIT.EDU (linuxsys@ssg.com)
Wed Mar 20 00:25:12 1996
Date: Wed, 20 Mar 1996 04:39:10 GMT
From: linuxsys@ssg.com
To: "Al Longyear" <longyear@netcom.com>
Cc: linuxsys@ssg.com, linux-net@vger.rutgers.edu
In-Reply-To: <199603200209.SAA00167@costello.longyear.com>
Al Longyear writes:
> > I'm still having problems maintaining a PPP link. The following
[...]
> There have been reports of people attempting to use the Linux PPP process
> with broken clients on the other end of the telephone line.
Add me to that number!
> The most common problem is that they totally freq out when they see a unknown
> frame. They will usually follow the RFC in that they will send a protocol
> reject, but they fail to understand that the CCP frame is an independent
> protocol and they try to take down the link when they see the CCP frame.
[...]
> or, if the peer refuses to listen to you or you can not convince them as
> to the errors of their ways,
I'm in this group, alas.
> 2. Edit the pppd code so that it does not attempt to send CCP frames. If you
> do this then you will also prevent the PPPD process from using CCP.
How bad is this (losing CCP frame capability)? What am I losing in
trying to talk with other, non-broken hosts if I don't have this
capability?
> If you choose to do this, then edit the main.c code and comment/delete
> the call to the ccp_open() function. In addition, you will need to
> comment/delete the CCP protocol entry in the protab[] list near the
> top of the file.
Sounds simple enough... (are those Famous Last Words?)
[...]
> It does. However, it is the peer system which sends the EchoRep to the
> second EchoReq. It had given up on the link because of the CCP frame
> by that time.
Gotit. TNX for excerpt from RFC 1661 and, once again, a glimpse at
enlightenment.
Rick
