Ben,
Based on your advice, I abandoned the scripts I was using and used the
connect script included with the diald source. (I would have used that
before, but I didn't have the source.) I had to modify it to include my
username, etc. and then also to get it to send a couple of returns that my
ISP expected. But, that seems to have gotten me up and running. Thanks
for your advice.
Now just one more thing. What do you use for a script to disconnect? I
have a small shell script that checks my email using fetchmail and then
sends my email using sendmail. The script I have been using shut down the
connection when sendmail completed. Right now, diald just waits a certain
length of time, and then shuts down automatically. I would like to get a
good disconnect script going so that diald will shut down immediately
after sendmail is finished. I guess that will also mean trying to find a
way to tell diald not to disconnect if there is other traffic (web
browsing, etc.) going on.
Cheers,
Sean
------------------
Theo. Sean Schulze
[EMAIL PROTECTED]
On Sat, 10 Oct 1998, Ben Williams wrote:
>
> Sean,
>
> I have a sneaking feeling that you are running a nested connect script
> here - hence the timeout. From your logs it looks to me as though the
> connect script has long completed when the 'connect script timed out'
> message appears. I think you are working too hard...
>
> Your diald.conf is:
>
> > local 0.0.0.0
> > remote 0.0.0.0
> > dynamic
> > defaultroute
> > # proxyarp
> > device /dev/ttyS3
> > lock
> > speed 38400
> > mtu 1524
> > connect /etc/suseppp/diald/dialdppp-up
> > disconnect /etc/suseppp/dialdppp-down
> > modem
> > crtscts
>
> So, to connect diald runs 'connect /etc/suseppp/diald/dialdppp-up'
>
> But this file contains _another_ connect command:
>
> > #!/bin/sh
> > #
> > # This script is adapted from the PPP HOWTO paragraph 15.2.
> > #
> > TELEPHONE=0620227780
> > # ACCOUNT=tschulze
> > # PASSWORD=mypassword
> > #
> > #
> > export TELEPHONE # ACCOUNT PASSWORD
> > #
> > #
> > DIALER_SCRIPT=/etc/suseppp/diald/dialdppp-up-dialer
> > #
> > #
> > exec /usr/sbin/pppd debug connect $DIALER_SCRIPT
>
> So the connect command is, in effect:
> 'connect pppd connect $DIALER_SCRIPT'
>
> So pppd is connecting, rather than diald. The diald connect command
> (the outer one) does not complete, because the pppd connect command
> completes first and locks the modem.
>
> The point? Well, I think the following change in diald.conf should
> crack it:
>
> connect /etc/suseppp/diald/dialdppp-up-dialer
>
> (There is a slight possibility that this will produce no dialling at
> all, due to the loss of modem location info. If that happens, you need
> to delete the '/usr/sbin/chat -v' line of the script and use
>
> connect "/usr/sbin/chat -v -f dialdppp-up-dialer"
>
> in diald.conf . You may also need to throw some quotes around
> things...)
>
> On the other hand, I could be missing the point entirely. *8)
>
> --
> (o_ Ben Williams _o)
> //\ [EMAIL PROTECTED] /\\
> V_/_ [EMAIL PROTECTED] _\_V
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
