From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 1 15:15:37 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 4B736345 for ; Wed, 1 Apr 2015 15:15:37 +0000 (UTC) Received: from mail-qg0-x236.google.com (mail-qg0-x236.google.com [IPv6:2607:f8b0:400d:c04::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 E785DBF4 for ; Wed, 1 Apr 2015 15:15:36 +0000 (UTC) Received: by qgep97 with SMTP id p97so45167392qge.1 for ; Wed, 01 Apr 2015 08:15:36 -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=NdvE3ox8E4B2wVgV1OPFkTXsuK+GbPnLwUB9yXQ7zZ4=; b=r4DbPDVVV5k5r4kFT4WgLRHqkMDnnz8SfOUXdDNDhU3qDL2buEvRC8cKQmyZzNoQ9W YYB2OIMa1l6QINq7LCQ76Go7Pnp2xuzD41h7TSAPCsO8Cg2g7EPRYDdvba7PLd7jxIjW 5MXWBbO1wckrYq/zK4IaWTdRnFshPnErHy5uK/9pzQZwnJtxLzoTIbJ62Znnx+H7VYM7 ptUVPzn+kLCg8v4ce5i6VgVEchTAZAG2F1veOjOnmOBy8KrtcqQUE6rYSIDqz9XkA4EL jQ4C8475uvglBPLcHMQKSOk+y7zMh1T47HF4KFANB76VHqinVds23DEE1ySWhY5BNqao MhEg== MIME-Version: 1.0 X-Received: by 10.140.86.199 with SMTP id p65mr55279372qgd.49.1427901336168; Wed, 01 Apr 2015 08:15:36 -0700 (PDT) Received: by 10.140.138.206 with HTTP; Wed, 1 Apr 2015 08:15:35 -0700 (PDT) In-Reply-To: References: <0AD7A2F7-37BE-4F6A-9FD6-F6C81B2CAF36@gmail.com> Date: Wed, 1 Apr 2015 08:15:35 -0700 Message-ID: Subject: Re: register HID with SDP error From: Maksim Yevmenkin To: Waitman Gobble 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: Wed, 01 Apr 2015 15:15:37 -0000 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