Need some PPP help

Embarrassingly, I was a big time PPP user many years ago (1995-2000),
but I forgot a lot.

I am trying to get my internet access work through PPP/CHAP using a
Motorola cell phone.

I finally got to the point of being able to link to the phone via
bluetooth, set up a ppp configuration file and chat file, as well as
username and password.

My problem is that AS SOON AS AUTHENTICATION SUCCEEDS, MODEM HANGS UP!
Why would that be?

Here is the log file

root:/etc/ppp/peers ###pppd call cingular
Mar 14 13:46:59 localhost pppd[7290]: pppd 2.4.4 started by ichudov,
uid 0
Mar 14 13:46:59 localhost hcid[6552]: link_key_request
(sba=00:0B:0D:0B:82:5B, d
ba=00:19:2C:0B:8B:58)
Mar 14 13:47:07 localhost chat[7295]: send (ATZ^M)
Mar 14 13:47:07 localhost chat[7295]: expect (OK)
Mar 14 13:47:07 localhost chat[7295]: ATZ^M^M
Mar 14 13:47:07 localhost chat[7295]: OK
Mar 14 13:47:07 localhost chat[7295]: -- got it
Mar 14 13:47:07 localhost chat[7295]: send
(AT+CGDCONT=1,IP,isp.cingular^M)
Serial connection established.
Using interface ppp0
Connect: ppp0 <--> /dev/rfcomm0
Mar 14 13:47:07 localhost chat[7295]: expect (OK)
Mar 14 13:47:07 localhost chat[7295]: ^M
Mar 14 13:47:07 localhost chat[7295]: AT+CGDCONT=1,IP,isp.cingular^M^M
Mar 14 13:47:07 localhost chat[7295]: OK
Mar 14 13:47:07 localhost chat[7295]: -- got it
Mar 14 13:47:07 localhost chat[7295]: send (ATD*99#^M)
Mar 14 13:47:08 localhost chat[7295]: expect (CONNECT)
Mar 14 13:47:08 localhost chat[7295]: ^M
Mar 14 13:47:08 localhost chat[7295]: ATD*99#^M^M
Mar 14 13:47:08 localhost chat[7295]: CONNECT
Mar 14 13:47:08 localhost chat[7295]: -- got it
Mar 14 13:47:08 localhost chat[7295]: send (^M)
Mar 14 13:47:08 localhost pppd[7290]: Serial connection established.
Mar 14 13:47:08 localhost pppd[7290]: Using interface ppp0
Mar 14 13:47:08 localhost pppd[7290]: Connect: ppp0 <--> /dev/rfcomm0
PAP authentication succeeded
Mar 14 13:47:09 localhost pppd[7290]: PAP authentication succeeded
Modem hangup
Connection terminated.
Mar 14 13:47:11 localhost pppd[7290]: Modem hangup
Mar 14 13:47:11 localhost pppd[7290]: Connection terminated.
besm6:root:/etc/ppp/peers ###Mar 14 13:47:12 localhost pppd[7290]:
Exit.


here's the options file:

root:/etc/ppp/peers ###cat cingular
/dev/rfcomm0 115200

connect '/usr/sbin/chat -v -f /etc/ppp/chat-cingular'
crtscts
modem -detach
noccp
#defaultroute
#usepeerdns
#auth
ipcp-accept-remote
ipcp-accept-local
noipdefault
user myusername
password mypassword


any ideas?

i

Ignoramus24277 <(E-Mail Removed)> wrote:
> Embarrassingly, I was a big time PPP user many years ago (1995-2000),
> but I forgot a lot.

> I am trying to get my internet access work through PPP/CHAP using a
> Motorola cell phone.

Don't be embarrassed, PPP/GPRS is significantly different from
landline PPP.

> I finally got to the point of being able to link to the phone via
> bluetooth, set up a ppp configuration file and chat file, as well as
> username and password.

> My problem is that AS SOON AS AUTHENTICATION SUCCEEDS, MODEM HANGS UP!
> Why would that be?

Good question, but one with several possible answers.

> Here is the log file

> root:/etc/ppp/peers ###pppd call cingular
> Mar 14 13:46:59 localhost pppd[7290]: pppd 2.4.4 started by ichudov,
> uid 0
> Mar 14 13:46:59 localhost hcid[6552]: link_key_request
> (sba=00:0B:0D:0B:82:5B, d
> ba=00:19:2C:0B:8B:58)
> Mar 14 13:47:07 localhost chat[7295]: send (ATZ^M)
> Mar 14 13:47:07 localhost chat[7295]: expect (OK)
> Mar 14 13:47:07 localhost chat[7295]: ATZ^M^M
> Mar 14 13:47:07 localhost chat[7295]: OK
> Mar 14 13:47:07 localhost chat[7295]: -- got it
> Mar 14 13:47:07 localhost chat[7295]: send
> (AT+CGDCONT=1,IP,isp.cingular^M)
> Serial connection established.
> Using interface ppp0
> Connect: ppp0 <--> /dev/rfcomm0
> Mar 14 13:47:07 localhost chat[7295]: expect (OK)
> Mar 14 13:47:07 localhost chat[7295]: ^M
> Mar 14 13:47:07 localhost chat[7295]: AT+CGDCONT=1,IP,isp.cingular^M^M
> Mar 14 13:47:07 localhost chat[7295]: OK
> Mar 14 13:47:07 localhost chat[7295]: -- got it
> Mar 14 13:47:07 localhost chat[7295]: send (ATD*99#^M)
> Mar 14 13:47:08 localhost chat[7295]: expect (CONNECT)
> Mar 14 13:47:08 localhost chat[7295]: ^M
> Mar 14 13:47:08 localhost chat[7295]: ATD*99#^M^M
> Mar 14 13:47:08 localhost chat[7295]: CONNECT
> Mar 14 13:47:08 localhost chat[7295]: -- got it
> Mar 14 13:47:08 localhost chat[7295]: send (^M)
> Mar 14 13:47:08 localhost pppd[7290]: Serial connection established.
> Mar 14 13:47:08 localhost pppd[7290]: Using interface ppp0
> Mar 14 13:47:08 localhost pppd[7290]: Connect: ppp0 <--> /dev/rfcomm0
> PAP authentication succeeded
> Mar 14 13:47:09 localhost pppd[7290]: PAP authentication succeeded
> Modem hangup

One of the weird things about PPP/GPRS is that while a PPP authentication
is usually required the real authentication almost always takes place
afterwards at a level below PPP.

> Connection terminated.
> Mar 14 13:47:11 localhost pppd[7290]: Modem hangup
> Mar 14 13:47:11 localhost pppd[7290]: Connection terminated.
> besm6:root:/etc/ppp/peers ###Mar 14 13:47:12 localhost pppd[7290]:
> Exit.


> here's the options file:

> root:/etc/ppp/peers ###cat cingular
> /dev/rfcomm0 115200
>
> connect '/usr/sbin/chat -v -f /etc/ppp/chat-cingular'
> crtscts
> modem -detach
> noccp
> #defaultroute
> #usepeerdns
> #auth
> ipcp-accept-remote
> ipcp-accept-local
> noipdefault
> user myusername
> password mypassword


> any ideas?

You can _try_ adding local and novj to the peers file. The first is to
compensate for a less than full RS-232 line and the second to compensate
for a minimal PPP implementation. See man pppd for details.

To generate and capture PPP link negotiation messages add debug to the
peers file, and then add

daemon.*;local2.* /var/log/ppp.log

to /etc/syslog.conf followed by "killall -HUP syslogd" to make syslogd
reread syslog.conf. The messages are sent to ppp.log and might provide
some insight for other changes in the peers configuration.

Or google for something like PPP+Linux+Cingular and you may find better
suggestions. Or, maybe, someone on comp.protocols.ppp could help.

Note that I've never run PPP over GPRS and since you are reading this
it means there was no obviously better response within 24 hours of your
posting time.

> i

--
Clifford Kite
/* Bluffing in a poker game can win big; bluffing in a newsgroup
only attracts sharks. */

On Thu, 15 Mar 2007 14:45:23 -0500, Clifford Kite <(E-Mail Removed)> wrote:
> Ignoramus24277 <(E-Mail Removed)> wrote:
>> Embarrassingly, I was a big time PPP user many years ago (1995-2000),
>> but I forgot a lot.
>
>> I am trying to get my internet access work through PPP/CHAP using a
>> Motorola cell phone.
>
> Don't be embarrassed, PPP/GPRS is significantly different from
> landline PPP.
>
>> I finally got to the point of being able to link to the phone via
>> bluetooth, set up a ppp configuration file and chat file, as well as
>> username and password.
>
>> My problem is that AS SOON AS AUTHENTICATION SUCCEEDS, MODEM HANGS UP!
>> Why would that be?
>
> Good question, but one with several possible answers.

Thanks a lot. The real answer was that a customer service zombie put
me on a wrong plan, she did not provision me for PPP. The next day,
after just half an hour of talking to another customer service zombie
who was also reading from a wrong script (she was trying to convince
me that my cell phone was not able to work as a modem), I convinced
her to transfer me to someone else who had a bit more clue.

After the last rep changed my plan, everything works great.

The real problem is that phone companies hire complete retards to do
things that they are not capable of. They should let these people
handle simple questions like instant message plans, and hire a little
more expensive people handle internet questions.

i


>> Here is the log file
>
>> root:/etc/ppp/peers ###pppd call cingular
>> Mar 14 13:46:59 localhost pppd[7290]: pppd 2.4.4 started by ichudov,
>> uid 0
>> Mar 14 13:46:59 localhost hcid[6552]: link_key_request
>> (sba=00:0B:0D:0B:82:5B, d
>> ba=00:19:2C:0B:8B:58)
>> Mar 14 13:47:07 localhost chat[7295]: send (ATZ^M)
>> Mar 14 13:47:07 localhost chat[7295]: expect (OK)
>> Mar 14 13:47:07 localhost chat[7295]: ATZ^M^M
>> Mar 14 13:47:07 localhost chat[7295]: OK
>> Mar 14 13:47:07 localhost chat[7295]: -- got it
>> Mar 14 13:47:07 localhost chat[7295]: send
>> (AT+CGDCONT=1,IP,isp.cingular^M)
>> Serial connection established.
>> Using interface ppp0
>> Connect: ppp0 <--> /dev/rfcomm0
>> Mar 14 13:47:07 localhost chat[7295]: expect (OK)
>> Mar 14 13:47:07 localhost chat[7295]: ^M
>> Mar 14 13:47:07 localhost chat[7295]: AT+CGDCONT=1,IP,isp.cingular^M^M
>> Mar 14 13:47:07 localhost chat[7295]: OK
>> Mar 14 13:47:07 localhost chat[7295]: -- got it
>> Mar 14 13:47:07 localhost chat[7295]: send (ATD*99#^M)
>> Mar 14 13:47:08 localhost chat[7295]: expect (CONNECT)
>> Mar 14 13:47:08 localhost chat[7295]: ^M
>> Mar 14 13:47:08 localhost chat[7295]: ATD*99#^M^M
>> Mar 14 13:47:08 localhost chat[7295]: CONNECT
>> Mar 14 13:47:08 localhost chat[7295]: -- got it
>> Mar 14 13:47:08 localhost chat[7295]: send (^M)
>> Mar 14 13:47:08 localhost pppd[7290]: Serial connection established.
>> Mar 14 13:47:08 localhost pppd[7290]: Using interface ppp0
>> Mar 14 13:47:08 localhost pppd[7290]: Connect: ppp0 <--> /dev/rfcomm0
>> PAP authentication succeeded
>> Mar 14 13:47:09 localhost pppd[7290]: PAP authentication succeeded
>> Modem hangup
>
> One of the weird things about PPP/GPRS is that while a PPP authentication
> is usually required the real authentication almost always takes place
> afterwards at a level below PPP.
>
>> Connection terminated.
>> Mar 14 13:47:11 localhost pppd[7290]: Modem hangup
>> Mar 14 13:47:11 localhost pppd[7290]: Connection terminated.
>> besm6:root:/etc/ppp/peers ###Mar 14 13:47:12 localhost pppd[7290]:
>> Exit.
>
>
>> here's the options file:
>
>> root:/etc/ppp/peers ###cat cingular
>> /dev/rfcomm0 115200
>>
>> connect '/usr/sbin/chat -v -f /etc/ppp/chat-cingular'
>> crtscts
>> modem -detach
>> noccp
>> #defaultroute
>> #usepeerdns
>> #auth
>> ipcp-accept-remote
>> ipcp-accept-local
>> noipdefault
>> user myusername
>> password mypassword
>
>
>> any ideas?
>
> You can _try_ adding local and novj to the peers file. The first is to
> compensate for a less than full RS-232 line and the second to compensate
> for a minimal PPP implementation. See man pppd for details.
>
> To generate and capture PPP link negotiation messages add debug to the
> peers file, and then add
>
> daemon.*;local2.* /var/log/ppp.log
>
> to /etc/syslog.conf followed by "killall -HUP syslogd" to make syslogd
> reread syslog.conf. The messages are sent to ppp.log and might provide
> some insight for other changes in the peers configuration.
>
> Or google for something like PPP+Linux+Cingular and you may find better
> suggestions. Or, maybe, someone on comp.protocols.ppp could help.
>
> Note that I've never run PPP over GPRS and since you are reading this
> it means there was no obviously better response within 24 hours of your
> posting time.
>
>> i
>

On Thu, 15 Mar 2007 15:05:58 -0500, Ignoramus12213 rearranged some
electrons to form:

>
>
> The real problem is that phone companies hire complete retards to do
> things that they are not capable of. They should let these people
> handle simple questions like instant message plans, and hire a little
> more expensive people handle internet questions.
>
> i
>
>

The people you talked to are probably not even in the US.

--
David M (dmacchiarolo)
http://home.triad.rr.com/redsled
T/S 53
sled351 Linux 2.4.18-14 has been up 10 days 22:50

On Fri, 16 Mar 2007 06:39:14 -0400, David M <(E-Mail Removed)> wrote:
> On Thu, 15 Mar 2007 15:05:58 -0500, Ignoramus12213 rearranged some
> electrons to form:
>
>>
>>
>> The real problem is that phone companies hire complete retards to do
>> things that they are not capable of. They should let these people
>> handle simple questions like instant message plans, and hire a little
>> more expensive people handle internet questions.
>>
>> i
>>
>>
>
> The people you talked to are probably not even in the US.
>

Your guess is insightful in general, but in this case, they all
sounded perfectly American.

i