On Sun, 18 Oct 1998, Talmon Reiss wrote:
> I am running IP Masq and diald together. It works fine except the diald
> does not shutdown the pppd after the timeout period for no activity is
> reached. This is the case with both windows and linux clients. If,
> however, my connection request comes from the linux machine with the
> diald running on it, the timeout does work. Am I missing some kind of
> disconnect script?
When you say it doesn't shutdown after the timeout, do you mean after the
timeout you expect to see or does the monitor information actually show no
live connections? There's a more or less known problem that some of us
have seen and discussed: what happens is that the masqueraded connections
don't get their timer reset on close, so diald waits longer than you'd
expect after (say) you shutdown telnet than it should. But at least IME
it does eventually shutdown. There have been some proposed "fixes" for
this, but I don't have anything handy to post.
One other thing that checking the monitor will show you that you might
want to look at. Last evening, our dial-up link stayed up all night long
because a browser was left running. The page it was displaying had,
unbeknownst to the user, some advertising crap that caused the broiwser to
refresh the ad(s) every six minutes. Luckily, the refresh interval was
shorter than the http-port timeout I have set, and the account has a
generous monthly connect time cap that this won't hurt us. If it had been
redialing ten times an hour for this unwanted junk... well, those nickles
do add up after a while. ;-(
Luck!
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
