From owner-freebsd-bluetooth@FreeBSD.ORG Fri Jan 7 18:02:32 2005 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 399BF16A4CF for ; Fri, 7 Jan 2005 18:02:32 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9324B43D49 for ; Fri, 7 Jan 2005 18:02:31 +0000 (GMT) (envelope-from Maksim.Yevmenkin@savvis.net) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44])j07I2PGF024058; Fri, 7 Jan 2005 12:02:25 -0600 Received: from s228130hz1ew17.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 7 Jan 2005 12:02:20 -0600 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew17.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 7 Jan 2005 12:02:13 -0600 Message-ID: <41DECEA3.5080500@savvis.net> Date: Fri, 07 Jan 2005 10:02:11 -0800 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Jes References: <20050107163705.616cbe5f@zurich.homeunix.com> In-Reply-To: <20050107163705.616cbe5f@zurich.homeunix.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Jan 2005 18:02:13.0412 (UTC) FILETIME=[03F15E40:01C4F4E3] X-ECS-MailScanner: No virus is found cc: freebsd-bluetooth@freebsd.org Subject: Re: Motorola E1000 and obexapp 1.4.4 in server mode X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jan 2005 18:02:32 -0000 Jes, > I've just found motorola e1000 suited for vodafone maybe can send files > via bluetooth (sort of more or less hidden menu option). Ok, obexapp in > client mode works fine (1.4.4) but in server mode i get errors > (/var/log/messages). > > I launch obexapp in server mode : > >>obexapp -d -s -C 10 > > then I send the file from phone, my phone finds my computer and try to > send ... and remains trying until I cancel. In /var/log/messages two > entries : > > Jan 7 16:34:10 zurich kernel: ng_l2cap_l2ca_receive: ubt0l2cap - > invalid L2CAP data packet. Packet too big, length=671, imtu=132, cid=77 > Jan 7 16:34:10 zurich kernel: ng_l2cap_l2ca_receive: ubt0l2cap - > invalid L2CAP data packet. Packet too big, length=363, imtu=132, cid=77 hmmm... strange. it appears that phone sends over sized l2cap packets. rfcomm layer sets default mtu of 132 bytes, but remote side (phone) keeps sending much bigger packets, so the stack drops them. > I can't find information about this... any idea ? as usual, i need binary hcidump (produced with -w option). without it i can not tell what is going on. just by looking at two error messages below i'd guess that both sides (phone and pc) seems to disagree on mtu. max