Linux PPP protocol development
 help / color / mirror / Atom feed
From: carlsonj@workingcode.com
To: linux-ppp@vger.kernel.org
Subject: Re: ppp 2.4.3 cvs authentication issue
Date: Thu, 28 Oct 2004 12:54:55 +0000	[thread overview]
Message-ID: <16768.60447.480154.73089@carlson.workingcode.com> (raw)
In-Reply-To: <20041028124517.7204.qmail@web25210.mail.ukl.yahoo.com>

a b writes:
> I'm trying to set up a pptpd server under Mandrake
> 10.0 and I think my problem is related to pppd and the
> authentication.

You're the server side?  Then why is your peer demanding that you
authenticate yourself?

> client:
> 
> cat /etc/ppp/peers/pptp0 
[...]
> refuse-pap
> refuse-eap
> refuse-chap
> refuse-mschap
> require-mschap-v2

There's the misconfiguration.  The client should not have the above
five options.  Instead, it should just have "noauth."  (As long as the
client doesn't have a default route, it won't even need "noauth.")

> Please note that if I simply change two lines on both
> sides:
> 
> add noauth and comment out require-mschap-v2 I get

Don't change both sides.  The server looks fine.  It's the client
that's misconfigured.

You have it set up so that both sides demand authentication and both
sides *refuse* that demand.  What else could possibly be the result?

-- 
James Carlson                                 <carlsonj@workingcode.com>

  reply	other threads:[~2004-10-28 12:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-28 12:45 ppp 2.4.3 cvs authentication issue a b
2004-10-28 12:54 ` carlsonj [this message]
2004-10-28 13:10 ` a b
2004-10-28 13:45 ` a b
2004-10-28 14:08 ` carlsonj
2004-10-28 14:52 ` a b
2004-10-28 15:00 ` carlsonj
2004-10-28 15:33 ` a b
2004-10-28 15:41 ` carlsonj
2004-10-28 15:52 ` a b
2004-10-28 15:57 ` carlsonj
2004-10-28 16:04 ` Bill Unruh
2004-10-28 16:07 ` Bill Unruh
2004-10-28 16:10 ` Bill Unruh
2004-10-28 17:01 ` a b

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=16768.60447.480154.73089@carlson.workingcode.com \
    --to=carlsonj@workingcode.com \
    --cc=linux-ppp@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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