I couldn't find anything quite like this in the archive, so... here goes. I'm trying to add DialD to a working PPPD setup. For DialD, I'm using the stock config files from the DialD package. For PPPD, I'm using the chat script and options that I've been using for months with PPPD alone (though I've transferred the PPPD options (MTU, etc...) that the DialD docs recommend from my PPPD config over to my DialD config). I'm running RedHat 5.2 and the latest DialD version (sorry, forgot the revision number, and the computer is at work). So... The problem: I start DialD from the command line (it defaults to being a daemon). Chat dials the modem, and apparently establishes a connection. PPPD starts up and connects to the modem device (/dev/cua1). Before PPPD establishes local and remote IP addresses, though (as it usually does at this point, when I'm not using DialD), PPPD says that it received a hangup signal, and hangs up the modem. DialD then pulls down the routes it established, and gets ready to retry. I tried increasing all of the time-outs to values far beyond what the above sequence takes. I also thought DialD might be hanging up because of no traffic, but at this point, the whole process is maybe 30 or 45 seconds old and I also added an "up" command to my diald.conf which, I believe, forces the link to be permanently up. Any ideas about what could be causing this or about what I might investigate to learn more? (I didn't want to post all of my config files in their entirety, so I'd also appreciate advice as to what information might be helpful for diagnosing my problem.) Thanks, Marc _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
