From owner-freebsd-bluetooth@FreeBSD.ORG Tue Apr 10 18:17:04 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 44BE816A401 for ; Tue, 10 Apr 2007 18:17:04 +0000 (UTC) (envelope-from vittorio@de-martino.it) Received: from vsmtp14.tin.it (vsmtp14.tin.it [212.216.176.118]) by mx1.freebsd.org (Postfix) with ESMTP id 0CB9313C46A for ; Tue, 10 Apr 2007 18:17:04 +0000 (UTC) (envelope-from vittorio@de-martino.it) Received: from [10.155.100.8] (82.55.226.152) by vsmtp14.tin.it (7.2.072.1) (authenticated as vdemart1@tin.it) id 460BD6E500EB3F0C for freebsd-bluetooth@freebsd.org; Tue, 10 Apr 2007 20:05:03 +0200 From: Vittorio De Martino To: freebsd-bluetooth@freebsd.org Date: Tue, 10 Apr 2007 20:04:34 +0000 User-Agent: KMail/1.9.5 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704102004.34814.vittorio@de-martino.it> Subject: tomtom serial connection 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: Tue, 10 Apr 2007 18:17:04 -0000 I read in the internet that it is possible to connect the tomtom go gps to a computer via bluetooth as a serial connection therefore allowing a gps program such as gpsdrive to read nmea data from it. If I victor$ sdpcontrol -a tomtom browse Record Handle: 00000000 Service Class ID List: Service Discovery Server (0x1000) Protocol Descriptor List: L2CAP (0x0100) Protocol specific parameter #1: u/int/uuid16 1 Protocol specific parameter #2: u/int/uuid16 1 Record Handle: 0x00010000 Service Class ID List: Browse Group Descriptor (0x1001) But trying to connect it to a serial device: victor$ rfcomm_sppd -a tomtom -t /dev/ttyp6 rfcomm_sppd: Could not obtain RFCOMM channel: Attribute not found How can I make it? Ciao Vittorio From owner-freebsd-bluetooth@FreeBSD.ORG Tue Apr 10 18:49:31 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CF3D516A402 for ; Tue, 10 Apr 2007 18:49:31 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from mh1.centtech.com (moat3.centtech.com [64.129.166.50]) by mx1.freebsd.org (Postfix) with ESMTP id A48FD13C483 for ; Tue, 10 Apr 2007 18:49:31 +0000 (UTC) (envelope-from anderson@freebsd.org) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh1.centtech.com (8.13.8/8.13.8) with ESMTP id l3AIQ7RZ041897; Tue, 10 Apr 2007 13:26:07 -0500 (CDT) (envelope-from anderson@freebsd.org) Message-ID: <461BD6BF.1030505@freebsd.org> Date: Tue, 10 Apr 2007 13:26:07 -0500 From: Eric Anderson User-Agent: Thunderbird 1.5.0.10 (X11/20070320) MIME-Version: 1.0 To: Vittorio De Martino References: <200704102004.34814.vittorio@de-martino.it> In-Reply-To: <200704102004.34814.vittorio@de-martino.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.88.4/3064/Tue Apr 10 11:25:23 2007 on mh1.centtech.com X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=8.0 tests=AWL,BAYES_00 autolearn=ham version=3.1.6 X-Spam-Checker-Version: SpamAssassin 3.1.6 (2006-10-03) on mh1.centtech.com Cc: freebsd-bluetooth@freebsd.org Subject: Re: tomtom serial connection 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: Tue, 10 Apr 2007 18:49:31 -0000 On 04/10/07 15:04, Vittorio De Martino wrote: > I read in the internet that it is possible to connect the tomtom go gps to a > computer via bluetooth as a serial connection therefore allowing a gps > program such as gpsdrive to read nmea data from it. > > If I > > victor$ sdpcontrol -a tomtom browse > > Record Handle: 00000000 > Service Class ID List: > Service Discovery Server (0x1000) > Protocol Descriptor List: > L2CAP (0x0100) > Protocol specific parameter #1: u/int/uuid16 1 > Protocol specific parameter #2: u/int/uuid16 1 > > Record Handle: 0x00010000 > Service Class ID List: > Browse Group Descriptor (0x1001) > > But trying to connect it to a serial device: > > victor$ rfcomm_sppd -a tomtom -t /dev/ttyp6 > rfcomm_sppd: Could not obtain RFCOMM channel: Attribute not found > > > How can I make it? I don't see RFCOMM in the list above. Here's what I do (for my Rikaline bluetooth gps): hccontrol -n ubt0hci inquiry gives me something like: Inquiry result, num_responses=1 Inquiry result #0 BD_ADDR: 00:00:00:00:67:4f Page Scan Rep. Mode: 0x1 Page Scan Period Mode: 00 Page Scan Mode: 00 Class: 00:00:00 Clock offset: 0x44da Then: sdpcontrol -a 00:00:00:00:67:4f browse Gives: Record Handle: 0x00090001 Service Class ID List: Serial Port (0x1101) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 1 Then: rfcomm_sppd -a 00:00:00:00:67:4f -t /dev/ttyp6 and in another xterm: $ sudo cu -l /dev/ttyp6 Connected $GPGGA,000156.20,0000.0000,N,00000.0000,E,0,00,0.00,0.00,M,0.00,M,,*6D $GPGSA,A,1,,,,,,,,,,,,,0.00,0.00,0.00*00 $GPVTG,0.00,T,,,0.00,N,0.00,K,N*7F $GPGLL,0000.0000,N,00000.0000,E,000156.20,V,N*71 $GPRMC,000156.20,V,0000.0000,N,00000.0000,E,0.00,0.00,220899,,,N*4E [..snip..] Eric From owner-freebsd-bluetooth@FreeBSD.ORG Tue Apr 10 19:08:54 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A1E9316A404 for ; Tue, 10 Apr 2007 19:08:54 +0000 (UTC) (envelope-from ml-vic@de-martino.it) Received: from vsmtp12.tin.it (vsmtp12.tin.it [212.216.176.206]) by mx1.freebsd.org (Postfix) with ESMTP id 68BBD13C480 for ; Tue, 10 Apr 2007 19:08:54 +0000 (UTC) (envelope-from ml-vic@de-martino.it) Received: from [10.155.100.8] (82.55.226.152) by vsmtp12.tin.it (7.2.072.1) (authenticated as vdemart1@tin.it) id 460BEED200EC1FC8 for freebsd-bluetooth@freebsd.org; Tue, 10 Apr 2007 20:57:09 +0200 From: Vittorio De Martino To: freebsd-bluetooth@freebsd.org Date: Tue, 10 Apr 2007 20:56:40 +0000 User-Agent: KMail/1.9.5 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200704102056.41056.ml-vic@de-martino.it> Subject: Connecting a tomtom gps to an fbsd 6.2 box via BT 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: Tue, 10 Apr 2007 19:08:54 -0000 I read in the internet that it is possible to connect the tomtom go gps to = a=20 computer via bluetooth as a serial connection therefore =A0allowing a gps=20 program such as gpsdrive to read nmea data from it. If I=20 victor$ sdpcontrol -a tomtom browse Record Handle: 00000000 Service Class ID List: =A0 =A0 =A0 =A0 Service Discovery Server (0x1000) Protocol Descriptor List: =A0 =A0 =A0 =A0 L2CAP (0x0100) =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Protocol specific parameter #1: u/int/uuid1= 6 1 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Protocol specific parameter #2: u/int/uuid1= 6 1 Record Handle: 0x00010000 Service Class ID List: =A0 =A0 =A0 =A0 Browse Group Descriptor (0x1001) But trying to connect it to a serial device: victor$ rfcomm_sppd -a tomtom -t /dev/ttyp6 rfcomm_sppd: Could not obtain RFCOMM channel: Attribute not found How can I make it? Ciao Vittorio From owner-freebsd-bluetooth@FreeBSD.ORG Tue Apr 10 19:59:55 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D74CE16A401 for ; Tue, 10 Apr 2007 19:59:55 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from smarthost01.eng.net (smarthost01.eng.net [213.130.146.173]) by mx1.freebsd.org (Postfix) with ESMTP id A138D13C459 for ; Tue, 10 Apr 2007 19:59:55 +0000 (UTC) (envelope-from plunky@rya-online.net) Received: from netmail01.eng.net ([213.130.128.38] helo=rya-online.net) by smarthost01.eng.net with smtp (Exim 4.62) (envelope-from ) id 1HbMVI-0007F9-GH; Tue, 10 Apr 2007 20:59:53 +0100 Received: (nullmailer pid 666 invoked by uid 1000); Tue, 10 Apr 2007 19:58:10 -0000 Date: Tue, 10 Apr 2007 20:58:09 +0100 (BST) To: Eric Anderson In-Reply-To: <461BD6BF.1030505@freebsd.org> References: <200704102004.34814.vittorio@de-martino.it> <461BD6BF.1030505@freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1176235090.016851.473.nullmailer@galant.ukfsn.org> From: Iain Hibbert Cc: freebsd-bluetooth@freebsd.org, Vittorio De Martino Subject: Re: tomtom serial connection 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: Tue, 10 Apr 2007 19:59:55 -0000 On Tue, 10 Apr 2007, Eric Anderson wrote: > On 04/10/07 15:04, Vittorio De Martino wrote: > > How can I make it? > > I don't see RFCOMM in the list above. yeah, Vittorio should try sdpcontrol -a tomtom search sp to see if the 'Serial Port' service is available.. > Record Handle: 0x00090001 > Service Class ID List: > Serial Port (0x1101) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 1 in the above example, you can connect to channel 1 directly since you know that the Serial Port service is there.. rfcomm_sppd -a xxx -t /dev/ttyp6 -c 1 perhaps if Vittorio can't find any serial port, try connecting to all the channels between 1 and 30 to see if he can find the one that the tomtom is listening on. iain From owner-freebsd-bluetooth@FreeBSD.ORG Tue Apr 10 20:31:24 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D125116A400 for ; Tue, 10 Apr 2007 20:31:24 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by mx1.freebsd.org (Postfix) with ESMTP id 894A613C4C5 for ; Tue, 10 Apr 2007 20:31:24 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so2154424ana for ; Tue, 10 Apr 2007 13:31:23 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=kPocZx1B43YL+Q1UqmB/Mkxsmno3BTuJ+qFedA9VDZsqJUrah7UKiIWh7Jg1F0kHyY52Wq3pvvZ3FKsRjBXZgjNmbM4z5cMNNZSK99GRiS54+JpyaT18kJEANlCRb8z6+2lWT8Y296/efp9cXIgQKP5KsHuvtFLQzJjDfx6Ghv4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=MaXCTJn3tdJfqaicM6VYa0Kmh7g6Qkohn+Mtiz+p6X8dCR5HCA0FL02zHv9LYzMkuXCng7zYhdP3o4MnZ+ULe1FQEmY5kQBsdZDtdCpszcONiIB6msP6K4YQNSHuLEGpQq+A1ADhf6BNZ0zTH2jJxi7ycwaYZJrgX282j2/CZAI= Received: by 10.100.124.5 with SMTP id w5mr5264195anc.1176237083552; Tue, 10 Apr 2007 13:31:23 -0700 (PDT) Received: by 10.100.111.18 with HTTP; Tue, 10 Apr 2007 13:31:23 -0700 (PDT) Message-ID: Date: Tue, 10 Apr 2007 13:31:23 -0700 From: "Maksim Yevmenkin" To: "Vittorio De Martino" In-Reply-To: <1176235090.016851.473.nullmailer@galant.ukfsn.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <200704102004.34814.vittorio@de-martino.it> <461BD6BF.1030505@freebsd.org> <1176235090.016851.473.nullmailer@galant.ukfsn.org> Cc: freebsd-bluetooth@freebsd.org Subject: Re: tomtom serial connection 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: Tue, 10 Apr 2007 20:31:24 -0000 On 4/10/07, Iain Hibbert wrote: > On Tue, 10 Apr 2007, Eric Anderson wrote: > > > On 04/10/07 15:04, Vittorio De Martino wrote: > > > How can I make it? > > > > I don't see RFCOMM in the list above. > > yeah, Vittorio should try > sdpcontrol -a tomtom search sp > > to see if the 'Serial Port' service is available.. > > > Record Handle: 0x00090001 > > Service Class ID List: > > Serial Port (0x1101) > > Protocol Descriptor List: > > L2CAP (0x0100) > > RFCOMM (0x0003) > > Protocol specific parameter #1: u/int8/bool 1 > > in the above example, you can connect to channel 1 directly since you know > that the Serial Port service is there.. > > rfcomm_sppd -a xxx -t /dev/ttyp6 -c 1 > > perhaps if Vittorio can't find any serial port, try connecting to all the > channels between 1 and 30 to see if he can find the one that the tomtom is > listening on. well, it might or might not work. was tomtom gps previously paired with another bluetooth device? some devices are quite paranoid and will not accept any incoming connection unless it comes from "known/trusted" device. if fact, some devices wont even advertise service once they were paired. the assumption here is that "known/trusted" device saved all required information (such as rfcomm channel number, link key or pin code) locally and will use it next time to connect. so, if your tomtom gps supports "pairing" mode you need to put it into this mode first time you try to connect "new" device to tomtom gps. also, as others already pointed out, it is better to use % sdpcontrol -a xxxx search sp instead of 'browse'. many devices do not bother to put advertised services into public browse group, so 'browse' will not find them. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 11 17:08:21 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3297F16A403 for ; Wed, 11 Apr 2007 17:08:21 +0000 (UTC) (envelope-from vittorio@de-martino.it) Received: from vsmtp14.tin.it (vsmtp14.tin.it [212.216.176.118]) by mx1.freebsd.org (Postfix) with ESMTP id F02B613C4C7 for ; Wed, 11 Apr 2007 17:08:20 +0000 (UTC) (envelope-from vittorio@de-martino.it) Received: from [10.155.100.8] (82.55.226.152) by vsmtp14.tin.it (7.2.072.1) (authenticated as vdemart1@tin.it) id 460BD6E500FC8C2E for freebsd-bluetooth@freebsd.org; Wed, 11 Apr 2007 19:08:19 +0200 From: Vittorio De Martino To: freebsd-bluetooth@freebsd.org Date: Wed, 11 Apr 2007 19:07:51 +0000 User-Agent: KMail/1.9.5 References: <200704102004.34814.vittorio@de-martino.it> <1176235090.016851.473.nullmailer@galant.ukfsn.org> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200704111907.52164.vittorio@de-martino.it> Subject: Re: tomtom serial connection 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, 11 Apr 2007 17:08:21 -0000 :=20 Yes, I can smoothly pair the tomtom gps to my nokia cellular phone e61. No = pin=20 is required. The connection via umts is required from time to time by the=20 tomtom site to pdate traffic news . I tried the following but SP doesn't seem to exist victor$ sudo l2ping -a tomtom 44 bytes from tomtom seq_no=3D0 time=3D246.214 ms result=3D0 44 bytes from tomtom seq_no=3D1 time=3D28.889 ms result=3D0 44 bytes from tomtom seq_no=3D2 time=3D31.084 ms result=3D0 ^C victor$ sudo sdpcontrol -a tomtom search sp victor$ victor$ sudo rfcomm_sppd -a tomtom -t /dev/ttyp6 -c 1 rfcomm_sppd: Could not connect socket: Connection refused victor$ sudo rfcomm_sppd -a tomtom -t /dev/ttyp6 -c 2 rfcomm_sppd: Could not connect socket: Connection refused victor$ sudo rfcomm_sppd -a tomtom -t /dev/ttyp6 -c 3 rfcomm_sppd: Could not connect socket: Connection refused Ciao Vittorio Alle 20:31, marted=EC 10 aprile 2007, Maksim Yevmenkin ha scritto: > On 4/10/07, Iain Hibbert wrote: > > On Tue, 10 Apr 2007, Eric Anderson wrote: > > > On 04/10/07 15:04, Vittorio De Martino wrote: > > > > How can I make it? > > > > > > I don't see RFCOMM in the list above. > > > > yeah, Vittorio should try > > sdpcontrol -a tomtom search sp > > > > to see if the 'Serial Port' service is available.. > > > > > Record Handle: 0x00090001 > > > Service Class ID List: > > > Serial Port (0x1101) > > > Protocol Descriptor List: > > > L2CAP (0x0100) > > > RFCOMM (0x0003) > > > Protocol specific parameter #1: u/int8/bool 1 > > > > in the above example, you can connect to channel 1 directly since you > > know that the Serial Port service is there.. > > > > rfcomm_sppd -a xxx -t /dev/ttyp6 -c 1 > > > > perhaps if Vittorio can't find any serial port, try connecting to all t= he > > channels between 1 and 30 to see if he can find the one that the tomtom > > is listening on. > > well, it might or might not work. was tomtom gps previously paired > with another bluetooth device? > > some devices are quite paranoid and will not accept any incoming > connection unless it comes from "known/trusted" device. if fact, some > devices wont even advertise service once they were paired. the > assumption here is that "known/trusted" device saved all required > information (such as rfcomm channel number, link key or pin code) > locally and will use it next time to connect. > > so, if your tomtom gps supports "pairing" mode you need to put it into > this mode first time you try to connect "new" device to tomtom gps. > > also, as others already pointed out, it is better to use > > % sdpcontrol -a xxxx search sp > > instead of 'browse'. many devices do not bother to put advertised > services into public browse group, so 'browse' will not find them. > > thanks, > max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 12 00:30:16 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 84BDB16A402 for ; Thu, 12 Apr 2007 00:30:16 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.240]) by mx1.freebsd.org (Postfix) with ESMTP id 46B8613C483 for ; Thu, 12 Apr 2007 00:30:16 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so414673ana for ; Wed, 11 Apr 2007 17:30:15 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Rk+V+ohAX/2UEYhoFmkgVlfA5tbONUqn/Za/h6SMVxs2DQrW3f9gLRrIKbKhvSck3PFyu3RGJRl+5OLkSJ7e2Gv+6PbmBgMv0QQOXE4/jkBsT9UwZstkVeHKvB+ZmOt+jpqfH/gcrMtvtR/OXnd34peqjm+HOiFsL7j61Eg/nuA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=p1dzP+3GVqCKjfKo2pQRGnX7c0zvviMTnnZ1xhINeyg3/u5cLQOHswzYO4hZOdczYXqIbgE3SgwkkYUqHixU38lo1eks4F8ee3i/0wTM2SaJ/TL91Jdh/y1QRkygIdvdyJcRVe4avTLgq1K4EgKmLrpsLlqsYvmBaLJ2kJnDoug= Received: by 10.100.31.2 with SMTP id e2mr916991ane.1176337815233; Wed, 11 Apr 2007 17:30:15 -0700 (PDT) Received: by 10.100.111.18 with HTTP; Wed, 11 Apr 2007 17:30:15 -0700 (PDT) Message-ID: Date: Wed, 11 Apr 2007 17:30:15 -0700 From: "Maksim Yevmenkin" To: "Vittorio De Martino" In-Reply-To: <200704111907.52164.vittorio@de-martino.it> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <200704102004.34814.vittorio@de-martino.it> <1176235090.016851.473.nullmailer@galant.ukfsn.org> <200704111907.52164.vittorio@de-martino.it> Cc: freebsd-bluetooth@freebsd.org Subject: Re: tomtom serial connection 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, 12 Apr 2007 00:30:16 -0000 On 4/11/07, Vittorio De Martino wrote: > : > Yes, I can smoothly pair the tomtom gps to my nokia cellular phone e61. N= o pin > is required. The connection via umts is required from time to time by the > tomtom site to pdate traffic news . > did you try to pair your tomtom gps with your pc? > I tried the following but SP doesn't seem to exist > > victor$ sudo l2ping -a tomtom > 44 bytes from tomtom seq_no=3D0 time=3D246.214 ms result=3D0 > 44 bytes from tomtom seq_no=3D1 time=3D28.889 ms result=3D0 > 44 bytes from tomtom seq_no=3D2 time=3D31.084 ms result=3D0 ??? l2ping has nothing to do with sp, just tells you that remote side answers l2cap, but we already know this, because sdpcontrol returns stuff. > victor$ sudo sdpcontrol -a tomtom search sp > victor$ ok, stupid question, is your tomtom a complete unit with screen and buttons, etc. or just a standalone bluetooth gps receiver with no user interface at all? could you please provide model number for your tomtom device? can you force your tomtom gps into pairing mode and then try 'sdpcontrol -a tomtom search sp'? thanks, max > victor$ sudo rfcomm_sppd -a tomtom -t /dev/ttyp6 -c 1 > rfcomm_sppd: Could not connect socket: Connection refused > victor$ sudo rfcomm_sppd -a tomtom -t /dev/ttyp6 -c 2 > rfcomm_sppd: Could not connect socket: Connection refused > victor$ sudo rfcomm_sppd -a tomtom -t /dev/ttyp6 -c 3 > rfcomm_sppd: Could not connect socket: Connection refused > > Ciao > Vittorio > > Alle 20:31, marted=EC 10 aprile 2007, Maksim Yevmenkin ha scritto: > > On 4/10/07, Iain Hibbert wrote: > > > On Tue, 10 Apr 2007, Eric Anderson wrote: > > > > On 04/10/07 15:04, Vittorio De Martino wrote: > > > > > How can I make it? > > > > > > > > I don't see RFCOMM in the list above. > > > > > > yeah, Vittorio should try > > > sdpcontrol -a tomtom search sp > > > > > > to see if the 'Serial Port' service is available.. > > > > > > > Record Handle: 0x00090001 > > > > Service Class ID List: > > > > Serial Port (0x1101) > > > > Protocol Descriptor List: > > > > L2CAP (0x0100) > > > > RFCOMM (0x0003) > > > > Protocol specific parameter #1: u/int8/bool 1 > > > > > > in the above example, you can connect to channel 1 directly since you > > > know that the Serial Port service is there.. > > > > > > rfcomm_sppd -a xxx -t /dev/ttyp6 -c 1 > > > > > > perhaps if Vittorio can't find any serial port, try connecting to all= the > > > channels between 1 and 30 to see if he can find the one that the tomt= om > > > is listening on. > > > > well, it might or might not work. was tomtom gps previously paired > > with another bluetooth device? > > > > some devices are quite paranoid and will not accept any incoming > > connection unless it comes from "known/trusted" device. if fact, some > > devices wont even advertise service once they were paired. the > > assumption here is that "known/trusted" device saved all required > > information (such as rfcomm channel number, link key or pin code) > > locally and will use it next time to connect. > > > > so, if your tomtom gps supports "pairing" mode you need to put it into > > this mode first time you try to connect "new" device to tomtom gps. > > > > also, as others already pointed out, it is better to use > > > > % sdpcontrol -a xxxx search sp > > > > instead of 'browse'. many devices do not bother to put advertised > > services into public browse group, so 'browse' will not find them. > > > > thanks, > > max > _______________________________________________ > freebsd-bluetooth@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth > To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@freebsd.o= rg" > From owner-freebsd-bluetooth@FreeBSD.ORG Sat Apr 14 22:42:05 2007 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C254516A40F for ; Sat, 14 Apr 2007 22:42:05 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.242]) by mx1.freebsd.org (Postfix) with ESMTP id 79B7F13C484 for ; Sat, 14 Apr 2007 22:42:05 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by an-out-0708.google.com with SMTP id c24so1331570ana for ; Sat, 14 Apr 2007 15:42:04 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=WwVaUg3Rk04VnKmdtkYEdo5NGn/BO/Leti3odPekoGMo32SzB1jQTwcxNFAbto6Vh3F0zio1JYqBmNsFUQNGG6ldLpZem3ZWFmLqUsijTtkfVqHJMjSNXza2doTGgt0qQDJO9T4L6C5wOJg+4zGJtsai22kGeopywOP9gd3auZU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SYO4IOthVzv8zOl6wKw3vYZLn31mI03gIBFBXrfCJ0KnkUhlhnhg7VjRZHaR7HacHxBmJQ3L7gW9SwDJO5Zjge6jWuRxe5XIaEw0eyIQRvN3ghJI4eQarf9Ik1kJls7pNu7jA74WlmG1qdYJssQywdu9Q5sfSNoPkPi5N95Fx9c= Received: by 10.100.141.13 with SMTP id o13mr3457891and.1176590524715; Sat, 14 Apr 2007 15:42:04 -0700 (PDT) Received: by 10.100.111.18 with HTTP; Sat, 14 Apr 2007 15:42:04 -0700 (PDT) Message-ID: Date: Sat, 14 Apr 2007 15:42:04 -0700 From: "Maksim Yevmenkin" To: "=mato=" In-Reply-To: <462076EE.9040402@pobox.sk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <462076EE.9040402@pobox.sk> Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: BT / hcsecd(8) -- changing PINs and dumping link keys -- bug? 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: Sat, 14 Apr 2007 22:42:05 -0000 Hello, > I think I've run into a problem (bug?) with hcsecd(8). > > The documentation says that upon sending HUP signal to hcsecd it should > reread its configuration and dump the link keys file. So after I changed yes, that is correct > PINs for my BT devices on both of my laptops (in hcsecd.conf) I sent HUPs > and reinitialised BT devices. But reopening of connection failed > (permission denied). I rerun both hcsecd daemons in foreground and noticed > that upon receiving HUP signal hcsecd does not use PIN as it does the very > first time but use key which should have been dumped. So then I killed the i think you misunderstood the word "dump". in this context "dump" means "save" the cached (in memory) link keys into the /var/run/hcsecd.keys file. the man page states "... To preserve link keys between restarts the hcsecd daemon dumps link keys for all entries in the /var/db/hcsecd.keys link keys file ..." "dump" does not mean "forget" or "delete" here. the man page also says "... For any given entry, the link key takes precedence over the PIN code ..." it seems like, in your case, link key existed and hcsecd(8) used it. it does not matter that you have changed the pin code. pin code will only be used if there is no link key. > daemons, deleted their hcsecd.keys files and started up the daemons again. > After that my new PINs got accepted and connection succeeded. well, yes, there is no way to delete cached link key other than deleting the key from the /var/db/hcsecd.keys and restarting hcsecd(8). the assumption here is that pairing has to done only once. if someone wants to re-pair the same devices then extra effort is justified. > I don't think this is intended behaviour, but if it is I believe it should > be clearly documented (the current man page suggests something else). from what i can see, hcsecd(8) did the right thing here. thanks, max