From owner-freebsd-bluetooth@FreeBSD.ORG  Mon Mar 23 07:42:45 2015
Return-Path: <owner-freebsd-bluetooth@FreeBSD.ORG>
Delivered-To: freebsd-bluetooth@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id CEABB780
 for <freebsd-bluetooth@freebsd.org>; Mon, 23 Mar 2015 07:42:45 +0000 (UTC)
Received: from relay3-d.mail.gandi.net (relay3-d.mail.gandi.net
 [IPv6:2001:4b98:c:538::195])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 80C44D17
 for <freebsd-bluetooth@freebsd.org>; Mon, 23 Mar 2015 07:42:45 +0000 (UTC)
Received: from mfilter2-d.gandi.net (mfilter2-d.gandi.net [217.70.178.140])
 by relay3-d.mail.gandi.net (Postfix) with ESMTP id 661ADA80CE;
 Mon, 23 Mar 2015 08:42:43 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mfilter2-d.gandi.net
Received: from relay3-d.mail.gandi.net ([217.70.183.195])
 by mfilter2-d.gandi.net (mfilter2-d.gandi.net [10.0.15.180]) (amavisd-new,
 port 10024)
 with ESMTP id 6FfGBZ8ezwat; Mon, 23 Mar 2015 08:42:41 +0100 (CET)
X-Originating-IP: 81.168.1.155
Received: from galant.ogmig.net (unknown [81.168.1.155])
 (Authenticated sender: plunky@ogmig.net)
 by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id A67A7A80D5;
 Mon, 23 Mar 2015 08:42:41 +0100 (CET)
Received: by galant.ogmig.net (Postfix, from userid 1000)
 id D32922600C5; Mon, 23 Mar 2015 07:42:40 +0000 (GMT)
Date: Mon, 23 Mar 2015 07:42:40 +0000 (GMT)
From: Iain Hibbert <plunky@ogmig.net>
To: Waitman Gobble <gobble.wa@gmail.com>
Subject: Re: register HID with SDP error
In-Reply-To: <CAFuo_fwBcBQOZzFNntBSP0AwyAkGq=s-eeKJ1CCgjPp5tWdG=A@mail.gmail.com>
Message-ID: <alpine.NEB.2.11.1503230738400.2717@galant.ogmig.net>
References: <CAFuo_fy9xRU2T3GUPY8116yZCUd8sL9pBQ9ixXnMwO56niJFog@mail.gmail.com>
 <CAFuo_fzrk+WLXivZrnTsGQD+S7mq+USXB7Mn6+JT=y64JakGSw@mail.gmail.com>
 <CAFPOs6q3iVcNthF=S--UgTm=5wA0HM6coqB7AcmCKb=55OWdTQ@mail.gmail.com>
 <CAFuo_fxgBVKxmzbJs+-XDz+u4tb2_i3eYXSa-oiOoU+QD6ApwQ@mail.gmail.com>
 <CAFPOs6r_D7bcGCMP_bP+QtZgKt7Oj5jRJ2v872RODekn+6xv1Q@mail.gmail.com>
 <CAFuo_fwPuaD4bYwfZou0RBswZsTmdtVZA1B2GqUdo3ZJJiWRQg@mail.gmail.com>
 <0AD7A2F7-37BE-4F6A-9FD6-F6C81B2CAF36@gmail.com>
 <CAFuo_fye5RWNtjsutHa+bXL0AYHYRpJxW-b=48o0iMwX227wdA@mail.gmail.com>
 <alpine.NEB.2.11.1503170658130.4414@galant.ogmig.net>
 <CAFuo_fx47uRC-eKD_KtsSsrMCQZauyHyCOgRxGbtp_WEZ49o_Q@mail.gmail.com>
 <alpine.NEB.2.11.1503171759510.4792@galant.ogmig.net>
 <CAFPOs6omaOOOumNk2Zg=YBgK9cy7JumOZ6k-89oTbVw-3PgAvg@mail.gmail.com>
 <CAFuo_fy+dmpcswwLMV3LaGGkN6VyQ+=ieEzYUT=omSLkhS8=EA@mail.gmail.com>
 <CAFuo_fwBcBQOZzFNntBSP0AwyAkGq=s-eeKJ1CCgjPp5tWdG=A@mail.gmail.com>
User-Agent: Alpine 2.11 (NEB 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org>
X-BeenThere: freebsd-bluetooth@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Using Bluetooth in FreeBSD environments
 <freebsd-bluetooth.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bluetooth>, 
 <mailto:freebsd-bluetooth-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bluetooth/>
List-Post: <mailto:freebsd-bluetooth@freebsd.org>
List-Help: <mailto:freebsd-bluetooth-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
 <mailto:freebsd-bluetooth-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2015 07:42:45 -0000

On Sun, 22 Mar 2015, Waitman Gobble wrote:

> Through trial and error I found that this code is preventing the
> response to the  0x0100 (L2CAP) query.
>
> in sdpd/ssar.c around line 230 or so.
>
> if (memcmp(&uuid, &puuid, sizeof(uuid)) != 0 &&
>    memcmp(&uuid, &uuid_public_browse_group, sizeof(uuid)) != 0)
> continue;
>
>
> When I comment that code out then it responds to the request with the
> list of registered and advertised services and my clients then
> magically connect.

and if you search for some other protocol UUID that is perhaps not
present?  I suspect that without that code, you will get all profiles
back, whatever you search for (which is going to be wrong :)

the real problem is, that sdpd does not enumerate the Protocol UUIDs in
each profile that it has stored, and therefore cannot respond properly to
the request for 'all records containing UUID 0x0100' for example.

regards,
iain