On Sun, 20 Sep 1998, Ivan Gustin wrote:
> I am seting up Linux Internet server via leased line using USR Courier.
> Distribution is Caldera OpenLinux Base 1.1 based on Linux 2.0.29.
>...
> There is a problem with establishing connection. pppd starts well, but it
> hangs up short after with message in /var/log/message "LCP timeout sending
> Config-Request". Few seconds after it wakes up again, but with the same
> result.
>...
> Using interface ppp0
> Connect: ppp0 <--> /dev/ttyS1
> sent [LCP ConfReq id=0x1e <mru 576> <magic 0xb9e283eb> <pcomp> <accomp>]
> LCP timeout sending Config-Request
> Hangup (SIGHUP)
> Modem hangup
> Connection terminated
> ----------
>
> I have following line in /etc/rc.d/rc.local:
> ----------
> setserial /dev/ttyS1 115200
> pppd /dev/ttyS1 115200 &
> ----------
>
> Here is /etc/ppp/option.ttyS1:
> ----------
> crtscts
> mru 576
> mtu 576
> passive
> LocalIP:RemoteIP -> here is real IP numbers
> -chap
> modem
> -pap
> persist
> ----------
>
> /etc/ppp/option is empty.
>
> I assume that there is some problem with some timing parameter, but nothing
> helped what I tried. I tried with uart 16450 option (suspecting on FIFO),
> increasing lcp-max-configure number, but without success.
Is there a log file at the other end that you can look at? I.e. can
you confirm that the LCP ConfReqs are really being sent out?
The possibilities are that they are not being sent, or that replies
to them are not being seen, or that there is a PPP problem at the
other end, am I right?
Since you have a passive PPP already on the line, shouldn't the
first line in the log file refer to receipt of a packet from the
other end? I.e. it shouldn't be sending config requests until it
has received a packet, if I understand rightly; and the packet it
receives should be a ConfReq which it should have logged.
Now for the drastic solution. Chuck out the 486. I few weeks ago I
had almost exactly the same problem, but with the addition of mgetty
and a dial-up line.
pppd would start, and would send out ConfReqs but ignored the
responses and hung up. It could run pppd as a client, receiving
packets normally, but had a strange blindness to all responses to
its own ConfReqs. I suspected bad memory, replaced the old 486 with
a new computer and the problem (that particular one - I'm still not
in operation) was fixed.
Rgds, mtw
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
