Re: M$CHAP with PPP

1999-07-16 Thread Damon Muller

On Wed, 14 Jul 1999 10:52:20 -0500
Michael Merten [EMAIL PROTECTED] wrote:

 The NT server I'm trying to connect to is definitely using the
 M$CRAP^H^H^HHAP mentioned in one of the doc files included with ppp
 (it's different from the standard CHAP).  To date I still haven't
 managed to get this to work.

I've also had a play around with this, trying to connect to an NT
server, and have also had no luck.

I wonder if the default debian pppd has MSCHAP80 support compiled in
already? in the README.MSCHAP doc, it says that the client (my debian
machine), so respond with an NAck, saying it doesn't understand CHAP80,
but mine responds with an Ack. I'm not sure I exactly understand what is
going on, but here is the relevant bit of my ppp.log

Jul 15 13:05:11 rei pppd[28567]: sent [LCP ConfReq id=0x1 asyncmap 0x0
magic 
0xef142e3e pcomp accomp]
Jul 15 13:05:11 rei pppd[28567]: rcvd [LCP ConfReq id=0x0 asyncmap 0x0
auth c
hap 80 magic 0x52dc pcomp accomp]
Jul 15 13:05:11 rei pppd[28567]: sent [LCP ConfAck id=0x0 asyncmap 0x0
auth c
hap 80 magic 0x52dc pcomp accomp]
Jul 15 13:05:11 rei pppd[28567]: rcvd [LCP ConfAck id=0x1 asyncmap 0x0
magic 
0xef142e3e pcomp accomp]
Jul 15 13:05:11 rei pppd[28567]: sent [LCP EchoReq id=0x0 magic=0xef142e3e]
Jul 15 13:05:11 rei pppd[28567]: rcvd [CHAP Challenge id=0x14
b8c560ecb9d27626
, name = ]
Jul 15 13:05:11 rei pppd[28567]: sent [CHAP Response id=0x14
00
002c02709fb8f21e7fa8fe7b8a7b666bda3c5b8f06125a3ab
201
, name = damonm]
Jul 15 13:05:11 rei pppd[28567]: rcvd [LCP EchoRep id=0x0 magic=0x52dc]
Jul 15 13:05:14 rei pppd[28567]: sent [CHAP Response id=0x14
00
002c02709fb8f21e7fa8fe7b8a7b666bda3c5b8f06125a3ab
201
, name = damonm]
Jul 15 13:05:14 rei pppd[28567]: rcvd [CHAP Failure id=0x14 E=691 R=1]
Jul 15 13:05:14 rei pppd[28567]: Remote message: E=691 R=1
Jul 15 13:05:14 rei pppd[28567]: CHAP authentication failed

It looks like it responded to the chap challenge, yet it still failed to
authenticate. This is with the default pppd included with slink.

Any thought anyone?

damon

--
Damon Muller  | Did a large procession wave their torches
([EMAIL PROTECTED]) | As my head fell in the basket,
Network Administrator | And was everyone dancing on the casket...
EmpireNET |  - TBMG, Dead


Re: M$CHAP with PPP

1999-07-16 Thread John Hasler
 I wonder if the default debian pppd has MSCHAP80 support compiled in
 already?

2.3.7 does.  From the changelog, it appears to have been there since
2.3.2.

If you get it working let me know how so I can add support for it to
pppconfig.
-- 
John Hasler
[EMAIL PROTECTED] (John Hasler)
Dancing Horse Hill
Elmwood, WI


Re: M$CHAP with PPP

1999-07-16 Thread Michael Merten
On Fri, Jul 16, 1999 at 12:11:32PM +1000, Damon Muller wrote:
 
 On Wed, 14 Jul 1999 10:52:20 -0500
 Michael Merten [EMAIL PROTECTED] wrote:
 
  The NT server I'm trying to connect to is definitely using the
  M$CRAP^H^H^HHAP mentioned in one of the doc files included with ppp
  (it's different from the standard CHAP).  To date I still haven't
  managed to get this to work.
 
 I've also had a play around with this, trying to connect to an NT
 server, and have also had no luck.
 
 I wonder if the default debian pppd has MSCHAP80 support compiled in
 already? in the README.MSCHAP doc, it says that the client (my debian
 machine), so respond with an NAck, saying it doesn't understand CHAP80,
 but mine responds with an Ack. I'm not sure I exactly understand what is
 going on, but here is the relevant bit of my ppp.log
 
 Jul 15 13:05:11 rei pppd[28567]: rcvd [LCP ConfReq id=0x0 asyncmap 0x0
 auth chap 80 magic 0x52dc pcomp accomp]
 Jul 15 13:05:11 rei pppd[28567]: sent [LCP ConfAck id=0x0 asyncmap 0x0
 auth chap 80 magic 0x52dc pcomp accomp]
 Jul 15 13:05:11 rei pppd[28567]: rcvd [LCP ConfAck id=0x1 asyncmap 0x0
 magic 0xef142e3e pcomp accomp]
 Jul 15 13:05:11 rei pppd[28567]: sent [LCP EchoReq id=0x0 magic=0xef142e3e]
 Jul 15 13:05:11 rei pppd[28567]: rcvd [CHAP Challenge id=0x14
 b8c560ecb9d27626, name = ]
 Jul 15 13:05:11 rei pppd[28567]: sent [CHAP Response id=0x14
 
 2c02709fb8f21e7fa8fe7b8a7b666bda3c5b8f06125a3ab201, name = damonm]
 Jul 15 13:05:11 rei pppd[28567]: rcvd [LCP EchoRep id=0x0 magic=0x52dc]
 Jul 15 13:05:14 rei pppd[28567]: sent [CHAP Response id=0x14
 
 2c02709fb8f21e7fa8fe7b8a7b666bda3c5b8f06125a3ab201, name = damonm]
 Jul 15 13:05:14 rei pppd[28567]: rcvd [CHAP Failure id=0x14 E=691 R=1]
 Jul 15 13:05:14 rei pppd[28567]: Remote message: E=691 R=1
 Jul 15 13:05:14 rei pppd[28567]: CHAP authentication failed
 
 It looks like it responded to the chap challenge, yet it still failed to
 authenticate. This is with the default pppd included with slink.

Well, you certainly got farther along than I did.  I can't get pppd 
(2.3.8) to even Ack the chap request.  However, something is strange
here...  from your log, you're geting 'auth chap 80' requests, from
my log, I'm getting 'auth chap m$oft' requests.  That's probably why
my pppd isn't responing to it.  :/

For you problem, you may need to specify (in chap-secrets) the NT
domain as well as the username / password, like this:

domain\\username   remotename   password
remotename   domain\\username   password

Also note that as according to the docs, you have to specify two lines
with the username and remote name swapped.   Beats me why.

HTH,
Mike

[I'm subscribed to the list, no need to CC: me on replys.]

--
Michael Merten ([EMAIL PROTECTED])
  --- NRA Life Member (http://www.nra.org)
  --- Debian GNU/Linux Fan (http://www.debian.org)
  --- CenLA-LUG Founder (http://www.angelfire.com/la2/cenlalug)
--
How many hardware guys does it take to change a light bulb?
Well the diagnostics say it's fine buddy, so it's a software problem.


Re: M$CHAP with PPP

1999-07-14 Thread Martin Waller
I had problems connecting to my provider with chap (but whether its the same 
version as your chap I don't know), and I used the ppp-config to set it up 
once all my 'by hand' efforts had failed.  It worked a charm, but I say I'm 
not sure my provider uses your provider's version of chap.


HTH

Martin


From: Michael Merten [EMAIL PROTECTED]
To: debian-user@lists.debian.org
Subject: Re: M$CHAP with PPP
Date: Mon, 12 Jul 1999 17:25:34 -0500

On Mon, Jul 12, 1999 at 01:14:30PM -0500, Jens B. Jorgensen wrote:
 I'm going to bet that it isn't liking the entries in your chap-secrets 
file. It probably isn't matching the entry you've made.



Ok, my chap-secrets file is set up like this...

   ntdomain\\username isp password
   isp ntdomain\\username password

I do know that the ntdomain must be given.  Even logging in with Win, you
get repeated authorization dialogs until you enter the correct NT domain.

In my /etc/ppp/peers/isp file I have:

   hide-password
   noauth
   connect /usr/sbin/chat -v -f /etc/chatscripts/isp
   debug
   /dev/ttyS1
   115200
   defaultroute
   noipdefault
   -am
   user username
   remotename isp
   ipparam isp
   usepeerdns

Note that I had to include the -am option in the above because when my side
of the connection sent an LCP packet requesting asyncmap negotiation 
(usually

the first thing sent), the other side dropped carrier.

Finally, /etc/chatscript/isp is:

   ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 
'NO DIAL TONE' ABORT 'NO ANSWER'

   '' ATZ
   OK-AT-OK ATDT*70,ispphone
   CONNECT \d\c


I'm at a loss to figure out anything else to do.  I have logged in using
Win dial-up, so I know the username/password/ntdomain are correct.  Any
ideas?

Mike

--
Michael Merten ([EMAIL PROTECTED])
  --- NRA Life Member (http://www.nra.org)
  --- Debian GNU/Linux Fan (http://www.debian.org)
  --- CenLA-LUG Founder (http://www.angelfire.com/la2/cenlalug)
--
It is now pitch dark. If you proceed, you will likely fall into a pit.


--
Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  
/dev/null





__
Get Your Private, Free Email at http://www.hotmail.com


Re: M$CHAP with PPP

1999-07-14 Thread Michael Merten
On Wed, Jul 14, 1999 at 03:27:04AM -0700, Martin Waller wrote:
 I had problems connecting to my provider with chap (but whether its the same 
 version as your chap I don't know), and I used the ppp-config to set it up 
 once all my 'by hand' efforts had failed.  It worked a charm, but I say I'm 
 not sure my provider uses your provider's version of chap.
 
 HTH
 
 Martin

The NT server I'm trying to connect to is definitely using the
M$CRAP^H^H^HHAP mentioned in one of the doc files included with ppp
(it's different from the standard CHAP).  To date I still haven't
managed to get this to work.

Mike
-- 
Michael Merten ([EMAIL PROTECTED])
  --- NRA Life Member (http://www.nra.org)
  --- Debian GNU/Linux Fan (http://www.debian.org)
  --- CenLA-LUG Founder (http://www.angelfire.com/la2/cenlalug)
--
New Hampshire law forbids you to tap your feet, nod your head, or in
any way keep time to the music in a tavern, restaurant, or cafe.
--
This signature was automatically generated with Signify v1.05.
For this and other cool products, check out http://www.debian.org/.


Re: M$CHAP with PPP

1999-07-12 Thread Jens B. Jorgensen
I'm going to bet that it isn't liking the entries in your chap-secrets file. It 
probably isn't matching the entry you've made.

Michael Merten wrote:

 Hi,

 Has anyone been able to get ppp to work with MSCHAP80?  I've
 done (as far as I can tell) everything the /usr/doc/ppp/README.MSCHAP80.gz
 file says to do, (downloaded and installed libdes, rebuilt the ppp package
 locally, edited the /etc/ppp/chap-secrets file, etc) but my pppd is still
 rejecting the auth requests:

   [snip]
   Jul 10 19:28:36 casper pppd[7055]: Connect: ppp0 -- /dev/ttyS1
   Jul 10 19:28:37 casper pppd[7055]: sent [LCP ConfReq id=0x1 magic 
 0x3f677f9d pcomp accomp]
   Jul 10 19:28:37 casper pppd[7055]: rcvd [LCP ConfReq id=0x0 asyncmap 0x0 
 auth chap m$oft magic 0x564e pcomp accomp]
   Jul 10 19:28:37 casper pppd[7055]: sent [LCP ConfRej id=0x0 asyncmap 0x0 
 auth chap m$oft]
   Jul 10 19:28:37 casper pppd[7055]: rcvd [LCP ConfAck id=0x1 magic 
 0x3f677f9d pcomp accomp]
   Jul 10 19:28:38 casper pppd[7055]: rcvd [LCP TermReq id=0x1 00 00 02 dc]
   Jul 10 19:28:38 casper pppd[7055]: sent [LCP TermAck id=0x1]
   Jul 10 19:28:38 casper pppd[7055]: Hangup (SIGHUP)
   [snip]

 I normally wouldn't worry about this, but I can access the internet
 through this server for free, if I can get it working.

 BTW, I'm using ppp 2.3.8.

 TIA,
 Mike

 --
 Michael Merten ([EMAIL PROTECTED])
   --- NRA Life Member (http://www.nra.org)
   --- Debian GNU/Linux Fan (http://www.debian.org)
   --- CenLA-LUG Founder (http://www.angelfire.com/la2/cenlalug)
 --
 Bank error in your favor.  Collect $200.
 --

 --
 Unsubscribe?  mail -s unsubscribe [EMAIL PROTECTED]  /dev/null

--
Jens B. Jorgensen
[EMAIL PROTECTED]



Re: M$CHAP with PPP

1999-07-12 Thread Michael Merten
On Mon, Jul 12, 1999 at 01:14:30PM -0500, Jens B. Jorgensen wrote:
 I'm going to bet that it isn't liking the entries in your chap-secrets file. 
 It probably isn't matching the entry you've made.
 

Ok, my chap-secrets file is set up like this...

   ntdomain\\username isp password
   isp ntdomain\\username password

I do know that the ntdomain must be given.  Even logging in with Win, you
get repeated authorization dialogs until you enter the correct NT domain.

In my /etc/ppp/peers/isp file I have:

   hide-password 
   noauth
   connect /usr/sbin/chat -v -f /etc/chatscripts/isp
   debug
   /dev/ttyS1
   115200
   defaultroute
   noipdefault
   -am
   user username
   remotename isp
   ipparam isp
   usepeerdns

Note that I had to include the -am option in the above because when my side
of the connection sent an LCP packet requesting asyncmap negotiation (usually
the first thing sent), the other side dropped carrier.

Finally, /etc/chatscript/isp is:

   ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO 
DIAL TONE' ABORT 'NO ANSWER'
   '' ATZ
   OK-AT-OK ATDT*70,ispphone
   CONNECT \d\c


I'm at a loss to figure out anything else to do.  I have logged in using 
Win dial-up, so I know the username/password/ntdomain are correct.  Any
ideas?

Mike

-- 
Michael Merten ([EMAIL PROTECTED])
  --- NRA Life Member (http://www.nra.org)
  --- Debian GNU/Linux Fan (http://www.debian.org)
  --- CenLA-LUG Founder (http://www.angelfire.com/la2/cenlalug)
--
It is now pitch dark. If you proceed, you will likely fall into a pit.


M$CHAP with PPP

1999-07-11 Thread Michael Merten
Hi,

Has anyone been able to get ppp to work with MSCHAP80?  I've
done (as far as I can tell) everything the /usr/doc/ppp/README.MSCHAP80.gz
file says to do, (downloaded and installed libdes, rebuilt the ppp package
locally, edited the /etc/ppp/chap-secrets file, etc) but my pppd is still
rejecting the auth requests:

  [snip]
  Jul 10 19:28:36 casper pppd[7055]: Connect: ppp0 -- /dev/ttyS1
  Jul 10 19:28:37 casper pppd[7055]: sent [LCP ConfReq id=0x1 magic 
0x3f677f9d pcomp accomp]
  Jul 10 19:28:37 casper pppd[7055]: rcvd [LCP ConfReq id=0x0 asyncmap 0x0 
auth chap m$oft magic 0x564e pcomp accomp]
  Jul 10 19:28:37 casper pppd[7055]: sent [LCP ConfRej id=0x0 asyncmap 0x0 
auth chap m$oft]
  Jul 10 19:28:37 casper pppd[7055]: rcvd [LCP ConfAck id=0x1 magic 
0x3f677f9d pcomp accomp]
  Jul 10 19:28:38 casper pppd[7055]: rcvd [LCP TermReq id=0x1 00 00 02 dc]
  Jul 10 19:28:38 casper pppd[7055]: sent [LCP TermAck id=0x1]
  Jul 10 19:28:38 casper pppd[7055]: Hangup (SIGHUP)
  [snip]

I normally wouldn't worry about this, but I can access the internet
through this server for free, if I can get it working.

BTW, I'm using ppp 2.3.8.

TIA,
Mike


-- 
Michael Merten ([EMAIL PROTECTED])
  --- NRA Life Member (http://www.nra.org)
  --- Debian GNU/Linux Fan (http://www.debian.org)
  --- CenLA-LUG Founder (http://www.angelfire.com/la2/cenlalug)
--
Bank error in your favor.  Collect $200.
--