From owner-freebsd-bluetooth@FreeBSD.ORG Fri Feb 13 16:05:58 2009 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 138411065670 for ; Fri, 13 Feb 2009 16:05:58 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-gx0-f224.google.com (mail-gx0-f224.google.com [209.85.217.224]) by mx1.freebsd.org (Postfix) with ESMTP id AD91D8FC21 for ; Fri, 13 Feb 2009 16:05:57 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by gxk24 with SMTP id 24so910601gxk.19 for ; Fri, 13 Feb 2009 08:05:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=W7WwQwhdx0y9vD7M5txik8dkUYwuAn7NW93BtijgDNc=; b=rtwlHCsIpEtYY0Oei9PeXrFqb1UNrb9zeEfQA60HgybQO+frEkEkrjeHBNuKC3iO4v gqz6M4cGov1HVx1wwC0xsN/XTbhSRjNvSOX8xjzahoEygFeWE6mTDxrvrANSOq3KqV/6 F3+hOr0UlbR9veNyp1j1edFB/TCFqNHfb1J9s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=wRVdxkfof7ppMEj9aEhjhrf6kZlDiOnWEUCeI59xgkmbG2AAhpcfqKN548IWadregL RVq0o89sd8mmomRDqwCzXz7o9TiSrYezHz+j5Yb5UGGhti6mwS3g16rG0aclk1QndECo V/7MITwK702lDAgsF10jIE26AqBM9/CJbsrJk= MIME-Version: 1.0 Received: by 10.151.6.16 with SMTP id j16mr2214635ybi.47.1234541157057; Fri, 13 Feb 2009 08:05:57 -0800 (PST) In-Reply-To: <46cbfbb80902130153y10469bbdn1d2b1c04b1824358@mail.gmail.com> References: <46cbfbb80902120107x6ef309efs3d6b03e76c82fa78@mail.gmail.com> <46cbfbb80902130153y10469bbdn1d2b1c04b1824358@mail.gmail.com> Date: Fri, 13 Feb 2009 08:05:56 -0800 Message-ID: From: Maksim Yevmenkin To: Oleg Nauman Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: Trouble connecting HP Compaq 6720s with Nokia 3610 cell phone 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: Fri, 13 Feb 2009 16:05:58 -0000 Oleg, please keep freebsd-bluetooth@ cc'd. >>> I have a trouble connecting my Nokia 3610 cell phone via bluetooth link. >> >> as Iain already asked :) what exactly are you trying to do? > > Was trying to establish connection in both directions but failed. > Many thanks to Iain for this issue explanation - it seems my Nokia > searching for audio enhancements only. Was thinking it is part of > another trouble - I'm unable to start a session through obexapp (file > transfer for example). > > How is it looks like: > > # sdpcontrol -a Nokia search FTRN > > Record Handle: 0x00010002 > Service Class ID List: > OBEX File Transfer (0x1106) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 10 > OBEX (0x0008) > Bluetooth Profile Descriptor List: > OBEX File Transfer (0x1106) ver. 1.0 ok this looks promising. > # obexapp -c -a Nokia -C FTRN -f > > Just sits there ( well yes I know Bluetooth is slow enough so was > waiting for two hours first time ) well, this is not good :) > And what I can see in the log: first of all, please set those "hci_debug_level" and "l2cap_debug_level" knobs in you ubt0.conf back to their default values (or just remove them completely from your ubt0.conf). those should really be used in a controlled environment when debugging confirmed problem in the stack. the trace you sent is very low level and does not give me much context. hcidump(1) from the ports collection is the primary tool for troubleshooting problems like yours. when running hcidump(1) please make sure to write dump to a file, i.e. use -w switch. no need to set/change "connectable", "discoverable" and/or "role_switch" knobs because they set to "yes" by default. it is a good idea to always start hcsecd(8), i.e add "hcsecd_enable="yes'" to your /etc/rc.conf and make sure you have entries for all your bluetooth devices that require paring/authentication/encryption. so, if you could please 1) remove "hci_debug_level" and "l2cap_debug_level" knobs from your ubt0.conf and restart bluetooth device (/etc/rc.d/bluetooth restart ubt0) 2) start hcsecd(8), i.e. add hcsecd_enable="yes" to your /etc/rc.conf and then /etc/rc.d/hcsecd restart (i assume you already added pin code for your phone) 3) run (as root) hcidump -w nokia3610.bin 4) in another window run obexapp(1) client 5) wait for it to hang/stop/etc and then wait another minute or so. 6) terminate obexapp(1) client with ^C 7) terminate hcidump(1) with ^C 8) send me nokia3610.bin > So something is wrong I think and my question "Where is I'm wrong" i can not answer this question yet :) > still remains open. Or it is just a good example how is Bluetooth link > unreliable ? its not *that* unreliable :) thanks, max