Dave Booth wrote:
Just an update on this issue - tried it again after grabbing the
latest 8120 device software, in case there was a bug there. A bit of a
forlorn hope since it was already working on windows and so it proved.
Results identical with bb device software v4.5.0.124.
Dave.
Dave,
After re-reading your original post and the pppd manual I believe this
is what is happening.
Your system received a request from your provider to authenticate using pap.
rcvd [LCP ConfReq id=0x0 <asyncmap 0x0> <auth pap>]
Your system say's "No auth is possible" and sends a reject message.
No auth is possible
sent [LCP ConfRej id=0x0 <auth pap>]
Since no authentication is possible the connection is closed.
From the pppd manual:
The default behaviour of pppd is to agree to authenticate if
requested, and to not require authentication from the peer.
However, pppd will not agree to authenticate itself with a par-
ticular protocol if it has no secrets which could be used to do
so.
I believe your /etc/ppp/pap-secrets file doesn't have any entries in it, hence "No
auth is possible".
Try adding one of these to the pap-secrets file:
\"\" * \"\"
or
"" * ""
or
* * \"\"
or
* * ""
White space should be a tab character!!!
Let me know if you get any further.
- Andy
.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Barry-devel mailing list
Barry-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/barry-devel
