On Thu, 8 Apr 1999, Dr. Nagarjuna G. wrote:
>> Again, what was process 1718? Is it terminating abnormally?
> I found out that this process is `sh /usr/bin/pon', a script that
> contains the following:
> #!/bin/sh
> /usr/sbin/pppd call ${1:-provider}
And that's exactly your problem. Unfortunately, you can't simply call
your existing pppd setup; with diald you have to be more selective. Your
connect script can't start pppd, instead it should call the provide, log
in, provide passwords, etc., without starting pppd.
If you look in your /etc/ppp/peers directory, you may see an entry for
your provider. That entry will refer you to a chat script, perhaps in
/etc/chatscripts with the same name. You may be able to use that as your
connect script. If not, or if you can't find it, you'll have to write
your own. It isn't hard.
You will also have to remove almost everything from /etc/ppp/options,
things such as lock, defaultroute, etc. Consult the diald documentation
for a complete list.
> As you rightly guessed diald is not aware of the established
> connection. Could it because it is listening on some other port or
> some thing. I have looked at the file standard-filter, which has a
> number of `120' strings, possibly referring to timout settings. I
> could not understand the meanings. I am sending this file as an
> attachment. I clearly see we are heading somewhere. Thanks.
I guess pppd is starting, routing the packets right past diald, diald
doesn't see anything and closes the idle link down after 120 seconds.
This may be happening because pppd is taking the defaultroute option,
among other problems.
Ed
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
