Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 247
  • Last Modified:

CHAT PROBLEMS

I HAVE A PROBLEM MAKING MY MODEM DIAL UP MY INTERNET CONNECTION PROPERLY. WHEN I CALL UP MY INTERNET SERVICE, THERE IS NO RESPONSE. I HAVE TRIED DIALING UP THROUGH MINICOM AND THEN START PPPD, AND THAT WAY IT WORKS. IT SEEMS LIKE IT SOMEHOW IS MY PPP-ON SCRIPT THAT IS WRONG. MY PPP-ON SCRIPT AND THE CHATSCRIPT ARE LOOKING AS FOLLOWING:
PPP-ON SCRIPT:
LOCKDIR=/var/spool/lock
DEVICE=modem
PHONE=********
USER=************
PASSWORD=********
OUR_IP_ADDR=0.0.0.0

if [ -f $LOCKDIR/LCK..$DEVICE ]
then
      echo "PPP device is locked"
      exit 1
fi

fix-cua $DEVICE
(
      stty 115200 -tostop

      if chat -v -f/usr/local/bin/chatscript
      then
      pppd asyncmap 0 -detach modem crtscts mru 1500 $OUR_IP_ADDR: /dev/$DEVICE
      rm -f LCK..$DEVICE
      exit 0
      else
            echo "PPP call failed" 1>&2
            exit 1
      fi
) < /dev/$DEVICE > /dev/$DEVICE

Chatscript:
ABORT
'NO CARRIER'
ABORT BUSY ''
ATZ OK
ATDT********
CONNECT ''
username: ************
password: \\q********
annex:ppp

The problem has occured after I upgraded my linux from 1.2.13 to 2.0.0. Beforehand I used almost the same ppp-on script just with the chatscript options as parameters using -l to the chat command, and that worked quite fine.
I hope you have a good answer to my question.

Bjarne
0
bjarne
Asked:
bjarne
1 Solution
 
mart010897Commented:
Hi,

Uh, you just upgraded the kernel and not the distribution right?  

Okay, well I'm going to be guessing without any debug output here... try doing a tail -f /var/adm/messages and a tail -f /var/adm/syslog in two other consoles when you run your pppd script to see any errors as they are produced.

I had a similar problem not too long ago and it turned out that it was because my ISP had switched to Unnumbered PPP without telling anyone.  Try using a bogus pair of addresses like 10.0.0.1:10.0.0.2 on your pppd commandline and then specify ipcp-accept-local and ipcp-accept-remote.

Also if this is working through minicom but not through your script setup, I would suggest writing your own ppp dialer script, one which specifies the commands in-line, since you probably know the sequence by heart now because of minicom :)

Something like:

pppd connect 'chat -v "" atdt******* ONNECT "" rname: ******** ssword: ******** nnex: ppp' asyncmap 0 modem /dev/modem crtscts debug 10.0.0.1:10.0.0.2 ipcp-accept-local ipcp-accept-remote

Then just watch /var/adm/messages scroll by for a monitor of what's going on.  Could be that the problem is in your chat script and the inline thing will fix it for now.  Once you get that long line right you can put it in a sh script, no problem.

If it seems like chat is getting through ok, and pppd takes over (some message like connect ppp0 <-> /dev/modem or something), then you still have problems, then the answer will most likely lie in /var/adm/debug.  Try making this file only one line long using your favorite editor so you know you'll only have output for the currently attempting connection.  Then post or mail the output to me and we can go over it.

I know it's a pain, but a really good understanding of pppd is the best weapon in this type or trouble... and I just don't like the ppp-on scripts that come with slackware... doing it yourself you can familiarize yourself with the sequence of events that is happening to establish your PPP connection.

Hope this helps, feel free to mail me directly...

Mart
mart@voicenet.com
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now