On 09/13/2016 08:33 AM, Sekar D wrote: > I did not see kind of issue on CentOS-5.11 . Please let me know if I > need to change any config parameters. It's a little hard to tell. What are your current configuration parameters? Have you tried running pppd with debugging enabled? It would help to have a trace of the connection in order to diagnose the failure mode. The starting point is the pppd "debug" option, but if you're controlling this connection with ifup/ifdown scripts, you'll have to look at your system configuration to find out what pppd options are in use for that link. One possible answer, if all else fails, would be to run this while the link is in the process of establishing: ps -fp `pgrep -d, pppd` | cat (Yes, the "cat" is important; it tricks ps into printing the whole line.) What kind of connection is this? That is, what's the underlying serial link? Is it a physical wire on a serial port? Is it a USB serial port? Is it ISDN? Is it PPPoE or PPTP or L2TP? Is it something else? At a guess, the problem is on the remote end. Typically, a user's PPP connection is set up to be a "client" -- that is, to reply to authentication requests from the peer and not to request authentication from the peer. This means that the remote system you're talking to asked for your CHAP credentials, your system supplied them, and the remote system denied your access based on those credentials. If that only happens "sometimes" or is dependent on timing, then it sounds like the remote system has some kind of usage restriction. -- James Carlson 42.703N 71.076W <carlsonj@xxxxxxxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-ppp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
