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]
