Problem with Verizon Broadband wireless PPP connection

Hi All,

I have been unable to connect to Verizon via their high-speed CDMA
1xevdo service. The problem seems
to be related to the ppp negotiation. I am running SuSE 8.2 on a
Toshiba Satellite Pro
running kernel 2.4.20-4GB. The Verizon card is the AirPrime 5220 and I
set it up sucessfully using the
instructions at http://www.ka9q.net/5220.html.

I have successfully connected at least three times, but most times,
immediately after what seems to be
a successful connect, I get a packet from Verizon requesting a
disconnect. For example

local IP address 166.180.55.131
remote IP address 66.174.120.134
primary DNS address 66.174.3.7
secondary DNS address 66.174.6.7
Script /etc/ppp/ip-up started (pid 7099)
Script /etc/ppp/ip-up finished (pid 7099), status = 0x0
rcvd [LCP TermReq id=0x5]
LCP terminated by peer
cbcp_lowerdown
Script /etc/ppp/ip-down started (pid 7160)
sent [LCP TermAck id=0x5]
Script /etc/ppp/ip-down finished (pid 7160), status = 0x0
Connection terminated.
Connect time 0.3 minutes.
Sent 145 bytes, received 106 bytes.

Here is what the log looks like
for a successful connection
http://www.celoso.net/pppd_verizon/ppp.1xevdo.good and here is what it
looks like
for an unsusccesful connection
http://www.celoso.net/pppd_verizon/ppp.1xevdo.bad. Lastly here are the
connection settings http://www.celoso.net/pppd_verizon/ppp.1xevdo.settings.

I cannot figure out what the problem here is. Sadly
when I contact Verizon, all they want to know is why I don't use their
windoze software (which does work - I just ddon't want to use
windoze).

Any clues, greatfully accepted.

Michael

Michael Hieb <michael_hieb@celoso.net> wrote:

> I have been unable to connect to Verizon via their high-speed
> CDMA 1xevdo service. The problem seems to be related to the ppp
> negotiation. I am running SuSE 8.2 on a Toshiba Satellite Pro
> running kernel 2.4.20-4GB. The Verizon card is the AirPrime
> 5220 and I set it up sucessfully using the instructions at
> http://www.ka9q.net/5220.html.

> I have successfully connected at least three times, but most times,
> immediately after what seems to be a successful connect, I get a
> packet from Verizon requesting a disconnect.
....

> Here is what the log looks like
> for a successful connection
> http://www.celoso.net/pppd_verizon/ppp.1xevdo.good and here is what it
> looks like
> for an unsusccesful connection
> http://www.celoso.net/pppd_verizon/ppp.1xevdo.bad. Lastly here are the
> connection settings http://www.celoso.net/pppd_verizon/ppp.1xevdo.settings.

The two remote connections have either different PPP implementations,
or configurations thereof. But it's quite clear that both want VJ
compression without connection ID compression - the 00 in <compress
VJ 0f 00>. Replace the pppd novj option with novjccomp and see if
that helps, but no guarantee - it's only a guess. That should allow
both connections to get the type of VJ they want and force pppd to
use it too.

You also might as well add the pppd option noccp since both the logs
show that the Verizon PPP implementation doesn't contain, or is not
configured to use, CCP. Even if the Verizon PPP did make CCP available,
it would be very unlikely to have CCP algorithm in common with pppd.

Strangely, the behavior of the Verizon PPP implementation for the good
connection is generally worse than the one for the bad connection.
The behavior of the SuSE modified pppd also appears to be below par.

> I cannot figure out what the problem here is. Sadly when I contact
> Verizon, all they want to know is why I don't use their windoze
> software (which does work - I just ddon't want to use windoze).

The help people at most ISPs have a list of questions and answers to
diagnose Microsoft problems, but not for problems with Linux.

Also it seems that Verizon and their kindred adhere to the PPP RFCs
only when it suits them. Disabling VJ compression should not result
in the termination of the PPP link - which seems to me to be what's
happening.

--
Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/
/* The wealth of a nation is created by the productive labor of its
* citizens. */

OK. I found the problem is related to the asycmap settings.

If I turn off the default setting

asyncmap 0

and turn on

default-asyncmap

I can reliably make a connection.

The pppd documetnation says this is often necessary with ISDN
services. This may not be the most efficient approach, so if someone
knows better, just let me know. But at least it is working.

Michael

michael_hieb@celoso.net (Michael Hieb) wrote in message news:<e369baba.0402151422.7800539e@posting.google. com>...
> Hi All,
>
> I have been unable to connect to Verizon via their high-speed CDMA
> 1xevdo service. The problem seems
> to be related to the ppp negotiation. I am running SuSE 8.2 on a
> Toshiba Satellite Pro
> running kernel 2.4.20-4GB. The Verizon card is the AirPrime 5220 and I
> set it up sucessfully using the
> instructions at http://www.ka9q.net/5220.html.
>
> I have successfully connected at least three times, but most times,
> immediately after what seems to be
> a successful connect, I get a packet from Verizon requesting a
> disconnect. For example
>
> local IP address 166.180.55.131
> remote IP address 66.174.120.134
> primary DNS address 66.174.3.7
> secondary DNS address 66.174.6.7
> Script /etc/ppp/ip-up started (pid 7099)
> Script /etc/ppp/ip-up finished (pid 7099), status = 0x0
> rcvd [LCP TermReq id=0x5]
> LCP terminated by peer
> cbcp_lowerdown
> Script /etc/ppp/ip-down started (pid 7160)
> sent [LCP TermAck id=0x5]
> Script /etc/ppp/ip-down finished (pid 7160), status = 0x0
> Connection terminated.
> Connect time 0.3 minutes.
> Sent 145 bytes, received 106 bytes.
>
> Here is what the log looks like
> for a successful connection
> http://www.celoso.net/pppd_verizon/ppp.1xevdo.good and here is what it
> looks like
> for an unsusccesful connection
> http://www.celoso.net/pppd_verizon/ppp.1xevdo.bad. Lastly here are the
> connection settings http://www.celoso.net/pppd_verizon/ppp.1xevdo.settings.
>
> I cannot figure out what the problem here is. Sadly
> when I contact Verizon, all they want to know is why I don't use their
> windoze software (which does work - I just ddon't want to use
> windoze).
>
> Any clues, greatfully accepted.
>
> Michael

Michael Hieb <michael_hieb@celoso.net> wrote:
> OK. I found the problem is related to the asycmap settings.

> If I turn off the default setting

> asyncmap 0

> and turn on

> default-asyncmap

> I can reliably make a connection.

Boy was I off-track!

But the Verizon PPP implementation for the bad connection actually
*requested* asyncmap 0 for itself, and accepted pppd's implementation
default asyncmap, which is also 0. That really doesn't make any sense.

--
Clifford Kite Email: "echo xvgr_yvahk-ccc@ri1.arg|rot13"
PPP-Q&A links, downloads: http://ckite.no-ip.net/