public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Daniel Stoddart <d.stoddart@cs.ucl.ac.uk>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Service registering but not visible
Date: Sat, 17 Jul 2004 17:39:39 +0200	[thread overview]
Message-ID: <1090078779.4558.35.camel@pegasus> (raw)
In-Reply-To: <000701c46c08$958becd0$af2dbeac@oemcomputer>

Hi Daniel,

> I tried the commands you suggested with the following results:
> 
> root@darkstar:~# hcid
> root@darkstar:~# /usr/sbin/sdpd

after that check what /proc/bluetooth/l2cap is saying.

> root@darkstar:~# hcitool dev
> Devices:
>         hci0    00:0A:3A:50:2F:2D
> root@darkstar:~# hcitool inq
> Inquiring ...
>         00:0E:6D:11:E6:EB       clock offset: 0x4c21    class: 0x500204
> root@darkstar:~# sdptool add --channel=13 OPUSH
> OBEX Object Push service registered
> root@darkstar:~# sdptool browse local
> Browsing FF:FF:FF:00:00:00 ...
> Service Search failed: Protocol error

That is the problem. Make sure that sdpd is really running.

> root@darkstar:~# hcidump -x
> HCIDump - HCI packet analyzer ver 1.9
> device: hci0 snap_len: 1028 filter: 0xffffffff
> 
> root@darkstar:~# hcidump -x
> HCIDump - HCI packet analyzer ver 1.9
> device: hci0 snap_len: 1028 filter: 0xffffffff
> > HCI Event: Connect Request (0x04) plen 10
>   EB E6 11 6D 0E 00 04 02 50 01
> < HCI Command: Accept Connection Request (0x01|0x0009) plen 7
>   EB E6 11 6D 0E 00 01
> > HCI Event: Command Status (0x0f) plen 4
>   00 01 09 04
> > HCI Event: Connect Complete (0x03) plen 11
>   00 29 00 EB E6 11 6D 0E 00 01 00
> < HCI Command: Write Link Policy Settings (0x02|0x000d) plen 4
>   29 00 0E 00
> > HCI Event: Page Scan Repetition Mode Change (0x20) plen 7
>   EB E6 11 6D 0E 00 01
> > HCI Event: Command Complete (0x0e) plen 6
>   01 0D 08 00 29 00
> < HCI Command: Change Connection Packet Type (0x01|0x000f) plen 4
>   29 00 18 CC
> > ACL data: handle 0x0029 flags 0x02 dlen 12
>     L2CAP(s): Connect req: psm 1 scid 0x0041
> < ACL data: handle 0x0029 flags 0x02 dlen 16
>     L2CAP(s): Connect rsp: dcid 0x0000 scid 0x0041 result 2 status 0

This means "Connection refused - PSM not supported" and leads to me that
the sdpd is not running.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-07-17 15:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16 20:25 [Bluez-devel] Service registering but not visible Daniel Stoddart
2004-07-16 21:15 ` Marcel Holtmann
2004-07-17 14:15   ` Daniel Stoddart
2004-07-17 15:39     ` Marcel Holtmann [this message]
2004-07-17 23:55       ` Daniel Stoddart
2004-07-18  8:59         ` Marcel Holtmann
2004-07-19 22:47           ` Daniel Stoddart

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=1090078779.4558.35.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=d.stoddart@cs.ucl.ac.uk \
    /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