On Fri, 08 Oct 1999, you wrote:
>Hi all!
>I'm new with diald, so perhaps I'll write some
>stupid things! Excuse me in advance ;-)
>
>Ok! I've installed diald on a Red Hat 6.0 linux box.
>It seems to run well: with all filters I set up (in standard.filter),
>I'm able to start the connection only when there is TCP traffic on
>eth0 (I've been able to stay quiet diald during DNS lookups).
>But I'd like to substitute completely our company "Wingate" system
>with Linux so my first think was about diald & dialmon.
>I just compiled dialmon (and installed dialm on Linux and the client
>for Win98). It seems to be able to drive diald connections via dialm,
>but during my experiments (with a modem not connected to the line) when
>I try a "UP LINK" and soon after a "DOWN LINK", I obtain that diald
>remains to try the connection indefinitively. WHY? I'd like to
>make a system which is able to START and DOWN connections at user command,
>just with my old Wingate. So I think my problem is some "timeout" paramater
>in a config file.
>
>Can you help me?
>
Does it do this if the modem is actually connected to the line. Up link
basically does "force-waitabit-unforce" where waitabit is 90 seconds
by default; down link just sends a "down" to diald. But, if diald cannot get the
connection, then i think it settles down into its 30-sec retry loop. I think
that if you did a "block" from dialm then it would shut up.
Regards
Mike (aka Mr. Dialmon)
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
