archive mirror
 help / color / mirror / Atom feed
From: James Carlson <>
Subject: Re: CHAP Auth issue at CentOS-6.8
Date: Tue, 13 Sep 2016 13:10:10 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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         <>

  reply	other threads:[~2016-09-13 13:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 12:45 CHAP Auth issue at CentOS-6.8 Sekar D
2016-09-13 13:10 ` James Carlson [this message]
2016-09-13 13:37 ` Sekar D
2016-09-13 14:05 ` James Carlson
2016-09-13 15:02 ` James Carlson
2016-09-13 23:06 ` Bill Unruh

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).