From owner-freebsd-bluetooth@FreeBSD.ORG  Thu Oct 11 22:32:48 2012
Return-Path: <owner-freebsd-bluetooth@FreeBSD.ORG>
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 06E103F9
 for <freebsd-bluetooth@freebsd.org>; Thu, 11 Oct 2012 22:32:48 +0000 (UTC)
 (envelope-from longwitz@incore.de)
Received: from dss.incore.de (dss.incore.de [195.145.1.138])
 by mx1.freebsd.org (Postfix) with ESMTP id B95298FC12
 for <freebsd-bluetooth@freebsd.org>; Thu, 11 Oct 2012 22:32:47 +0000 (UTC)
Received: from secmail.incore (inetdns.dmz [10.1.0.3])
 by dss.incore.de (Postfix) with ESMTP id A3A3B5C090;
 Fri, 12 Oct 2012 00:32:46 +0200 (CEST)
Received: from lolap.longwitz (ip-2-203-147-109.web.vodafone.de
 [2.203.147.109])
 by secmail.incore (Postfix) with ESMTPS id 565895C1E;
 Fri, 12 Oct 2012 00:32:46 +0200 (CEST)
Message-ID: <5077490F.7010901@incore.de>
Date: Fri, 12 Oct 2012 00:32:47 +0200
From: Andreas Longwitz <longwitz@incore.de>
User-Agent: Mozilla/5.0 (X11; FreeBSD i386;
 rv:7.0.1) Gecko/20111007 Thunderbird/7.0.1
MIME-Version: 1.0
To: maksim yevmenkin <maksim.yevmenkin@gmail.com>, 
 freebsd-bluetooth@freebsd.org
Subject: Re: btpand problem
References: <507736A8.4050605@incore.de>
 <BDA3CA14-92C0-414E-9D55-E96EA7A73312@gmail.com>
In-Reply-To: <BDA3CA14-92C0-414E-9D55-E96EA7A73312@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-bluetooth@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Using Bluetooth in FreeBSD environments
 <freebsd-bluetooth.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bluetooth>, 
 <mailto:freebsd-bluetooth-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bluetooth>
List-Post: <mailto:freebsd-bluetooth@freebsd.org>
List-Help: <mailto:freebsd-bluetooth-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth>, 
 <mailto:freebsd-bluetooth-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 22:32:48 -0000

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.

>>
>> I have the problem described in this list in May 2009 (btpand example) with FreeBSD 8.3.
>>
>> ping -s 635 panserver -->  ICMP 677 -->  nw=672 in bnep_send(), writev syscall is ok with iov[0].iov_len=9 and iov[1].iov_len=663.
>>
>> ping -s 636 panserver -->  ICMP 678 -->  nw=-1, errno=40 (EMSGSIZE) is not ok with iov[0].iov_len=9 and iov[1].iov_len=664.
>>
>> In the error case the trace written by hcidump is empty (no suprise).
>> My tap interface has mtu=1500<  1691 (checked in bnep_send).
>>

Andreas Longwitz