Check the man file for diald. I have been using the impulse option to
keep a connection up for a prescribed period of time (5 minutes in my
case - impulse 300,0,0). As long as you set your impulse time less than
your ISP's timeout you should be fine. By default diald looks like it
times out an idle connection that has had zero packets processed in two
minutes.
Bob
Mark Johnson wrote:
> Diald seems to want to keep connected at all times.
>
> When the connection has been inactive for about 25 minutes, it appears
> that my ISP drops the connection. Immediately, diald redials the ISP.
> For example, here's a typical sequence
> 1. Kill and restart diald ("/usr/sbin/diald debug 0x009c -daemon") on
> my linux gateway/BIND nameserver/firewall; diald does not connect.
> 2. Run Netscape 4.5 from a connected NT box, and diald connects.
> 3. Close Netscape.
> 4. After a while, I get logged messages like:
> May 27 11:52:50 linuxbox diald[4158]: Link died on remote end.
> May 27 11:52:54 linuxbox diald[4158]: Running connect (pid=4687).
>
> I'd like to get diald configured so that when my ISP drops the
> connection, diald doesn't bring it up again until needed. Better yet,
> I'd like to hangup from my end if there has been no significant
> activity for, say, 10 minutes.
>
> In order to understand what's happening, I'd like to examine diald's
> activities in detail. However, I've been unable to figure out how to
> run diald so that I can see the packets its receiving, the rules it
> applies to the packets, and what "connection identities" are in the
> "connection set" at the time of the redial.
>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
