Dear friends,
I use diald 0.99.2 with kernel 2.2.10 (SUSE 6.2) and after about 1
or 2 days of normal operation, DIALD must be stopped and
restarted, otherwise it does not dial out. The demon seems to be
running when I issue the "ps x" command, the sl0 interface and the
proper routings are there, but no dialling takes place.
I use pppd and a dynamic ip address with IP masquerading with
the scripts that Mike Jardis proposes in DIALD 0.99.2
When this happens, /var/log/messages shows the following:
Jan 5 06:38:37 nest-0 --MARK--
Jan 5 07:11:35 nest-0 diald[42]: Trigger: tcp 44.154.8.11/1151
195.167.100.100/80
Jan 5 07:13:01 nest-0 diald[42]: Trigger: tcp 192.168.0.1/1035
128.54.16.7/21
Jan 5 07:15:36 nest-0 /usr/sbin/gpm[156]: No data
When I go to /sbin/init.d and execute "./diald stop" and then
"./diald start" all is back to normal until after 1 or 2 days later when
the same happens again.
Has anybody faced such a problem before and how did he solve it?
Any reply would be much appreciated.
73 Demetre SV1UY
Demetre Ch. Valaris - SV1UY,
IP Coordinator for AMPRnet in Greece.
e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]
PBBS MAIL: [EMAIL PROTECTED]
---------------------------------------------------------
Visit Athnet's WEB SERVER at http://www.athnet.ampr.org
or my homepage at http://www.athnet.ampr.org/~sv1uy
MIRROR page at http://users.forthnet.gr/ath/sv1uy
Need a PLUG & PLAY JNOSKIT? Try my homepage!
---------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
