Date: Mon, 23 Mar 2015 07:42:40 +0000 (GMT) From: Iain Hibbert <plunky@ogmig.net> To: Waitman Gobble <gobble.wa@gmail.com> Cc: "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org> Subject: Re: register HID with SDP error Message-ID: <alpine.NEB.2.11.1503230738400.2717@galant.ogmig.net> In-Reply-To: <CAFuo_fwBcBQOZzFNntBSP0AwyAkGq=s-eeKJ1CCgjPp5tWdG=A@mail.gmail.com> References: <CAFuo_fy9xRU2T3GUPY8116yZCUd8sL9pBQ9ixXnMwO56niJFog@mail.gmail.com> <CAFuo_fzrk%2BWLXivZrnTsGQD%2BS7mq%2BUSXB7Mn6%2BJT=y64JakGSw@mail.gmail.com> <CAFPOs6q3iVcNthF=S--UgTm=5wA0HM6coqB7AcmCKb=55OWdTQ@mail.gmail.com> <CAFuo_fxgBVKxmzbJs%2B-XDz%2Bu4tb2_i3eYXSa-oiOoU%2BQD6ApwQ@mail.gmail.com> <CAFPOs6r_D7bcGCMP_bP%2BQtZgKt7Oj5jRJ2v872RODekn%2B6xv1Q@mail.gmail.com> <CAFuo_fwPuaD4bYwfZou0RBswZsTmdtVZA1B2GqUdo3ZJJiWRQg@mail.gmail.com> <0AD7A2F7-37BE-4F6A-9FD6-F6C81B2CAF36@gmail.com> <CAFuo_fye5RWNtjsutHa%2BbXL0AYHYRpJxW-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%2BdmpcswwLMV3LaGGkN6VyQ%2B=ieEzYUT=omSLkhS8=EA@mail.gmail.com> <CAFuo_fwBcBQOZzFNntBSP0AwyAkGq=s-eeKJ1CCgjPp5tWdG=A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.NEB.2.11.1503230738400.2717>