pppd would connect and then immediately disconnect,
as if authorization failed (I was using pap). I spent several
days trying different settings for the modem and every
possible setting in pppd.
The baffling part was that I could go into minicom and
dial the ISP (Linux friendly, btw) and immediately see
the ppp session start. NT would connect flawlessly,
and my telephone people were pretty sure the problem
was on my end.
After banging around for quite a while, a friend suggested
that I fire up minicom and quit with no reset, and fire
up a script with just the pppd call (no connect statement).
Here begins the baffling part - it works that way.
I can connect just fine, even with the exact same pppd
settings (just no connect with a chat script).
This leaves me rather puzzled, and I'm not alone. I've
searched a lot of the web for some solution that uses
straight pppd and chat and found no one with any
answers, so I'm asking this list. Maybe some clueful
individual out there can explain this.
My modem works great this way, but I'm missing one
of my favorite features of pppd - on demand dialing.
I figure I can get this back maybe by issuing a connect
that uses minicom and a script instead of chat (painful,
and likely unnecessary as well).
I'm willing to try and dig down until a solution is
found, or a bug, either way. I think that I'm not
alone and I'd like to write a HOWTO or something
for this problem if it will help.
Thanks for your time and consideration.
Sincerely,
Paul Ferris
-- Paul Ferris | http://linuxtoday.com | 330-875-2757 ------------------------------------------------------ Linux: Because a computer is a terrible thing to waste ------------------------------------------------------
