On 2006-01-14, Clifford Kite <(E-Mail Removed)> wrote:
> To even get started we need the chat and pppd scripts and the chat -v
> and pppd debug logs. Add debug to the pppd options and the line
> daemon.*;local2.* /var/log/ppp.log
> to /etc/syslog.conf, and do "killall -HUP syslogd" to make syslogd
> reread syslog.conf. Then try to connect and post exact copies of
> the scripts and log for the attempt.
>
> (It's likely to be harder than you expect to get things working since
> cell-phone PPP implementations are generally not well-written and
> different cell-phones require different chat and pppd configurations.)
>
I wen't through this same problem with Slackware and a AT&T
Wireless phone some time ago. I didn't get very far as they wanted to
use a MULTICAST address (aRGH!) But I can give the OP some clues
1. Most Cell ISPs don't want your username/password in their
authentication sessions. They know who you are based on your SIM card
info. In the case of AT&T your PAP password and username entries
would be set to a NULL entry (I believe use you use an '*' in both
fields of pap-secrets.
If you CAN authenticate and it tries to give you a multicast
addresss. UGH! you would need to read up on the multicasting howto
and possibly modify pppd and the kernal to allow for it.
I got Alltel now for my cellular service and I haven't begun
to figure out how to access this CDMA service yet. Did dial ATD#777
from minicom (as Alltel customer suport said to do). got NO ppp type
login session clues. just a connect message. Suposedly they use BREW
(what on earth is that? An alcholic beverage? one that the coder
drinks during debugging?

)
--
From the Desk of the Sysop of:
Planet Maca's Opus, a Free open BBS system. Not yet back online
The New Cnews maintainer
B'ichela