Linux bluetooth development
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vinicius.gomes@openbossa.org>
To: Charles Gordon <digigordo@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: l2ping Recv failed: Connection reset by peer
Date: Tue, 31 Jul 2012 19:33:14 -0300	[thread overview]
Message-ID: <20120731223314.GA19846@samus> (raw)
In-Reply-To: <CAGjArBcwtaRoecSivEaN9FiCbGfC3JhFRwXUVqq58SmQhN07sQ@mail.gmail.com>

Hi Charles,

On 17:12 Tue 31 Jul, Charles Gordon wrote:
> Hi,
> 
> I'm porting bluez 4.98 to an embedded system.  I have it up and running, but
> I notice that when I run l2ping, I get the message "Recv failed: Connection
> reset by peer" after l2ping runs for 5 seconds.  This is very consistent.
> It doesn't matter whether I ping once a second, or do a flood ping.  After 5
> seconds the l2ping program closes with the message saying the connection was
> reset by the peer.

If I run l2ping without parameters, I get this:

l2ping - L2CAP ping
Usage:
	l2ping [-i device] [-s size] [-c count] [-t timeout] [-d delay] [-f] [-r] [-v] <bdaddr>
	-f  Flood ping (delay = 0)
	-r  Reverse ping
	-v  Verify request and response payload

The '-t' option sounds promising.

But anyway, the default value for the timeout is 10 seconds. So I would like know
how would it behave with other values. Perhaps the remote side is disconnecting.

[snip]


Cheers,
-- 
Vinicius

  reply	other threads:[~2012-07-31 22:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31 21:12 l2ping Recv failed: Connection reset by peer Charles Gordon
2012-07-31 22:33 ` Vinicius Costa Gomes [this message]
2012-08-07 21:01 ` Mike

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=20120731223314.GA19846@samus \
    --to=vinicius.gomes@openbossa.org \
    --cc=digigordo@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox