On Wed, 6 Jan 1999, Benevento Cristiano-Q14793 wrote:
> First, the new log:
>
> Jan 6 13:54:17 xcpc pppd[2088]: rcvd [CCP TermReq id=0x6 00 00 02 dc]
> Jan 6 13:54:17 xcpc pppd[2088]: sent [CCP TermAck id=0x6]
...
> Jan 6 13:54:20 xcpc pppd[2088]: sent [CCP ConfReq id=0x1]
> Jan 6 13:54:44 xcpc last message repeated 8 times
> Jan 6 13:54:47 xcpc pppd[2088]: CCP: timeout sending Config-Requests
> Jan 6 13:56:54 xcpc pppd[2088]: Hangup (SIGHUP)
That does look strange. It appears that the peer is saying don't use CCP
right off the bat, your end acknowledges, but tries later anyway. You
might try adding 'noccp' to your pppd options and see what happens.
Geof
DISCLAIMER: The comments above are my own and may not represent the views
of my employer.
+-------------------------------+-------------------------------------------+
: Geoffrey P. Goodrum : US Department of Commerce :
: +1-301-457-5100 : NOAA/NESDIS National Climatic Data Center :
: [EMAIL PROTECTED]: Satellite Services Branch :
+-------------------------------+-------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to [EMAIL PROTECTED]
