[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Kernel rebuild



On Wed, 4 Nov 1998, Waif W. Urchin wrote:

> Sorry this reply took so long to post; I had to figure out how to get
> the ppp.log file created, then out of Linux and into Windows so I could
> share it with you.

Thats quite alright... :)

> The ppp.log file listed below contains two attempts from today.  The
> first attempt was done after a clean floppy install (ppp, slip, bsd
> compression, etc. all installed), but before running pppconfig to
> configure the CHAP stuff.  As such, the first attempt only contains the
> basic changes I made to both provider files to include the phone number
> of my ISP, my username and password.  That one at least says CONNECT at
> one point, then logs me off because (I think) the prompting is wrong in
> the chatscript provider (?  I'm guessing.)  Of course, my provider
> hasn't replied with the correct login prompts, and he said the board was
> run using CHAP anyways, so I'm lost (or he is?)  On this note, simply
> dialing the number via Procomm yields no prompts, just a blank screen,
> so I can't determine the prompts for myself using that method.
> 
> The second attempt was after running the pppconfig utility (which is
> almost identical in operation and the changes it makes to pppsetup
> (which I have tried as well) for those more familiar with that utility)
> to setup CHAP.
> 
> In addition to what you can ascertain from this file, please note I have
> tried running the later script as PAP, CHAP, using noauth, and auth, and
> it always comes out identical to the listing.

A couple of things, are you using 'user <user>' in your
/etc/ppp/peers/provider ?? The <user> should be the same as your login at
your ISP, and you should put a line in /etc/ppp/pap-secrets like so:

<user>       *      <password>

(there are directions in that file - check chap-secrets too.)

This should get your authentication working, although I dont know if that
is what is needed.

Secondly, have you tried dialing your ISP with a program such as minicom
to see if there is in fact a login prompt you must use?

> Again, any assistance would be greatly appreciated.

No problems.
 
> No pppconfig:
> 
> Nov  4 18:57:18 Debian pppd[152]: pppd 2.3.5 started by root, uid 0
> Nov  4 18:57:19 Debian chat[153]: abort on (BUSY)
> Nov  4 18:57:19 Debian chat[153]: abort on (NO CARRIER)
> Nov  4 18:57:19 Debian chat[153]: abort on (VOICE)
> Nov  4 18:57:19 Debian chat[153]: abort on (NO DIALTONE)
> Nov  4 18:57:19 Debian chat[153]: send (ATDT*70,3251981^M)
> Nov  4 18:57:19 Debian chat[153]: expect (ogin)
> Nov  4 18:57:40 Debian chat[153]: ^M
> Nov  4 18:57:40 Debian chat[153]: CONNECT 24000/ARQ/V34/LAPM/V42BIS^M
> Nov  4 18:58:04 Debian chat[153]: alarm
> Nov  4 18:58:04 Debian chat[153]: Failed
> Nov  4 18:58:04 Debian pppd[152]: Connect script failed
> Nov  4 18:58:36 Debian chat[174]: abort on (BUSY)
> Nov  4 18:58:36 Debian chat[174]: abort on (NO CARRIER)
> Nov  4 18:58:36 Debian chat[174]: abort on (VOICE)
> Nov  4 18:58:36 Debian chat[174]: abort on (NO DIALTONE)
> Nov  4 18:58:36 Debian chat[174]: send (ATDT*70,3251981^M)
> Nov  4 18:58:36 Debian chat[174]: expect (ogin)
> 
> After pppconfig:
> 
> Nov  4 19:09:50 Debian pppd[222]: pppd 2.3.5 started by root, uid 0
> Nov  4 19:09:51 Debian chat[223]: abort on (BUSY)
> Nov  4 19:09:51 Debian chat[223]: abort on (NO CARRIER)
> Nov  4 19:09:51 Debian chat[223]: abort on (VOICE)
> Nov  4 19:09:51 Debian chat[223]: abort on (NO DIALTONE)
> Nov  4 19:09:51 Debian chat[223]: abort on (NO ANSWER)
> Nov  4 19:09:51 Debian chat[223]: send (ATZ^M)
> Nov  4 19:09:51 Debian chat[223]: expect (OK)
> Nov  4 19:09:51 Debian chat[223]: ^M
> Nov  4 19:09:51 Debian chat[223]: OK
> Nov  4 19:09:51 Debian chat[223]:  -- got it
> Nov  4 19:09:51 Debian chat[223]: send (ATDT*70,3251981^M)
> Nov  4 19:09:52 Debian chat[223]: expect (CONNECT)
> Nov  4 19:09:52 Debian chat[223]: ^M
> Nov  4 19:10:14 Debian chat[223]: ^M
> Nov  4 19:10:14 Debian chat[223]: CONNECT
> Nov  4 19:10:14 Debian chat[223]:  -- got it
> Nov  4 19:10:14 Debian chat[223]: send (\d)
> Nov  4 19:10:15 Debian pppd[222]: Serial connection established.
> Nov  4 19:10:16 Debian pppd[222]: Using interface ppp0
> Nov  4 19:10:16 Debian pppd[222]: Connect: ppp0 <--> /dev/ttyS1
> Nov  4 19:10:16 Debian pppd[222]: sent [LCP ConfReq id=0x1 <asyncmap
> 0x0> <magic 0xffffa021> <pcomp> <accomp>]
> Nov  4 19:10:43 Debian last message repeated 9 times
> Nov  4 19:10:46 Debian pppd[222]: LCP: timeout sending Config-Requests
> Nov  4 19:10:46 Debian pppd[222]: Connection terminated.
> Nov  4 19:10:46 Debian pppd[222]: Hangup (SIGHUP)
> Nov  4 19:10:46 Debian pppd[222]: Exit.
> 
> 
> Waif
> 
> 
> 
> 
> -- 
> Unsubscribe?  mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
> 
> 
> 


                       Michael Beattie (mickyb@es.co.nz)

               PGP Key available, reply with "pgpkey" as subject.
 -----------------------------------------------------------------------------
                Mulder: Could say the guy was running on empty.
 -----------------------------------------------------------------------------
                Debian GNU/Linux....  Ooohh You are missing out!



Reply to: