btpand problem

[Andreas Longwitz]

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