Howdy folks,
  I installed diald a few days ago, and I've noticed a possible problem.
As you can see, from the logs below, pppd is shutting down the link (based
on the idle-disconnect, that I'd specified in the options file.
  At first, I thought that diald didn't know this, and was interpreting
the closure of the connection as a failure.  However, I have the two-way
option specified, in diald.conf, and yet the connection restarted almost
immediately.
  I attempted to fix this, by removing the idle-disconnect, and telling my
ISP to drop the line, after 30 seconds idle time.  Again, diald decided to
restart the connection.  (the line dropped immediately, which I've seen
frequently - this could be a problem with my ISP who do have the
occasional problems, but this is happening quite frequently, and I suspect
it may be a diald problem.
  So, my question is this: is the two-way option working properly here??
am I mis-interpreting its intended use?

Oct 12 20:19:24 etheral pppd[787]: No IP frames received within idle time limit
Oct 12 20:19:25 etheral pppd[787]: Connection terminated.
Oct 12 20:19:25 etheral pppd[787]: Exit.
Oct 12 20:19:25 etheral diald[110]: Link died on remote end.
Oct 12 20:19:25 etheral diald[110]: Closed fwdfd
Oct 12 20:19:25 etheral diald[110]: Changed snoop device to sl0
Oct 12 20:19:28 etheral diald[110]: Running connect (pid = 885).
Oct 12 20:19:28 etheral chat[887]: timeout set to 3 seconds


-- 
Steve Sutton  [EMAIL PROTECTED]  "# I caused a major war, just by talking"
http://www.etheral.demon.co.uk (PGP key avail.)  [EMAIL PROTECTED]
       All opinions expressed are my own, and not representitive of
           The British Computer Society, or Demon Internet Ltd.


-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]

Reply via email to