From owner-freebsd-bluetooth@FreeBSD.ORG Mon Mar 23 05:39:20 2015 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E5C67E77 for ; Mon, 23 Mar 2015 05:39:19 +0000 (UTC) Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E6E9ED9 for ; Mon, 23 Mar 2015 05:39:19 +0000 (UTC) Received: by wibg7 with SMTP id g7so28351525wib.1 for ; Sun, 22 Mar 2015 22:39:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MCAHP2OdUIC32DxJSGhhhhoxL82bsPTpayGSYkPWBMc=; b=lxxc7b0rn/y8+9YauebNB63PKtwrJkfBu3Kk7EQLcDYRxhULsw+sbtKyVBjqbY6EpM s4Cow4VMhW2pTIz2sC//FpzUS+Ua17dDLh2NKybU5nUwKfULYzWBUAUvqHFlTpq3ag27 XBKF9JDMVyU8motIp4NOXZOjoe9ljB1cPa1vWYK+QGjz0Zs4cjXRLNw0ZMIq3kgiQOi8 Gum1qjEkfNC3zVLKGTRils6VYeXJE2ZfHPHd1Pht0IT4iQJpytkFLwd5mxW5WtIgE26f 4WUkKqlhKzZj+PsabXRnNgIspTenvSpoSEFVzewKEBGUQ5hGS02Z9CPlms38ASMeBOJs gC0A== MIME-Version: 1.0 X-Received: by 10.180.83.195 with SMTP id s3mr16595007wiy.54.1427089157906; Sun, 22 Mar 2015 22:39:17 -0700 (PDT) Received: by 10.27.91.75 with HTTP; Sun, 22 Mar 2015 22:39:17 -0700 (PDT) In-Reply-To: References: <0AD7A2F7-37BE-4F6A-9FD6-F6C81B2CAF36@gmail.com> Date: Sun, 22 Mar 2015 22:39:17 -0700 Message-ID: Subject: Re: register HID with SDP error From: Waitman Gobble To: Maksim Yevmenkin Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-bluetooth@freebsd.org" , Iain Hibbert X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2015 05:39:20 -0000 On Tue, Mar 17, 2015 at 11:33 AM, Maksim Yevmenkin wrote: > On Tue, Mar 17, 2015 at 11:20 AM, Iain Hibbert wrote: >> On Tue, 17 Mar 2015, Waitman Gobble wrote: >> >>> hcidump log https://gist.github.com/waitman/c3f8a3bc9b046e36dbb5 >> >> Kind of unrelatedly, from that log, the Linux machine requests a search >> for Protocol UUID 0x0100 (L2CAP) but gets nothing in return.. >> >>> ACL data: handle 0x0048 flags 0x02 dlen 24 >> L2CAP(d): cid 0x44 len 20 [psm 1] >> SDP SSA Req: tid 0x0 len 0xf >> pat uuid-16 0x0100 (L2CAP) >> max 0xffff >> aid(s) 0x0000 - 0xffff >> cont 00 >> < ACL data: handle 0x0048 flags 0x02 dlen 15 >> L2CAP(d): cid 0x40 len 11 [psm 1] >> SDP SSA Rsp: tid 0x0 len 0x6 >> cnt 0x3 >> cont 00 >> >> ..does the SDP server not return results for that, Max? > > well, i don't think i ever got around to adding a feature that looks > for uuid inside records. it currently only matches service class > uuid's. so, yes, query for l2cap uuid will return nothing currently. > its trivial to add this though. i think i even have a patch somewhere. > > [...] > >> btw .. if you use sdpcontrol(1) to query the local SDP server (see -l) >> then hcidump will not see anything of the interchange, since it does not >> go through the Bluetooth stack. > > absolutely correct > > thanks, > max I'm tracking down a client connection problem, maybe this is causing the issue... checking it out. https://gist.github.com/waitman/c51ea08ebb6a2898f33f client gives up and never opens PSM channel 17 or 19 I did notice some clients request 0x1200 'pnp info' so I added SDP_SERVICE_CLASS_PNP_DEVICE handler to sdpd to see what would happen. The code is here -> https://github.com/waitman/sdpd/blob/master/pnp.c But the configuration parameters should be set by the request, not hardcoded into pnp.c (also hid.c should be fixed) -- Waitman Gobble Los Altos California USA 510-830-7975