From owner-freebsd-bluetooth@FreeBSD.ORG Thu Oct 11 22:39:54 2012 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 49E7870D for ; Thu, 11 Oct 2012 22:39:54 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1C2A88FC14 for ; Thu, 11 Oct 2012 22:39:53 +0000 (UTC) Received: by mail-pb0-f54.google.com with SMTP id rp8so2521135pbb.13 for ; Thu, 11 Oct 2012 15:39:53 -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=/lmQARAj1NdCRne8pGt3Lo5A/KoTBRDQ//jPELlTnCY=; b=WAYGdyisMsD+K/QahHkRE60GgHPoPAcXtrMyhNB0smI4NhvcLRWd2UzoEKyyaSfI0G IS69azqOlgpRNrvoFI6xr4diKuU1Pj75hTSUlAeeXAy4lSRBcEp5/tRuMgUt1oljd/D6 HuG81cwb2tFdyaXjXlP16GHVeSpiUkAutdMdFDOVJM6YTx/gHOK+8Ku5PZZGBWjdh+gz O6X+olGAEXiXFvk31grxdt+TgMvksSJWwzO3ZO2xcqX4OhaT/ns7CjtYxj7K7HT6jOWE /3dkic9rDdKma11FCIZQP3wJVCaMFGjLcU0dm2O8Yczk8WR37MJgwpqN6wYy5WbpYzNy /ZBg== MIME-Version: 1.0 Received: by 10.68.222.37 with SMTP id qj5mr7687712pbc.132.1349995193681; Thu, 11 Oct 2012 15:39:53 -0700 (PDT) Received: by 10.68.240.38 with HTTP; Thu, 11 Oct 2012 15:39:53 -0700 (PDT) In-Reply-To: <5077490F.7010901@incore.de> References: <507736A8.4050605@incore.de> <5077490F.7010901@incore.de> Date: Thu, 11 Oct 2012 15:39:53 -0700 Message-ID: Subject: Re: btpand problem From: Maksim Yevmenkin To: Andreas Longwitz Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-bluetooth@freebsd.org X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Oct 2012 22:39:54 -0000 On Thu, Oct 11, 2012 at 3:32 PM, Andreas Longwitz wrote: > Thanks for quick answer ! > >> Can you tell what l2cap Mtu was negotiated on both ends? > > HCIDump - HCI packet analyzer ver 1.5 > ... >> ACL data: handle 0x002a flags 0x02 dlen 18 > L2CAP(s): Config rsp: scid 0x004f flags 0x0000 result 0 clen 4 > MTU 672 >> ACL data: handle 0x002a flags 0x02 dlen 16 > L2CAP(s): Config req: dcid 0x004f flags 0x0000 clen 4 > MTU 256 > .... > < ACL data: handle 0x002a flags 0x02 dlen 16 > L2CAP(s): Config req: dcid 0x0203 flags 0x0000 clen 4 > MTU 1691 >> HCI Event: Number of Completed Packets(0x13) plen 5 >> ACL data: handle 0x002a flags 0x02 dlen 18 > L2CAP(s): Config rsp: scid 0x0050 flags 0x0000 result 0 clen 4 > MTU 1691 >> ACL data: handle 0x002a flags 0x02 dlen 16 > L2CAP(s): Config req: dcid 0x0050 flags 0x0000 clen 4 > MTU 1691 > .... > > My panserver is an iPhone 4S in hotspot mode. well, it looks like your device told btpand(8) that it can not accept more than 672 bytes (default l2cap mtu) at a time. hence the emsgsize error, i.e. datagram, btpand(8) is trying to send, is too big for remote device to accept. quick fix would be to adjust mtu on the tap interface to make sure btpand(8) never tries to send more than 672 bytes of payload. thanks, max