I am running diald on RedHat Linux 5.1 (kernel 2.0.32). I configure those
linux boxes as LAN Internet gateways for clients who wish to offer web
surfing to network clients. Apache proxy is used to facilitate the browsing
and all clients are masqueraded.
This works fine, except that occasionally, diald will dial out and simply
hang up (closing down idle link) without transmitting any packets. It will
then immediately (after modem reset delay) redial and repeat the entire
process for a long time until the system is reset. Restarting diald does
not resolve the issue.
This has been noticed when there are no other users on the network but one
machine which does an IMAP/POP poll of the linux box. Therefore there
should be no external IP traffic flowing.
This problem also manifests itself usually in the morning when users are
attempting to browse. While the system goes through its dial cycling
phases, everyone simply gets "proxy error" messages.
Normally, the system works flawlessly
Settings are as follows:
Initial commect: 60sec
http: 10min
ftp, etc: 45sec or kept the default setting
Can anyone point me in the right direction where I can correct this. Note
this happens on more than one system. In some cases, given time it
eventually works it out of its system, but this is costly as there is a
*hefty* connection charge both for online connection and telephone toll.
Another note: how do I get diald to report ist logs in local time instead of
GMT? This throws off my logging since PPP and all other processes use local
time.
Thanks much
Gerry George <[EMAIL PROTECTED]>
Remote Access Systems
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
