Re: wvdial does not connect
- From: "usher_raymond82@xxxxxxxxx" <usher_raymond82@xxxxxxxxx>
- Date: 4 Apr 2006 05:32:13 -0700
Nice to hear from you James. I've been reading your replies in this
group to guide me on ppp.
James Carlson wrote:
You might want to search netnews archives. The oddities of GPRS havenetnews archives??
been discussed many times before.
Now I get a clearer picture.
This behavior is pretty typical for GPRS.
GPRS is designed very strangely. It does not do peer authentication
during the PPP Authentication phase. That PAP Authenticate-Ack that
you see is a complete fabrication: no authentication was done.
Instead, it waits until IPCP runs to authenticate the user. If
authentication fails, you then get really strange behavior with the
peer appearing to be unable to negotiate an IP address.
This is just a GPRS design flaw.
No. It means that either your user name/password are incorrect, orI believe the username and password should be correct. It is provided
that your GPRS service has not been properly activated.
by the service provider here. I also believe that GPRS service has been
properly activated as I managed to dial up on MS Win XP platform and
also do some surfing on the phone itself, just to make sure GPRS and
the phone works properly. Perhaps the only thing that I am afraid most
is missing configurations. I've added the user name and password even
to /etc/ppp/pap-secrets, necessary configurations to /etc/ppp/options
and configured wvdial.conf. I hope and certainly wish I do not miss
anything.
So this could mean that all the pap authentication messages is a polite
It means that the peer is asking you to please go away. It doesn't
want to talk to you anymore. It could just disconnect at layer one
(hang up the phone), but it's being overly polite.
act? If so, why does IPCP send a ConfReq? If that is normal, then how
come it can dial on a Win XP system?
Debug log at the peer side? Do you mean check on the ISP side? I have
Other than the suggestions above, the only way to find out why the
peer sent the link termination request is to go inspect the debug logs
on the peer's side. LCP provides a means for some useful text
information to be included in the termination message, but for some
reason the peer didn't bother doing that.
no idea on how to do this.
Thanks and hope to hear from you soon.
Regards,
Raymond
.
- Follow-Ups:
- Re: wvdial does not connect
- From: Unruh
- Re: wvdial does not connect
- From: James Carlson
- Re: wvdial does not connect
- References:
- wvdial does not connect
- From: usher_raymond82@xxxxxxxxx
- Re: wvdial does not connect
- From: James Carlson
- wvdial does not connect
- Prev by Date: Re: wvdial does not connect
- Next by Date: Re: wvdial does not connect
- Previous by thread: Re: wvdial does not connect
- Next by thread: Re: wvdial does not connect
- Index(es):
Relevant Pages
|
Loading