On Sat, 11 Mar 2000, Janette Welsh wrote:
|Mar 10 22:54:02 dusty pppd[817]: rcvd [LCP TermReq id=0x3]
|Mar 10 22:54:02 dusty pppd[817]: LCP terminated by peer
|Mar 10 22:54:02 dusty pppd[817]: sent [LCP TermAck id=0x3]
|Mar 10 22:54:03 dusty pppd[817]: Hangup (SIGHUP)
|Mar 10 22:54:03 dusty pppd[817]: Modem hangup
|Mar 10 22:54:03 dusty pppd[817]: Connection terminated.
|Mar 10 22:54:03 dusty pppd[817]: Connect time 2.2 minutes.
|Mar 10 22:54:03 dusty pppd[817]: Sent 404 bytes, received 456 bytes.
|Mar 10 22:54:04 dusty pppd[817]: Exit.
|
|End Section 3 -------------------
|
|
|Any suggestions? I really don't wan't to be running top or pinging a
|host every minute to keep alive. Before today I've managed to stay
|connected to this ISP (DataFast) for days without a problem and now
|trouble begins. I have tried my old ISP and had no problems with
|timeouts (Telstra bigpond). Can I do anything from my side (I think it's
|a problem from their side or incompatability or something)?
The logs seemed a bit less than pristine, but all things considered I
think you'll either need to talk to the ISP and get them to remove the
timeout they apparently have set on their end, or to add the pppd option
"lcp-echo-interval <n>" . I don't know whether including the option
"lcp-echo-failure <n>" is appropriate or not for you. See man pppd.
---
Clifford Kite Not a guru. (tm)
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
