From owner-freebsd-isdn Tue Oct 27 15:40:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13020 for freebsd-isdn-outgoing; Tue, 27 Oct 1998 15:40:29 -0800 (PST) (envelope-from owner-freebsd-isdn@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13010 for ; Tue, 27 Oct 1998 15:40:24 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id AAA17644; Wed, 28 Oct 1998 00:39:44 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA01608 (5.67b/IDA-1.5); Wed, 28 Oct 1998 00:36:37 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id AAA03672; Wed, 28 Oct 1998 00:08:05 +0100 (CET) From: Wilko Bulte Message-Id: <199810272308.AAA03672@yedi.iaf.nl> Subject: Re: authentication problem In-Reply-To: <199810260847.JAA01447@peedub.muc.de> from Gary Jennejohn at "Oct 26, 98 09:47:15 am" To: garyj@muc.de Date: Wed, 28 Oct 1998 00:08:05 +0100 (CET) Cc: freebsd-isdn@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isdn@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Gary Jennejohn wrote... > Wilko Bulte writes: > >I'm currently working to get i4b to connect to one of my ISPs. On the other > >ISP It works OK, but the 2nd one seems to give me authentication problems. > >Using a Motorola Bitsurfr TA using PAP I can work with both (apart > >from the bugginess of the BS firmware of course ;-) > > > >Thoughts appreciated, > > > > Wilko > > > >Oct 25 23:22:32 yedi /kernel: isppp1: Up event > >Oct 25 23:22:32 yedi /kernel: isppp1: lcp up(starting) > >Oct 25 23:22:32 yedi /kernel: isppp1: lcp output >5-6-36-40-a0-a0-3-4-c0-23> <== PAP > >Oct 25 23:22:33 yedi /kernel: isppp1: lcp input(req-sent): >len=14 5-6-49-31-d5-b1-3-4-c0-23> > >Oct 25 23:22:33 yedi /kernel: isppp1: lcp parse opts: magic auth-proto > >Oct 25 23:22:33 yedi /kernel: isppp1: lcp parse opt values: magic 0x4931d5b1 > >auth-proto send conf-ack > >Oct 25 23:22:33 yedi /kernel: isppp1: lcp output >5-6-49-31-d5-b1-3-4-c0-23> > >Oct 25 23:22:33 yedi /kernel: isppp1: lcp input(ack-sent): >len=9 3-5-c2-23-5> <== CHAP > > if I read RFC 1334 correctly, you're requesting PAP (the c0-23) and he's > rejecting it, saying that he wants CHAP (the c2-23). The strange thing is > that he appears to have OK'd PAP in the first `lcp input' ?!? Or maybe he's > rejecting it. God knows :) > > what does your spppcontrol call look like ? Are you sure that you've > specified CHAP ? It seems to be working now. But I'm not really sure why.. My spppcontrol had pap and still has pap spec'ed. Maybe I choose a bad day to test? Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isdn" in the body of the message