From owner-freebsd-bluetooth@FreeBSD.ORG Thu Oct 28 20:58:38 2010 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7585D106564A for ; Thu, 28 Oct 2010 20:58:38 +0000 (UTC) (envelope-from plunky@galant.ukfsn.org) Received: from mail.ukfsn.org (mail.ukfsn.org [77.75.108.10]) by mx1.freebsd.org (Postfix) with ESMTP id 08C1E8FC0A for ; Thu, 28 Oct 2010 20:58:37 +0000 (UTC) Received: from localhost (smtp-filter.ukfsn.org [192.168.54.205]) by mail.ukfsn.org (Postfix) with ESMTP id 7780CDEC01; Thu, 28 Oct 2010 21:31:26 +0100 (BST) Received: from mail.ukfsn.org ([192.168.54.25]) by localhost (smtp-filter.ukfsn.org [192.168.54.205]) (amavisd-new, port 10024) with ESMTP id FZTl-9klV1DX; Thu, 28 Oct 2010 21:31:26 +0100 (BST) Received: from galant.ukfsn.org (84-43-108-63.ppp.onetel.net.uk [84.43.108.63]) by mail.ukfsn.org (Postfix) with ESMTP id 24A6FDEBFC; Thu, 28 Oct 2010 21:31:26 +0100 (BST) Received: by galant.ukfsn.org (Postfix, from userid 1000) id CA155260260; Thu, 28 Oct 2010 21:31:50 +0100 (BST) Date: Thu, 28 Oct 2010 21:31:50 +0100 (BST) From: Iain Hibbert To: Maksim Yevmenkin In-Reply-To: Message-ID: References: <1287509041.022618.4884.nullmailer@galant.ukfsn.org> <1287561876.893861.6837.nullmailer@galant.ukfsn.org> <1287732977.227959.8695.nullmailer@galant.ukfsn.org> <1287738768.915002.8520.nullmailer@galant.ukfsn.org> <1287857292.298365.1038.nullmailer@galant.ukfsn.org> <1287874077.365931.1417.nullmailer@galant.ukfsn.org> <1287909035.704733.393.nullmailer@galant.ukfsn.org> <1288042690.562160.2361.nullmailer@galant.ukfsn.org> <1288081190.705299.12876.nullmailer@galant.ukfsn.org> User-Agent: Alpine 2.00 (NEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-bluetooth@freebsd.org Subject: Re: obexapp get failure X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2010 20:58:38 -0000 On Tue, 26 Oct 2010, Maksim Yevmenkin wrote: > not sure if obexftp still being actively used. last time i checked > there was a bunch of bluetooth-obex related code in gnome/kde etc. i > dont keep track of it - things change too fast in linux land :) perhaps development has ceased with obexftp. I know that there is an obexd in development for BlueZ now > > that patch does indeed make it work! fetching an 8k file with 4k MTU: > > thanks for trying it! could you please also try PUT (to and from > obexapp server) using wm6? sure obexapp client PUT -> wm6 server, no change (that code path is not used) wm6 client PUT -> obexapp server, it works ok but I see that the obexapp server does not ever actually provide a Connection ID but that we do send one that is zero with the Put response because it is not initialized to OBEXAPP_INVALID_CONNECTION_ID, eg < ACL data: handle 11 flags 0x02 dlen 16 L2CAP(d): cid 0x0048 len 12 [psm 3] RFCOMM(d): UIH: cr 0 dlci 20 pf 0 ilen 8 fcs 0xeb OBEX: Put rsp(f): status 100 len 8 Status 100 = Continue Connection ID (0xcb) = 0 so if I initialize that (in main.c, below) then it does not appear during a remote PUT. One thing that I can't check, what would happen if the "obexapp client GET -> remote" session get response did contain a Connection ID already, would we send it twice? iain --- main.c.orig 2010-10-22 07:29:06.000000000 +0100 +++ main.c 2010-10-27 22:12:01.000000000 +0100 @@ -108,6 +108,7 @@ main(int argc, char *argv[]) errx(1, "Could not allocate context.sbuffer"); context.mtu = OBEX_MAXIMUM_MTU; + context.connection_id = OBEXAPP_INVALID_CONNECTION_ID; memset(&custfunc, 0, sizeof(custfunc)); custfunc.connect = obexapp_transport_connect;