From: Andy <fs@globalnetit.com>
To: linux-ppp@vger.kernel.org
Subject: Re: pppd 2.4.2b3 IPCP converge failure
Date: Sun, 21 Mar 2004 19:21:12 +0000 [thread overview]
Message-ID: <1079896872.1131.65.camel@dell.tranquilitynj.net> (raw)
In-Reply-To: <1079855955.1133.48.camel@dell.tranquilitynj.net>
On Sun, 2004-03-21 at 13:44, James Carlson wrote:
> You've cut off the important part of this log -- the one where the
> peers had initial trouble negotiating IPCP. You'll need to get that
> part of the log and examine it.
I know. As I mentioned, I only have about 5 minutes of logs, the earlier
stuff got overwritten. There's just not enough space on the device to
store more. This whole event lasted for about an hour.
If it happens again, I may be able to find a way to save more.
>
> > I'm wondering about the ConfReq packets, what is the second address
> > field doing there (as in addrs 68.244.143.67 0.0.0.0)
>
> This is the old, obsolete IP-Addresses option (see RFC 1332, section
> 3.1). The only time it's used is when the modern IP-Address option
> fails. And, yes, pppd is rather insistent on trying to use it when
> all else fails.
>
> It's just a symptom of some other problem, not a cause, and not
> necessarily a problem in itself.
>
> At a guess, something went terribly wrong in the initial IPCP
> negotiation. Does that remote peer properly implement the state
> machine from RFC 1661?
No idea - it's an ISP, I don't know what they're using.
However, whether they implement it correctly or not, it seems that pppd
does not - it's pretty clear from rfc1661 that just repeating the same
configure-request over and over, despite getting a configure-reject, is
a protocol violation.
Although it would be useful to know how we got into this state, it's
probably more important to fix the code so this endless loop won't
happen. I'm not familiar enough with the IPCP FSM as implemented in pppd
to be able to do that quickly, I was hoping someone may have done this
work already. If not, I'll try to get into the code myself.
next prev parent reply other threads:[~2004-03-21 19:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-21 7:59 pppd 2.4.2b3 IPCP converge failure Andy
2004-03-21 18:44 ` James Carlson
2004-03-21 19:21 ` Andy [this message]
2004-03-22 5:34 ` Paul Mackerras
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=1079896872.1131.65.camel@dell.tranquilitynj.net \
--to=fs@globalnetit.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