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

Re: /etc/chatscripts/provider



Problem fixed-------I had first run pppconfig and later tried to edit /etc/chatscripts/provider and /etc/ppp/peers/provider files not realizing that pppconfig
had already taken care of those files.  My 'editing'
messed up things.

I cleaned out the two files plus pppconfig and started
fresh on pppconfig.  I checked the two files and sure enough
pppconfig had entered the data there.

ISP log on is fine now, gnome's monitor applet shows data send/receive is working and the net is accessible. Now I can put apt to work.

Incidently, I have two installations of Debian on this computer (one,for trouble shooting). I wasn't able to log on with either one because of my unnecessary 'editing'. Why don't THEY tell us these things?

Thanks, guys

Alex

Donald Spoon wrote:
alex wrote:

I had no problem configuring /etc/chatscripts/provider in Progeny Debian but the one in Debian Woody has a different
format that gives me a problem. I can't figure out what
kind of data should be entered and how it should be entered.
I couldn't find any info about this.


1.  What data should be entered?  Examples would be helpful.

2.  Should the # be removed and the data entered on the same
line or should the the original # be retained and the data entered on the next line without a # ?


--/etc.chatscripts/provider----------------------------
# This chatfile was generated by pppconfig 2.0.10.
# Please do not delete any of the comments.  Pppconfig needs them.
#
# ispauth PAP
# abortstring
ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT DELAYED
# modeminit
'' ATZ
# ispnumber      <Something in addition to the phone number?
# ispconnect
# prelogin
# ispname        < Quite sure what goes here
# isppassword    <   "     "    "    "    "
# postlogin
# end of pppconfig stuff


By far the easiest way to get the /etc/chatscripts/provider file is to run the pppconfig program and fill in the blanks. This will generate the appropriate script automatically. If it doesn't work after this, THEN you consider editing the file rather than starting from scratch. From the example provided, it appears you have not done the initial stuff but are starting with the original file. Here is a "fake" chatscript I just generated as an example of what worked for me:

# This chatfile was generated by pppconfig 2.1.
# Please do not delete any of the comments.  Pppconfig needs them.
#
# ispauth PAP
# abortstring
ABORT BUSY ABORT 'NO CARRIER' ABORT VOICE ABORT 'NO DIALTONE' ABORT 'NO DIAL TONE' ABORT 'NO ANSWER' ABORT DELAYED
# modeminit
'' ATZ
# ispnumber
OK-AT-OK ATDT1234567 <--- new line added
# ispconnect
CONNECT \d\c <--- new line added
# prelogin

# ispname
# isppassword
# postlogin

# end of pppconfig stuff

Note the items added to your example. In addition to generating the appropriate /etc/chatscripts/provider file, pppconfig also sets up your PAP/CHAP authentication and the /etc/ppp/peers/provider files. The pppconfig program is your friend and will save you a lot of hair-pulling and de-bugging, IMHO.

Cheers,
-Don Spoon-








Reply to: