Hi,
I saw your message on the debian mailing list, where you described your
problem with getting up diald.
Now, what is happening is your 'ppp-up' script. Diald is informing you
in the log, that it doesn't get a return code from this script. It never
returns to diald, so diald thinks that no connection has been made, and
thus terminates the line. Now, you might ask how come the connection works
and the answer to that is that that part is taken care off by pppd, which
you execute on your own in your 'ppp-up'.
You should remove the line in your 'ppp-up' script where you start the
execution of 'pppd'... that should do the trick.
If that doesn't work, you should change the 'ppp-up' script... or actually
bypass it. Which means you can clean up your 'ppp-dialer' script, so that it
contains only these parts for chat (i.e. not the 'chat -v' etc.):
ABORT BUSY
ABORT "NO CARRIER"
.
.
.
OK ATwDT...
^- if you are using your home line, this will wait for a carrier
. before dialing. That means your wife doesn't have to hear
. the loud sqeak on the line, if the computer decides to dial
. while she's on the phone.
asswd: "boo"
After this, you change the connect line in the diald.options file to
be something like:
connect "chat -f <file-containing-above-chat-code>"
You see, diald will start the 'pppd' itself after the connection has been
made... and set the netmask, the fake local and remote ip addresses and all
the rest... all the connect script has to do, is open the line to the
remote computer.
Hope this helps...
--
----------------------------------------------------------------------------
Ørn Einar Hansen [EMAIL PROTECTED]
[EMAIL PROTECTED]
fax; +46 035 217194
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
[EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED]
