From: Johan Hedberg <johan.hedberg@gmail.com>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: obexd: obex_handle_input: poll event HUP ERR
Date: Tue, 22 Jun 2010 10:58:33 +0300 [thread overview]
Message-ID: <20100622075833.GA14319@jh-x301> (raw)
In-Reply-To: <4C206924.50303@gmail.com>
Hi,
On Tue, Jun 22, 2010, Jiri Slaby wrote:
> > libopenobex seems to be indicating REQDONE, so it doesn't look like
> > anything is necessarily wrong with obexd here. However, you'd need to
> > look at the HCI level trafic (output of "hcidump -XV") to determine
> > what's really going on (e.g. is it obexd or the client that's
> > disconnecting).
>
> Attached:
Thanks.
> # hcidump -XV
<snip>
> < ACL data: handle 42 flags 0x02 dlen 11
> L2CAP(d): cid 0x0041 len 7 [psm 3]
> RFCOMM(d): UIH: cr 0 dlci 18 pf 0 ilen 3 fcs 0x14
> OBEX: Put rsp(f): status 403 len 3
So obexd is responding with "forbidden" to the client.
Possible reasons:
* obexd doesn't have write access to the directory it's trying to
write to
* You don't have an agent registered for obexd that could accept
the request or you're not running obexd in the auto-accept mode
(the -a switch).
Johan
next prev parent reply other threads:[~2010-06-22 7:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 7:23 obexd: obex_handle_input: poll event HUP ERR Jiri Slaby
2010-06-22 7:38 ` Johan Hedberg
2010-06-22 7:41 ` Jiri Slaby
2010-06-22 7:58 ` Johan Hedberg [this message]
2010-06-22 8:04 ` Jiri Slaby
2010-06-22 8:13 ` Johan Hedberg
2010-06-22 16:16 ` Jiri Slaby
2010-06-22 16:34 ` Bastien Nocera
-- strict thread matches above, loose matches on Subject: below --
2011-09-15 7:43 Alex Mach
[not found] <E1R47Z5-0000QH-00.alexvm12e-mail-ru@f167.mail.ru>
2011-09-16 8:07 ` Luiz Augusto von Dentz
2011-09-21 12:13 ` Alex Mach
2011-09-21 12:33 ` Luiz Augusto von Dentz
2011-09-22 7:40 ` alexvm12e
2011-09-22 8:07 ` Luiz Augusto von Dentz
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=20100622075833.GA14319@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=jirislaby@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;
as well as URLs for NNTP newsgroup(s).