From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 1 15:24:14 2015 Return-Path: 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 2D2EF4F6 for ; Wed, 1 Apr 2015 15:24:14 +0000 (UTC) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (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 A181ACF5 for ; Wed, 1 Apr 2015 15:24:13 +0000 (UTC) Received: by wixm2 with SMTP id m2so38053189wix.0 for ; Wed, 01 Apr 2015 08:24:12 -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=jY+4Kcgfxp/YZ7dMJSXk7QLZV8YOKXxPgnSwmzl1eLQ=; b=nInLyTZKnaPTKtk96bl6ALGO3Z9AGwS0GIASlEPV9skPvQOA+5gzwtUlClyq5G6eTk MShCUy2ZMwE7+LPMKYHCDVed7Fk9ub+eDOVLADLqLXrX88LRcImr31VaWQsIMNdNjKSl O4LLGOJh23vOU9NY8SFfTDFwVHYLNIIdKm4pQn2R3/apC+oSpp0zTdesJD98ol/m42yP vMLscVRxrOLLlZTU1fQvprF2YL5aQWjWu9z+RpXayn+vK3N3O0PYebWZdjiJsgpgWVKe c7RrK0qkBiB5tshzH9sSHsSAMJuPfuYeKjLLYoM6SxoQsIDGIMWOSXS+YmtKwXu4HBIu 6MLA== MIME-Version: 1.0 X-Received: by 10.195.12.97 with SMTP id ep1mr86615005wjd.134.1427901852171; Wed, 01 Apr 2015 08:24:12 -0700 (PDT) Received: by 10.27.91.75 with HTTP; Wed, 1 Apr 2015 08:24:12 -0700 (PDT) Received: by 10.27.91.75 with HTTP; Wed, 1 Apr 2015 08:24:12 -0700 (PDT) In-Reply-To: References: <0AD7A2F7-37BE-4F6A-9FD6-F6C81B2CAF36@gmail.com> Date: Wed, 1 Apr 2015 08:24:12 -0700 Message-ID: Subject: Re: register HID with SDP error From: Waitman Gobble To: Maksim Yevmenkin Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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: Wed, 01 Apr 2015 15:24:14 -0000 On Apr 1, 2015 8:15 AM, "Maksim Yevmenkin" wrote: > > On Wed, Apr 1, 2015 at 8:09 AM, Waitman Gobble wrote: > > On Wed, Apr 1, 2015 at 8:05 AM, Maksim Yevmenkin > > wrote: > >> Hello, > >> > >> [...] > >> > >>> Can this 'syntax error' problem be related to the requested MTU? > >>> > >>> with essentially the 'same' connection request, > >>> > >>> here's the transaction log from an MS Windows client. No syntax > >>> errors. The requested MTU is 1024 > >>> > >>> https://gist.github.com/waitman/2d5a72e9f9544848e832 > >>> > >>> L2CAP(d): cid 0x40 len 346 [psm 1] > >>> > >>> > >>> and a log from android client. Requested MTU is 256. > >>> > >>> https://gist.github.com/waitman/e365debcd4a96d849153 > >>> > >>> L2CAP(d): cid 0x43 len 247 [psm 1] > >>> > >>> note it's bombing out with something about aid 0x0200, which isn't > >>> actually an aid specified in my 0x1124 record. > >> > >> just a wild guess. please make sure that you maintain continuation > >> state properly. when sdp response is bigger than l2cap mtu, response > >> is chunked. > > > > Thank you, I was tinkering with things for awhile to try to find out > > why I was seeing 'syntax errors', but I'm thinking now there isn't a > > syntax error with the record, it's the hcidump program reading the > > broken up response. > > hcidump tries do be smart and re-assemble spd responses. if your > continuation state is wrong, hcidump might not be able to re-assemble > and parse response correctly > > thanks, > max Interesting. I will check into this. Thanks for the info. Waitman