btpand problem

[Maksim Yevmenkin]

On Thu, Oct 11, 2012 at 3:32 PM, Andreas Longwitz <longwitz at incore.de> 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