From: Radek (Fotopiper) <fotopiper@o2.pl>
To: bluez-devel@lists.sf.net
Subject: Re: [Bluez-devel] RFCOMM - serial line looped back.
Date: Fri, 12 Oct 2007 01:08:51 +0200 [thread overview]
Message-ID: <20071012010851.1a1ffc7e@darkstar.example.net> (raw)
In-Reply-To: <20071011143418.65350112@darkstar.example.net>
On Thu, 11 Oct 2007 14:34:18 +0200
Radek (Fotopiper) <fotopiper@o2.pl> wrote:
> Hello,
> I'm getting a "Serial line is looped back." from pppd when I try to connect to
> the net threw my GSM phone.
> pppd 2.4.4
> kernel 2.6.22.8 (22.2 & 22.9 give the same results)
> Bluez 3.20 (libs&utils)
> Slacware 12
>
> PPPD debug fallows "serial line looped back" and (at the end of mail) "LCP
> terminated by peer (peer refused to authenticate)".
>
> Any suggestions what I am doing wrong?
Well I found a remedy, maybe someone else will benefit..
The serial line looped back if there was a problem connecting the ISP.. but the
main problem was the noauth option in pppd, as my ISP changed they configuration:
rcvd [LCP ConfReq id=0x1 <asyncmap 0xa0000> <auth pap>]
this line says that the peer (ISP) needs to authenticate (if anybody else
starts to look for a solution for a similar problem)..
Best regards to ALL, and sorry for the trouble
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-10-11 23:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 12:34 [Bluez-devel] RFCOMM - serial line looped back Radek
2007-10-11 23:08 ` Radek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071012010851.1a1ffc7e@darkstar.example.net \
--to=fotopiper@o2.pl \
--cc=bluez-devel@lists.sf.net \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.