From owner-freebsd-bluetooth@FreeBSD.ORG Wed Feb 15 06:08:26 2006 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org 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 AE2E916A420 for ; Wed, 15 Feb 2006 06:08:26 +0000 (GMT) (envelope-from mmumby@xtra.co.nz) Received: from mta201-rme.xtra.co.nz (mta201-rme.xtra.co.nz [210.86.15.144]) by mx1.FreeBSD.org (Postfix) with ESMTP id D18A543D4C for ; Wed, 15 Feb 2006 06:08:25 +0000 (GMT) (envelope-from mmumby@xtra.co.nz) Received: from web3-rme.xtra.co.nz ([210.86.15.193]) by mta201-rme.xtra.co.nz with ESMTP id <20060215060824.ZWSG1862.mta201-rme.xtra.co.nz@web3-rme.xtra.co.nz>; Wed, 15 Feb 2006 19:08:24 +1300 Received: from orac ([222.152.21.232]) by web3-rme.xtra.co.nz with SMTP id <20060215060823.YFWI22512.web3-rme.xtra.co.nz@orac>; Wed, 15 Feb 2006 19:08:23 +1300 From: "Mark Mumby" To: "Maksim Yevmenkin" Date: Wed, 15 Feb 2006 19:08:35 +1300 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: <43F0E117.2060509@savvis.net> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 Cc: freebsd-bluetooth@freebsd.org Subject: RE: Pairing problem with Motorola E398 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: Wed, 15 Feb 2006 06:08:26 -0000 Max, Absolutely fantastic, worked first time. Thanks for your help. Mark -----Original Message----- From: Maksim Yevmenkin [mailto:maksim.yevmenkin@savvis.net] Sent: Tuesday, 14 February 2006 8:42 a.m. To: Mark Mumby Cc: freebsd-bluetooth@freebsd.org Subject: Re: Pairing problem with Motorola E398 Mark, > I have a problem that i hope you can help with. > > I am trying to pair my E398 with my FreeBSD 5.4 box. Basicly nothing > happens. > I have only recently added bluetooth to my setup and i am new to it. > > I am able to pair my iPAQ 2110 and my PC to the FreeBSD box. > > I have been through the configs many times and believe the are correct - > > When i start Bluetooth i get - > firewall# /etc/rc.bluetooth start ubt0 [...] looks good. > When i put the phone into "Find Me" (only allows 60 sec) mode i get - > firewall# hccontrol -n ubt0hci inquiry > Inquiry result, num_responses=1 > Inquiry result #0 > BD_ADDR: MarkCell > Page Scan Rep. Mode: 0x1 > Page Scan Period Mode: 00 > Page Scan Mode: 00 > Class: 52:22:04 > Clock offset: 0x232 > Inquiry complete. Status: No error [00] looks good > Then do a name query - > firewall# hccontrol -n ubt0hci remote_name_request markcell 0 0 0 > BD_ADDR: MarkCell > Name: MarkCell looks good > Then do a spdcontrol -a markcell browse (this can be done at anytime oes not > need to be in "Find Me" mode - > > firewall# /usr/sbin/spdcontrol -a markcell browse [...] looks good. > I have addeded MarkCell to the host file - > 00:0a:28:32:0e:25 MarkCell > > Here is the hcsecd.conf entry - > device { > bdaddr 00:0a:28:32:0e:25; > name "MarkCell"; > key nokey; > pin "0000"; > } looks fine > But when i run hcsecd -d and put the phone into "Find Me" mode nothing seems > to happen. hcsecd(8) will NOT actively connect to your phone. all hcsecd(8) does is answers hci pin code/link key request events. one of the devices (either phone or pc) has to request authentication. many devices (such as phones) only ask for authentication when remote device is trying to use service. first, make sure that hcsecd(8) is running then do # hccontrol -n ubt0hci write_authentication_enable 1 now try to do % sdpcontrol -a MarkCell browse you should get request for pin code in hcsecd(8). after the link key was generated it will be stored in /var/db/hcsecd.keys file. next time the phone will request authentication this key will be used. note that you MUST run hcsecd(8) at all times. now you can turn authentication off # hccontrol -n ubt0hci write_authentication_enable 0 thanks, max