Fast answer from Spider Boardman spider_at_Orb.Nashua.NH.US hjelped me a
lot.
First the question I posted:
I'm trying to set up a PPP dial-out connection under Digital Unix 4.x. I
once successfully set up a PPP dial IN connection with DU 3.x and the
public domain ppp 2.2 software and a dial out connection with ppp 2.2 under
linux. The modem is an hayes compatible 'Presticom14.4 fax/data modem'. I'm
pretty sure it is set up OK. It is working well under windoze.
For some reason, it does not work.
Here is what I did:
1) Defined a simple modem in /etc/remote just to test basic connectivity
with the modem like this:
modem1:dv=/dev/tty00:br#38400:pa=none
I can 'tip modem1' without any problems and send commands to configure the
modem. I noticed on the console that I sometimes get an acerint: ace0:
input silo overflow: 63
The command file /dev/tty00 gives me:
/dev/tty00: character special (35/0) ACE_SLU #0 terminal #0 errors =
28/0 mo
dem_control off
(BTW, what is this error=28/0 stuff ?)
When I try to use pppd and chat to dial-out, I issue the following command:
pppd /dev/tty00 38400 connect `chat -v -f chat-script`
My script hangs ! Here is the script as well as what gets logged by syslogd
(I used the local2.debug syslog.conf option, and DEC does not tell you that
the ppp they ship is compiled with debug) nothing shows with daemon.debug
so I had to use local2.debug...
Content of chat-script:
ABORT BUSY \
ABORT 'NO CARRIER' \
"" ATZ OK
ATDT96438386 CONNECT \
name: MyUsername \
CODE: MyPassword
As you can see, at this point, I just want to connect to the host, other
configurations issues will be solved later.
Here is syslogd output:
Nov 4 13:12:09 QDIS01 chat[4432]: abort on (BUSY)
Nov 4 13:12:09 QDIS01 chat[4432]: abort on (NO CARRIER)
Nov 4 13:12:09 QDIS01 chat[4432]: send (ATZ^M)
Nov 4 13:12:09 QDIS01 chat[4432]: expect (OK)
Nov 4 13:12:54 QDIS01 chat[4432]: alarm
Nov 4 13:12:54 QDIS01 chat[4432]: Failed
Nov 4 13:12:54 QDIS01 pppd[4417]: pppd started by root, uid 0
Nov 4 13:12:55 QDIS01 pppd[4417]: Connect script failed
Nov 4 13:12:55 QDIS01 pppd[4417]: Exit.
The modem does not reply OK to the ATZ string that I send and it times out.
What is wrong ? If I use tip, I can type the ATZ command and I receive the
OK string. Do I have to put a \r after the ATZ I send ?
Ohter question: Is there a way to use environment variables in the chat
scripts ? We are using a SecureID server and the password is never the same
for each connection, I would like to put it in an environment variable
before calling the script.
Thanks !
P.S.: If you can send me some chat scripts examples, I would be happy.
----------------------------------------------------------------
Solutions:
1- About the acerint: ace0 input silo overflow: 63
I searched the archives and found out that it is normally related to the
fact that the serial port is not set to use crtscts (hardware handshaking).
This message appeared when I used tip to try to dial out. To fix that, you
can use something like
'stty -f /dev/tty00 crtscts' before useing the device (with tip for
example). It will stay configured like that until you reset it or the next
reboot (Better put it in a script before using it)
Spider also suggested the following but I did not have to go to these
extremes:
"The input silo overflows are partly hardware. To avoid this, use
the options "modem" and "crtscts" in the options file (or on the
command line). I also recommend the "lock" option, to keep tip
away from the line while PPP is running.
There's also a possibility of losing data because of not enough
clists. Check what "sysconfig -q bsd_tty" has to say. The
default is only 120 clists, which is OK for a user typing at
/dev/console, but is woefully inadequate for PPP (or slip).
# sysconfig -q bsd_tty
bsd_tty:
nclist = 6000
I've upped it to 6000 for this site. Note that simply editing
the /etc/sysconfigtab file is not supported (even though it
usually works). To change this value the supported way:
# sysconfigdb -l bsd_tty > /tmp/xx
# test -s /tmp/xx || sysconfig -q bsd_tty > /tmp/xx
# ex - /tmp/xx <<\X
g/nclist/s/[0-9][0-9]*/6000/
x
X
# sysconfigdb -m -f /tmp/xx
# rm -f /tmp/xx
Unforunately, for the change to take effect you have to reboot."
2- My other problem:
I used backticks instead of quotes ! Using quotes gave way to another
problem that I discovered: I taught that pppd was doing nothing, in fact is
forks in the background (without telling you) and runs chat (or whatever
you told it to do after the connect option)
The subtelty is that when you specify a chat script to run, give the WHOLE
PATH to the file or the chat command (which runs in another shell) won't
find it (I assumed it would find it in the current directory but that did
not work)
Thanks !
Received on Tue Nov 04 1997 - 23:22:35 NZDT