chat will not send password
I have been attempting for some time to establish a ppp connection with my internet service provider. There are many ways to do this depending upon which document I consult (NET-3-HOWTO, ISP-Hookup-HOWTO, DIP man pages, Debian User's Guide, ad nauseam). Currently I am trying to directly invoke the pppd and use a chatscript as described in the Debian User's Guide. I have the correct port, dial the number, correctly log in my user name, but chat will not send my password at the Password prompt given by my ISP.
Here is my chatscript (not my real password, though):
ABORT "NO CARRIER"
ABORT BUSY
ABORT "NO DIALTONE"
ABORT WAITING
"" AT&F\r
OK AT&D2&C1\r
OK ATDT3810293
ogin: chipg\r
Password: zzzzzzz\r
Password: zzzzzzz\r
***end chatscript file***
By looking at the connect-errors file, which I believe is created because of the '-V' option I use to invoke chat I see that everything works up to 'login', but the expect part of the Password line doesn't work (I have of course tried assword:, ssword:, sword:, word: )
I have even tried inserting a REPORT Password statement, and chat duly reports that it sees Password, but the expect part doesn't work. If I add some more expect lines (as I have in the above version of my chatscript, where I simply expect Password again) I get "Invalid Login" and my password is supplied to a subsequent login prompt.
I tried for a couple of days to understand and use DIP (also to no avail). Although in DIP I was able to get into a terminal mode where I could manually login. The Password prompt comes directly after I hit the RETURN key to send my user ID. (no need for additional RETURN keys or BREAKs or anything that I can tell). The only thing Unique AND THIS MAY BE THE A LEAD TO THE SECRET is that my password is not echoed back.
To be honest I wouldn't mind manually logging in every time. Isn't there some simply way I can just have a manual terminal, log in myself, and have the pppd take over??
Or perhaps someone knows why chat won't work for me?
Thank You,
Chip Grandits
P.S.
Below is some excerpts from my connect-errors log generated by chat (I assume). Running commentary in <> added afterwards with text editor.
<Original Script, REPORT CONNECT and expect "ssword:" at the end>
AT&F
OK
AT&D2&C1
OK
ATDT3810293
CONNECT 31200/ARQchat: Jun 16 01:39:38 CONNECT 31200/ARQ
Front Range Internet, Inc.
Unauthorized Access is Prohibited.
Login:chipg
Password:
<Here you can see log shows password prompt but chat never gives response>
<added REPORT Password to really make sure Password is being received, expect Password twice at end>
AT&F
OK
AT&D2&C1
OK
ATDT3810293
CONNECT 31200/ARQ
Front Range Internet, Inc.
Unauthorized Access is Prohibited.
Login:chipg
Password: chat: Jun 16 01:54:35 Password:
<the 'chat...' I believe was actually written to stderr, not sent to serial port>
Invalid Login
Login:zzzzzzz
<here at least is my password in a subsequent login prompt - why wasn't it given where it is suppose to>
Password:
<OK - take out all REPORT statements, expect "Password;" only once at end>
AT&F
OK
AT&D2&C1
OK
ATDT3810293
CONNECT 31200/ARQ
Front Range Internet, Inc.
Unauthorized Access is Prohibited.
Login:chipg
Password:
<ISP simply hangs up on me as chat never sends my password>
<Put REPORT password back in, expect "Password:" only once at end>
AT&F
OK
AT&D2&C1
OK
ATDT3810293
CONNECT 31200/ARQ
Front Range Internet, Inc.
Unauthorized Access is Prohibited.
Login:chipg
Password:chat: Jun 16 02:01:53 Password:
<I suppose this is proof that 'chat...' goes to stderr as my ISP still waits for a password and eventually hangs up>
<script contains REPORT Password and uses secondary expect "Password:--Password: zzzzzzz" >
AT&F
OK
AT&D2&C1
OK
ATDT3810293
CONNECT 31200/ARQ
Front Range Internet, Inc.
Unauthorized Access is Prohibited.
Login:chipg
Password: chat: Jun 16 02:04:11 Password:
Invalid Login
Login:zzzzzzz
<WHY HERE, WHY NOT at password prompt!!!>
Password:
<ISP hangs up after taking my password at second login prompt>
<...Several dozen more attempts with various permutations - all futile>
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: