From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 1 15:06:20 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 196ADC41 for ; Wed, 1 Apr 2015 15:06:20 +0000 (UTC) Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::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 B6F41AA9 for ; Wed, 1 Apr 2015 15:06:19 +0000 (UTC) Received: by qgh3 with SMTP id 3so44837269qgh.2 for ; Wed, 01 Apr 2015 08:06:19 -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=m50M8DSGmmVzlKoNjyLN59UG+aiGCrdY0ekWdPJ4du4=; b=mSX0xKREyhJGwVJ4wOgyhEatcB0C8DKi5fhmPgDUA+w9flM0lS9Zc2Fikym4FWaujh CI7yTyRgqbdZmPOJwqEfHbZuosfNXMCwOwBlhgTofvgK0hClVYzfiILWRJhPd3gQWePw XI3/RD0zgFLbjd6I3VePscHUWWrBKp1euuDpuWZYSVKMtrBBVK2vo2WDh+ajSwpaR2er 6bL+YEpStOq29tqExfoZdv7wPHbrH1ACOwpaxh5yIn3mwPBcdYy9B7DPNwEKwNnwHJzp 7OFzgO2C/mm2M27qlk6csZUXC98kocnjWfU+H1Dp25d72pX5Hap8MGYVTI0U9glg5IyD 0z7g== MIME-Version: 1.0 X-Received: by 10.140.239.140 with SMTP id k134mr56198405qhc.98.1427900778965; Wed, 01 Apr 2015 08:06:18 -0700 (PDT) Received: by 10.140.138.206 with HTTP; Wed, 1 Apr 2015 08:06:18 -0700 (PDT) In-Reply-To: References: <0AD7A2F7-37BE-4F6A-9FD6-F6C81B2CAF36@gmail.com> Date: Wed, 1 Apr 2015 08:06:18 -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:06:20 -0000 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. thanks, max