Hullo:
> I have been doing some research. In general, ppp problems fall into four
> broad areas:
>
> 1. physical installation of modem
> wrong serial port, it's a winmodem, setserial config needed, IRQ
> conflicts, pnp not set up, linmodem drivers not installed
Modem works fine. It's been recognized by the system; it works with kppp
without troubles; if I launch pppd manually from the command line it works
too.
> 2. misconfiguration
> typos in username, password, chat script; missing info; incorrect DNS
> config
Nothing changed there. As I said, it works fine in kppp. I've been over the
config stuff 20 times...
I should note that we started having failures after a dirty shutdown -- but
I have NO idea where to look for damage...
> 3. authentication
> wrong protocol selected, incorrect implementation of PPP on the ISP's
> end, weird app behavior (subtle changes in ppp, kppp, etc.)
But why does it work when you don't run it from the script?
> 4. hardware failure
> it's just broken
Doesn't seem likely - the hardware works with everything else...
> I suspect the trouble here falls into area #3, and there are plenty of
posts
> to the Mandrake usenet group that mirror this problem. The solution is to
> use "debug" and minicom to gather as much ionf about the connection as
> possible.
You're probably right... but it's all very nebulous... somebody has got to
know more about what's going on here...
And again -- that SIGHUP is damn peculiar -- who is sending it?
-Stephen-