> -----Original Message-----
> From: Mark Johnson [mailto:markj*no*spam*@gilanet.com]
> Sent: 27 May 1999 22:25
[snip]
> 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
[snip]
My ISP does not disconnect by itself, so I dont have a personal
experience with this problem.
So take this for what its worth.
> 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.
diald should do this automatically - my configuration does. If the
link is brought up, and there is no traffic for the first 120 secs,
the link is brought down. This typically happens for e.g. some
application doing a gethostbyname() (DNS-lookup).
If there is traffic, e.g. someone browsing the net, the link stays
up, but for no more than 5 minutes of inactivity. So if someone
goes to a site, and spends more than 5 minutes reading it, diald
will disconnect.
This works fine, and is almost diald default behaviour. I believe I
changed the default inactivity timeout from 2mins to 5mins.
> 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.
Run diald with 'debug 1' - this will enable logging of most of
what you're asking for.
regards,
Per Jessen, ENIDAN Technologies, London
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
