From owner-freebsd-bluetooth@FreeBSD.ORG Tue Aug 22 13:45:08 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 841FC16A4E2 for ; Tue, 22 Aug 2006 13:45:08 +0000 (UTC) (envelope-from freebsd@abv.bg) Received: from smtp-out.abv.bg (smtp-out.abv.bg [194.153.145.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A8AC43D76 for ; Tue, 22 Aug 2006 13:45:02 +0000 (GMT) (envelope-from freebsd@abv.bg) Received: from mail04.abv.bg (mail04.ni.bg [192.168.151.19]) by smtp-out.abv.bg (Postfix) with ESMTP id 2BD37EB7BA for ; Tue, 22 Aug 2006 16:45:01 +0300 (EEST) Received: from mail04.abv.bg (localhost.localdomain [127.0.0.1]) by mail04.abv.bg (Postfix) with ESMTP id 778AB8AEEB for ; Tue, 22 Aug 2006 16:45:00 +0300 (EEST) Message-ID: <208735345.378631156254300487.JavaMail.nobody@mail04.abv.bg> Date: Tue, 22 Aug 2006 16:45:00 +0300 (EEST) From: Mario Pavlov To: freebsd-bluetooth@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 8bit X-Mailer: AbvMail 1.0 X-Originating-IP: 85.187.214.163 Subject: pairing PC and 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: Tue, 22 Aug 2006 13:45:08 -0000 Hello guys I'm tring to get my FreeBSD-6.1-STABLE to transfer files with my NOKIA 6021 phone here is what I do: # kldload ng_ubt # /etc/rc.bluetooth start ubt0 BD_ADDR: 11:11:11:11:11:11 Features: 0xbf 0xfe 0x8d 0x78 0x8 0x18 00 00 <3-Slot> <5-Slot> Max. ACL packet size: 678 bytes Number of ACL packets: 8 Max. SCO packet size: 48 bytes Number of SCO packets: 10 # hccontrol -n ubt0hci inquiry Inquiry result, num_responses=1 Inquiry result #0 BD_ADDR: 00:17:b0:53:55:29 Page Scan Rep. Mode: 0x2 Page Scan Period Mode: 0x2 Page Scan Mode: 00 Class: 52:02:04 Clock offset: 0x458 Inquiry complete. Status: No error [00] # hccontrol -n ubt0hci remote_name_request 00:17:b0:53:55:29 0 0 0 BD_ADDR: 00:17:b0:53:55:29 Name: Tilifon everything looks fine this is my config # cat /etc/bluetooth/hcsecd.conf device { bdaddr 00:00:00:00:00:00; name "Default entry"; key nokey; pin nopin; } device { bdaddr 00:17:b0:53:55:29; name "Tilifon"; key nokey; pin "nopin"; } so I run the hcsecd daemon and I try: # obexapp -c -a 00:17:b0:53:55:29 -C 1 my phone tells me that some device want to pair with it I chose accept and the phone is prompting me for passcode... I enter something and it sasy "pairing failed" and the obexapp exits how to deal with this passcode ? how to tell the obexapp to use some passcode ? I've also tried this: # hccontrol -n ubt0hci write_authentication_enable 1 # sdpcontrol -a 00:17:b0:53:55:29 browse and it prompts me for passcode again and the result is the same: "pairing failed" than I've tried this: # hccontrol -n ubt0hci write_authentication_enable 0 # sdpcontrol -a 00:17:b0:53:55:29 browse Record Handle: 0x00010078 Service Class ID List: Dial-Up Networking (0x1103) Generic Networking (0x1201) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 1 Bluetooth Profile Descriptor List: Dial-Up Networking (0x1103) ver. 1.0 Record Handle: 0x00010079 Service Class ID List: Serial Port (0x1101) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 15 Record Handle: 0x0001007a Service Class ID List: Serial Port (0x1101) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 3 Record Handle: 0x0001007b Service Class ID List: Handsfree Audio Gateway (0x111f) Generic Audio (0x1203) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 13 Bluetooth Profile Descriptor List: Handsfree (0x111e) ver. 1.1 Record Handle: 0x0001007c Service Class ID List: Headset Audio Gateway (0x1112) Generic Audio (0x1203) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 12 Bluetooth Profile Descriptor List: Headset (0x1108) ver. 1.0 Record Handle: 0x00010081 Service Class ID List: SIM Access (0x112d) Generic Telephony (0x1204) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 4 Bluetooth Profile Descriptor List: SIM Access (0x112d) ver. 1.0 Record Handle: 0x00010083 Service Class ID List: OBEX Object Push (0x1105) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 9 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX Object Push (0x1105) ver. 1.0 Record Handle: 0x00010084 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 Record Handle: 0x00010086 Service Class ID List: 0x00000002-0000-1000-8000-0002ee000002 Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 11 OBEX (0x0008) and again with obex, but still the same... can I anyone help me please thank you :) ----------------------------------------------------------------- http://ide.li/ - портал за българите по света. Статии, новини, форуми, снимки, информация. From owner-freebsd-bluetooth@FreeBSD.ORG Tue Aug 22 17:12:18 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 0ECB816A4DA for ; Tue, 22 Aug 2006 17:12:18 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE50C43D5A for ; Tue, 22 Aug 2006 17:12:17 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 96D243BE4A; Tue, 22 Aug 2006 12:12:16 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 27312-01-24; Tue, 22 Aug 2006 12:12:16 -0500 (CDT) Received: from [10.12.163.251] (unknown [10.12.163.251]) by mailgate1b.savvis.net (Postfix) with ESMTP id 381D13BE43; Tue, 22 Aug 2006 12:12:16 -0500 (CDT) Message-ID: <44EB3AEF.2030701@savvis.net> Date: Tue, 22 Aug 2006 10:12:15 -0700 From: Maksim Yevmenkin User-Agent: Thunderbird 1.5.0.2 (X11/20060603) MIME-Version: 1.0 To: Mario Pavlov References: <208735345.378631156254300487.JavaMail.nobody@mail04.abv.bg> In-Reply-To: <208735345.378631156254300487.JavaMail.nobody@mail04.abv.bg> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at savvis.net Cc: freebsd-bluetooth@freebsd.org Subject: Re: pairing PC and 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: Tue, 22 Aug 2006 17:12:18 -0000 Mario, [...] > # cat /etc/bluetooth/hcsecd.conf > device { > bdaddr 00:00:00:00:00:00; > name "Default entry"; > key nokey; > pin nopin; > } > > device { > bdaddr 00:17:b0:53:55:29; > name "Tilifon"; > key nokey; > pin "nopin"; > } you need to specify pin code, for example pin "1234"; > so I run the hcsecd daemon > > and I try: > # obexapp -c -a 00:17:b0:53:55:29 -C 1 > > my phone tells me that some device want to pair with it > I chose accept > and the phone is prompting me for passcode... > I enter something and it sasy "pairing failed" when phone prompts, you need to enter the same pin code you have put into /etc/bluetooth/hcsecd.conf, i.e. for example above you need to enter 1234 on the phone. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Aug 22 20:51:53 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 3BD7F16A4DD for ; Tue, 22 Aug 2006 20:51:53 +0000 (UTC) (envelope-from freebsd@abv.bg) Received: from smtp-out.abv.bg (smtp-out.abv.bg [194.153.145.99]) by mx1.FreeBSD.org (Postfix) with ESMTP id B387443D64 for ; Tue, 22 Aug 2006 20:51:46 +0000 (GMT) (envelope-from freebsd@abv.bg) Received: from mail02.abv.bg (app9.ni.bg [192.168.151.43]) by smtp-out.abv.bg (Postfix) with ESMTP id A2B9AEB2D4; Tue, 22 Aug 2006 23:51:45 +0300 (EEST) Received: from mail02.abv.bg (localhost.localdomain [127.0.0.1]) by mail02.abv.bg (Postfix) with ESMTP id 94B6D86B54; Tue, 22 Aug 2006 23:51:45 +0300 (EEST) Message-ID: <1098400120.449091156279905606.JavaMail.nobody@mail02.abv.bg> Date: Tue, 22 Aug 2006 23:51:45 +0300 (EEST) From: Mario Pavlov To: Maksim Yevmenkin MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 8bit X-Mailer: AbvMail 1.0 X-Originating-IP: 85.187.137.6 Cc: freebsd-bluetooth@freebsd.org Subject: Re: Re: pairing PC and 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: Tue, 22 Aug 2006 20:51:53 -0000 >Mario, > >[...] > >> # cat /etc/bluetooth/hcsecd.conf >> device { >> bdaddr 00:00:00:00:00:00; >> name "Default entry"; >> key nokey; >> pin nopin; >> } >> >> device { >> bdaddr 00:17:b0:53:55:29; >> name "Tilifon"; >> key nokey; >> pin "nopin"; >> } > >you need to specify pin code, for example > >pin "1234"; > >> so I run the hcsecd daemon >> >> and I try: >> # obexapp -c -a 00:17:b0:53:55:29 -C 1 >> >> my phone tells me that some device want to pair with it >> I chose accept >> and the phone is prompting me for passcode... >> I enter something and it sasy "pairing failed" > >when phone prompts, you need to enter the same pin code you have put >into /etc/bluetooth/hcsecd.conf, i.e. for example above you need to >enter 1234 on the phone. > >thanks, >max > Thank you very much it has connected but now there is another problem so...when the phone prompt me for the passcode and I enter it it says that is connected, but the obex returns this: # obexapp -c -a 00:17:b0:53:55:29 -C 1 Could not connect to the remote OBEX server. Response: Unknown response (0). Service: None and in a few seconds the fone tells that is disconnected what does this mean ? how can I browse the files in my phone ? sdpcontrol returns this: # sdpcontrol -a 00:17:b0:53:55:29 browse Record Handle: 0x00010087 Service Class ID List: Dial-Up Networking (0x1103) Generic Networking (0x1201) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 1 Bluetooth Profile Descriptor List: Dial-Up Networking (0x1103) ver. 1.0 Record Handle: 0x00010088 Service Class ID List: Serial Port (0x1101) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 15 Record Handle: 0x00010089 Service Class ID List: Serial Port (0x1101) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 3 Record Handle: 0x0001008a Service Class ID List: Handsfree Audio Gateway (0x111f) Generic Audio (0x1203) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 13 Bluetooth Profile Descriptor List: Handsfree (0x111e) ver. 1.1 Record Handle: 0x0001008b Service Class ID List: Headset Audio Gateway (0x1112) Generic Audio (0x1203) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 12 Bluetooth Profile Descriptor List: Headset (0x1108) ver. 1.0 Record Handle: 0x00010090 Service Class ID List: SIM Access (0x112d) Generic Telephony (0x1204) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 4 Bluetooth Profile Descriptor List: SIM Access (0x112d) ver. 1.0 Record Handle: 0x00010092 Service Class ID List: OBEX Object Push (0x1105) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 9 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX Object Push (0x1105) ver. 1.0 Record Handle: 0x00010093 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 Record Handle: 0x00010095 Service Class ID List: 0x00000002-0000-1000-8000-0002ee000002 Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 11 OBEX (0x0008) ----------------------------------------------------------------- http://ide.li/ - портал за българите по света. Статии, новини, форуми, снимки, информация. From owner-freebsd-bluetooth@FreeBSD.ORG Tue Aug 22 21:00:59 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 AFC0616A4DA for ; Tue, 22 Aug 2006 21:00:59 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1555243D46 for ; Tue, 22 Aug 2006 21:00:59 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 211AA3BE57; Tue, 22 Aug 2006 16:00:58 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 30566-02-73; Tue, 22 Aug 2006 16:00:58 -0500 (CDT) Received: from [10.12.163.251] (unknown [10.12.163.251]) by mailgate1b.savvis.net (Postfix) with ESMTP id B22993BE3C; Tue, 22 Aug 2006 16:00:57 -0500 (CDT) Message-ID: <44EB7086.6070309@savvis.net> Date: Tue, 22 Aug 2006 14:00:54 -0700 From: Maksim Yevmenkin User-Agent: Thunderbird 1.5.0.2 (X11/20060603) MIME-Version: 1.0 To: Mario Pavlov References: <1098400120.449091156279905606.JavaMail.nobody@mail02.abv.bg> In-Reply-To: <1098400120.449091156279905606.JavaMail.nobody@mail02.abv.bg> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at savvis.net Cc: freebsd-bluetooth@freebsd.org Subject: Re: pairing PC and 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: Tue, 22 Aug 2006 21:00:59 -0000 Mario, [...] > Thank you very much > it has connected > but now there is another problem > so...when the phone prompt me for the passcode and I enter it > it says that is connected, but the obex returns this: > > # obexapp -c -a 00:17:b0:53:55:29 -C 1 > Could not connect to the remote OBEX server. Response: Unknown response (0). Service: None > > and in a few seconds the fone tells that is disconnected > what does this mean ? > how can I browse the files in my phone ? [...] > sdpcontrol returns this: > # sdpcontrol -a 00:17:b0:53:55:29 browse [...] > Record Handle: 0x00010092 > Service Class ID List: > OBEX Object Push (0x1105) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 9 > OBEX (0x0008) > Bluetooth Profile Descriptor List: > OBEX Object Push (0x1105) ver. 1.0 > > Record Handle: 0x00010093 > 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 according to the sdp, obex services are on rfcomm channels 9 (push) and 10 (file transfer). you have specifically told obexapp(1) to connect to rfcomm channel 1 (-C 1 option) where no obex service is listening. just let obexapp(1) figure out rfcomm channel number automatically, i.e. % obexapp -c -a 00:17:b0:53:55:29 -C opush (to use obex push service) or % obexapp -c -a 00:17:b0:53:55:29 -f -C ftrn (to use obex file transfer service) thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Aug 23 05:30:43 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 0F0C616A4E0 for ; Wed, 23 Aug 2006 05:30:43 +0000 (UTC) (envelope-from vlado@botka.homeunix.org) Received: from smtp-out4.iol.cz (smtp-out4.iol.cz [194.228.2.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BA6143D45 for ; Wed, 23 Aug 2006 05:30:42 +0000 (GMT) (envelope-from vlado@botka.homeunix.org) Received: from antivir4.iol.cz (avir4 [192.168.30.209]) by smtp-out4.iol.cz (Postfix) with ESMTP id 39FA81F9451; Wed, 23 Aug 2006 07:30:41 +0200 (CEST) Received: from localhost (antivir4.iol.cz [127.0.0.1]) by antivir4.iol.cz (Postfix) with ESMTP id 2A83624003A; Wed, 23 Aug 2006 07:30:41 +0200 (CEST) Received: from smtp-out4.iol.cz (smtp-out-4.iplanet.iol.cz [192.168.30.31]) by antivir4.iol.cz (Postfix) with ESMTP id 0751024003B; Wed, 23 Aug 2006 07:30:41 +0200 (CEST) Received: from ace.botka.homeunix.org (3.77.broadband2.iol.cz [83.208.77.3]) by smtp-out4.iol.cz (Postfix) with ESMTP id 95ABD22AEFA; Wed, 23 Aug 2006 07:30:30 +0200 (CEST) Received: by ace.botka.homeunix.org (Postfix, from userid 1001) id 52D43BA; Wed, 23 Aug 2006 07:30:30 +0200 (CEST) X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on ace.botka.homeunix.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0 Received: from srv (ac.botka.homeunix.org [192.168.1.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ace.botka.homeunix.org (Postfix) with ESMTP id CF37683; Wed, 23 Aug 2006 07:30:25 +0200 (CEST) Date: Wed, 23 Aug 2006 07:30:25 +0200 (CEST) From: Vladimir Botka X-X-Sender: vlado@srv.g1.netng.org To: Mario Pavlov In-Reply-To: <208735345.378631156254300487.JavaMail.nobody@mail04.abv.bg> Message-ID: <20060823072503.T54403@srv.g1.netng.org> References: <208735345.378631156254300487.JavaMail.nobody@mail04.abv.bg> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: amavisd-new at iol.cz Cc: freebsd-bluetooth@freebsd.org Subject: Re: pairing PC and 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: Wed, 23 Aug 2006 05:30:43 -0000 Hello, put some "passcode" into the pin option (now you have "nopin") in the /etc/bluetooth/hcsecd.conf . Then use it in pairing process. It is a good idea to setup an obex server. Here are some notes: http://wiki.botka.homeunix.org/bin/view/Main/BlueTooth HTH. Cheers, -vlado On Tue, 22 Aug 2006, Mario Pavlov wrote: > Hello guys > I'm tring to get my FreeBSD-6.1-STABLE to transfer files with my NOKIA 6021 phone > > here is what I do: > > # kldload ng_ubt > > # /etc/rc.bluetooth start ubt0 > BD_ADDR: 11:11:11:11:11:11 > Features: 0xbf 0xfe 0x8d 0x78 0x8 0x18 00 00 > <3-Slot> <5-Slot> > > > > > Max. ACL packet size: 678 bytes > Number of ACL packets: 8 > Max. SCO packet size: 48 bytes > Number of SCO packets: 10 > > # hccontrol -n ubt0hci inquiry > Inquiry result, num_responses=1 > Inquiry result #0 > BD_ADDR: 00:17:b0:53:55:29 > Page Scan Rep. Mode: 0x2 > Page Scan Period Mode: 0x2 > Page Scan Mode: 00 > Class: 52:02:04 > Clock offset: 0x458 > Inquiry complete. Status: No error [00] > > # hccontrol -n ubt0hci remote_name_request 00:17:b0:53:55:29 0 0 0 > BD_ADDR: 00:17:b0:53:55:29 > Name: Tilifon > > everything looks fine > this is my config > > # cat /etc/bluetooth/hcsecd.conf > device { > bdaddr 00:00:00:00:00:00; > name "Default entry"; > key nokey; > pin nopin; > } > > device { > bdaddr 00:17:b0:53:55:29; > name "Tilifon"; > key nokey; > pin "nopin"; > } > > so I run the hcsecd daemon > > and I try: > # obexapp -c -a 00:17:b0:53:55:29 -C 1 > > my phone tells me that some device want to pair with it > I chose accept > and the phone is prompting me for passcode... > I enter something and it sasy "pairing failed" > and the obexapp exits > how to deal with this passcode ? > how to tell the obexapp to use some passcode ? > > I've also tried this: > # hccontrol -n ubt0hci write_authentication_enable 1 > # sdpcontrol -a 00:17:b0:53:55:29 browse > and it prompts me for passcode again > and the result is the same: "pairing failed" > > than I've tried this: > # hccontrol -n ubt0hci write_authentication_enable 0 > # sdpcontrol -a 00:17:b0:53:55:29 browse > > Record Handle: 0x00010078 > Service Class ID List: > Dial-Up Networking (0x1103) > Generic Networking (0x1201) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 1 > Bluetooth Profile Descriptor List: > Dial-Up Networking (0x1103) ver. 1.0 > > Record Handle: 0x00010079 > Service Class ID List: > Serial Port (0x1101) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 15 > > Record Handle: 0x0001007a > Service Class ID List: > Serial Port (0x1101) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 3 > > Record Handle: 0x0001007b > Service Class ID List: > Handsfree Audio Gateway (0x111f) > Generic Audio (0x1203) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 13 > Bluetooth Profile Descriptor List: > Handsfree (0x111e) ver. 1.1 > > Record Handle: 0x0001007c > Service Class ID List: > Headset Audio Gateway (0x1112) > Generic Audio (0x1203) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 12 > Bluetooth Profile Descriptor List: > Headset (0x1108) ver. 1.0 > > Record Handle: 0x00010081 > Service Class ID List: > SIM Access (0x112d) > Generic Telephony (0x1204) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 4 > Bluetooth Profile Descriptor List: > SIM Access (0x112d) ver. 1.0 > > Record Handle: 0x00010083 > Service Class ID List: > OBEX Object Push (0x1105) > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 9 > OBEX (0x0008) > Bluetooth Profile Descriptor List: > OBEX Object Push (0x1105) ver. 1.0 > > Record Handle: 0x00010084 > 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 > > Record Handle: 0x00010086 > Service Class ID List: > 0x00000002-0000-1000-8000-0002ee000002 > Protocol Descriptor List: > L2CAP (0x0100) > RFCOMM (0x0003) > Protocol specific parameter #1: u/int8/bool 11 > OBEX (0x0008) > > and again with obex, but still the same... > > can I anyone help me please > thank you :) > > > > ----------------------------------------------------------------- > http://ide.li/ - ?????? ?? ????????? ?? ?????. ??????, ??????, ??????, ??????, ??????????. > _______________________________________________ > freebsd-bluetooth@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth > To unsubscribe, send any mail to "freebsd-bluetooth-unsubscribe@freebsd.org" > > From owner-freebsd-bluetooth@FreeBSD.ORG Wed Aug 23 12:44:28 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 846BC16A4E0 for ; Wed, 23 Aug 2006 12:44:28 +0000 (UTC) (envelope-from bel@orel.ru) Received: from mail.orel.ru (relay.orel.ru [213.59.64.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id CADF643DC5 for ; Wed, 23 Aug 2006 12:44:11 +0000 (GMT) (envelope-from bel@orel.ru) Received: from [192.168.99.99] (pf1.net.orel.ru [213.59.64.75]) by mail.orel.ru (8.13.4/8.13.4) with ESMTP id k7NCi3cc002322 for ; Wed, 23 Aug 2006 16:44:06 +0400 (MSD) (envelope-from bel@orel.ru) Message-ID: <44EC4D93.6000603@orel.ru> Date: Wed, 23 Aug 2006 16:44:03 +0400 From: Andrew Belashov Organization: ORIS User-Agent: Thunderbird 1.5 (X11/20060123) MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: Dr.Web (R) for Mail Servers on mail.orel.ru host X-Antivirus-Code: 100000 X-Zombi-Check: on netra2.orel.ru Subject: The bluetooth stack does not work on FreeBSD/sparc64 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, 23 Aug 2006 12:44:28 -0000 Hello, All! The help in debugging netgraph bluetooth stack is necessary to me. I have a working example on i386, but on sparc64 same example does not work. On sparc64(SMP) I have following debug information: $ uname -a FreeBSD bel.localdomain 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #11: Tue Apr 25 14:08:31 MSD 2006 bel@bel.localdomain:/usr/obj/usr/src/sys/SUNC3D sparc64 $ obexapp -c -a POCKET_PC -C FTRN -f OBEX_TransportConnect(): obex_transport_connect_request(): Custom connect [pause at ~60 seconds] obex_transport_connect_request(): ret=-1 obex_transport_disconnect_request(): Custom disconnect obex_transport_disconnect_server(): Custom disconnect obexapp_transport_connect(): Could not connect socket. Operation timed out (60) obexapp_client(): OBEX_TransportConnect failed # l2control -a bel Read_Channel_List L2CAP channels: Remote BD_ADDR SCID/ DCID PSM IMTU/ OMTU State POCKET_PC 65/ 65 3 0/ 1691 OPEN # hcidump -r /tmp/obexftrn.hcidump HCIDump - HCI packet analyzer ver 1.5 < HCI Command: Create Connection(0x01|0x0005) plen 13 > HCI Event: Command Status(0x0f) plen 4 > HCI Event: Connect Complete(0x03) plen 11 < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 < ACL data: handle 0x0001 flags 0x02 dlen 12 L2CAP(s): Connect req: psm 1 scid 0x0040 > HCI Event: Max Slots Change(0x1b) plen 3 > HCI Event: Command Complete(0x0e) plen 6 > HCI Event: Number of Completed Packets(0x13) plen 5 > ACL data: handle 0x0001 flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0 < ACL data: handle 0x0001 flags 0x02 dlen 12 L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0 > HCI Event: Number of Completed Packets(0x13) plen 5 > ACL data: handle 0x0001 flags 0x02 dlen 20 L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 8 MTU 512 FlushTO 65535 < ACL data: handle 0x0001 flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0 > ACL data: handle 0x0001 flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0 < ACL data: handle 0x0001 flags 0x02 dlen 24 L2CAP(d): cid 0x40 len 20 [psm 1] SDP SSA Req: tid 0x0 len 0xf pat uuid-16 0x1106 (OBEXObjTrnsf) max 0xffff aid(s) 0x0004 (ProtocolDescList) cont 00 > HCI Event: Number of Completed Packets(0x13) plen 5 > HCI Event: Number of Completed Packets(0x13) plen 5 > ACL data: handle 0x0001 flags 0x02 dlen 39 L2CAP(d): cid 0x40 len 35 [psm 1] SDP SSA Rsp: tid 0x0 len 0x1e cnt 0x1b srv rec #0 aid 0x0004 (ProtocolDescList) < < uuid-16 0x0100 (L2CAP) > < uuid-16 0x0003 (RFCOMM) uint 0x3 > < uuid-16 0x0008 (OBEX) > > cont 00 < ACL data: handle 0x0001 flags 0x02 dlen 12 L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040 < ACL data: handle 0x0001 flags 0x02 dlen 12 L2CAP(s): Connect req: psm 3 scid 0x0041 > HCI Event: Number of Completed Packets(0x13) plen 5 > HCI Event: Number of Completed Packets(0x13) plen 5 > ACL data: handle 0x0001 flags 0x02 dlen 12 L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040 > ACL data: handle 0x0001 flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0041 result 0 status 0 < ACL data: handle 0x0001 flags 0x02 dlen 16 L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 4 MTU 0 [hmmm, MTU=0! Why?] > ACL data: handle 0x0001 flags 0x02 dlen 16 L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 4 MTU 1691 < ACL data: handle 0x0001 flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 0 > HCI Event: Number of Completed Packets(0x13) plen 5 > HCI Event: Number of Completed Packets(0x13) plen 5 > ACL data: handle 0x0001 flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 0 < ACL data: handle 0x0001 flags 0x02 dlen 8 L2CAP(d): cid 0x41 len 4 [psm 3] RFCOMM(s): SABM: cr 1 dlci 0 pf 1 ilen 0 fcs 0x1c > HCI Event: Number of Completed Packets(0x13) plen 5 [pause at ~60 seconds] < ACL data: handle 0x0001 flags 0x02 dlen 12 L2CAP(s): Disconn req: dcid 0x0041 scid 0x0041 > HCI Event: Number of Completed Packets(0x13) plen 5 > ACL data: handle 0x0001 flags 0x02 dlen 12 L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0041 > HCI Event: Disconn Complete(0x05) plen 4 Messages from modified (for debugging) kernel: ng_btsocket_rfcomm_session_create: sosetopt: mtu=672 ng_btsocket_l2cap_ctloutput: SOPT_SET: SO_L2CAP_IMTU: pcb->imtu=0 Why MTU is 0? Any ideas are welcomed. -- With Best Regards, Andrew Belashov. From owner-freebsd-bluetooth@FreeBSD.ORG Wed Aug 23 17:20:24 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 CBE6E16A4DE for ; Wed, 23 Aug 2006 17:20:24 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7749F43D5A for ; Wed, 23 Aug 2006 17:20:24 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 9A4763BE7A; Wed, 23 Aug 2006 12:20:23 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 16712-02-32; Wed, 23 Aug 2006 12:20:23 -0500 (CDT) Received: from [10.12.163.251] (unknown [10.12.163.251]) by mailgate1b.savvis.net (Postfix) with ESMTP id 1D7AC3BE61; Wed, 23 Aug 2006 12:20:23 -0500 (CDT) Message-ID: <44EC8E56.4010008@savvis.net> Date: Wed, 23 Aug 2006 10:20:22 -0700 From: Maksim Yevmenkin User-Agent: Thunderbird 1.5.0.2 (X11/20060603) MIME-Version: 1.0 To: Vladimir Botka References: <208735345.378631156254300487.JavaMail.nobody@mail04.abv.bg> <20060823072503.T54403@srv.g1.netng.org> In-Reply-To: <20060823072503.T54403@srv.g1.netng.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at savvis.net Cc: freebsd-bluetooth@freebsd.org Subject: Re: pairing PC and 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: Wed, 23 Aug 2006 17:20:24 -0000 Vladimir, > put some "passcode" into the pin option (now you have "nopin") in the > /etc/bluetooth/hcsecd.conf . Then use it in pairing process. > > It is a good idea to setup an obex server. Here are some notes: > http://wiki.botka.homeunix.org/bin/view/Main/BlueTooth please take no offense, but this kind of notes are not very helpful. this is what i call "linux howto-style" documentation. all it (usually) does is provides list of some commands to execute without giving any background information. it may work for some users, however, when someone's environment is not exactly the same it does not work and leaves no clue to what might be going wrong and how to fix it. personally, i've seen quite a few wiki's/howto's/etc. related to freebsd and bluetooth, however none of them gives all the information. so, it would be very nice if someone wrote a document describing bluetooth basics, i.e. - concept of baseband (physical/radio) link - concept of logical links, i.e. l2cap and rfcomm - concept of l2cap psm and rfcomm channel - what is pairing, how it works exactly and why one needs it - concept of bluetooth services/profiles - concept of bluetooth service discovery thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Aug 23 17:34:39 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 66F1C16A4DE for ; Wed, 23 Aug 2006 17:34:39 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB9BF43D4C for ; Wed, 23 Aug 2006 17:34:38 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id 6835F3BE8D; Wed, 23 Aug 2006 12:34:38 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 16193-02-20; Wed, 23 Aug 2006 12:34:38 -0500 (CDT) Received: from [10.12.163.251] (unknown [10.12.163.251]) by mailgate1b.savvis.net (Postfix) with ESMTP id 0A1653BE89; Wed, 23 Aug 2006 12:34:37 -0500 (CDT) Message-ID: <44EC91AD.1090405@savvis.net> Date: Wed, 23 Aug 2006 10:34:37 -0700 From: Maksim Yevmenkin User-Agent: Thunderbird 1.5.0.2 (X11/20060603) MIME-Version: 1.0 To: Andrew Belashov References: <44EC4D93.6000603@orel.ru> In-Reply-To: <44EC4D93.6000603@orel.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at savvis.net Cc: freebsd-bluetooth@freebsd.org Subject: Re: The bluetooth stack does not work on FreeBSD/sparc64 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, 23 Aug 2006 17:34:39 -0000 Andrew, > # l2control -a bel Read_Channel_List > L2CAP channels: > Remote BD_ADDR SCID/ DCID PSM IMTU/ OMTU State > POCKET_PC 65/ 65 3 0/ 1691 OPEN [...] > < ACL data: handle 0x0001 flags 0x02 dlen 16 > L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 4 > MTU 0 > [hmmm, MTU=0! Why?] i think there is a bug in ng_btsocket_rfcomm.c. could you please try to change ng_btsocket_rfcomm_session_create() function and define local mtu valiable as u_int16_t instead of int, i.e. change static int ng_btsocket_rfcomm_session_create(ng_btsocket_rfcomm_session_p *sp, struct socket *l2so, bdaddr_p src, bdaddr_p dst, struct thread *td) { ng_btsocket_rfcomm_session_p s = NULL; struct sockaddr_l2cap l2sa; struct sockopt l2sopt; int mtu, error; to static int ng_btsocket_rfcomm_session_create(ng_btsocket_rfcomm_session_p *sp, struct socket *l2so, bdaddr_p src, bdaddr_p dst, struct thread *td) { ng_btsocket_rfcomm_session_p s = NULL; struct sockaddr_l2cap l2sa; struct sockopt l2sopt; int error; u_int16_t mtu; thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Aug 24 05:33:44 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 CCA1516A4DA for ; Thu, 24 Aug 2006 05:33:44 +0000 (UTC) (envelope-from bel@orel.ru) Received: from mail.orel.ru (relay.orel.ru [213.59.64.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id 28F3F43D49 for ; Thu, 24 Aug 2006 05:33:43 +0000 (GMT) (envelope-from bel@orel.ru) Received: from [192.168.99.99] (pf1.net.orel.ru [213.59.64.75]) by mail.orel.ru (8.13.4/8.13.4) with ESMTP id k7O5XcA0058161; Thu, 24 Aug 2006 09:33:40 +0400 (MSD) (envelope-from bel@orel.ru) Message-ID: <44ED3A32.6080105@orel.ru> Date: Thu, 24 Aug 2006 09:33:38 +0400 From: Andrew Belashov Organization: ORIS User-Agent: Thunderbird 1.5 (X11/20060123) MIME-Version: 1.0 To: Maksim Yevmenkin References: <44EC4D93.6000603@orel.ru> <44EC91AD.1090405@savvis.net> In-Reply-To: <44EC91AD.1090405@savvis.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: Dr.Web (R) for Mail Servers on mail.orel.ru host X-Antivirus-Code: 100000 X-Zombi-Check: on netra2.orel.ru Cc: freebsd-bluetooth@freebsd.org Subject: Re: The bluetooth stack does not work on FreeBSD/sparc64 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, 24 Aug 2006 05:33:44 -0000 Maksim Yevmenkin wrote: > Andrew, > >> # l2control -a bel Read_Channel_List >> L2CAP channels: >> Remote BD_ADDR SCID/ DCID PSM IMTU/ OMTU State >> POCKET_PC 65/ 65 3 0/ 1691 OPEN > > [...] > >> < ACL data: handle 0x0001 flags 0x02 dlen 16 >> L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 4 >> MTU 0 >> [hmmm, MTU=0! Why?] > > i think there is a bug in ng_btsocket_rfcomm.c. could you please try to > change ng_btsocket_rfcomm_session_create() function and define local mtu > valiable as u_int16_t instead of int, i.e. > > change > > static int > ng_btsocket_rfcomm_session_create(ng_btsocket_rfcomm_session_p *sp, > struct socket *l2so, bdaddr_p src, bdaddr_p dst, > struct thread *td) > { > ng_btsocket_rfcomm_session_p s = NULL; > struct sockaddr_l2cap l2sa; > struct sockopt l2sopt; > int mtu, error; > > to > > static int > ng_btsocket_rfcomm_session_create(ng_btsocket_rfcomm_session_p *sp, > struct socket *l2so, bdaddr_p src, bdaddr_p dst, > struct thread *td) > { > ng_btsocket_rfcomm_session_p s = NULL; > struct sockaddr_l2cap l2sa; > struct sockopt l2sopt; > int error; > u_int16_t mtu; > > thanks, > max > Yes, this patch solves a problem. Many thanks! I should issue the PR? -- With Best Regards, Andrew Belashov. From owner-freebsd-bluetooth@FreeBSD.ORG Thu Aug 24 16:53:07 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 C16DD16A4DD for ; Thu, 24 Aug 2006 16:53:07 +0000 (UTC) (envelope-from maksim.yevmenkin@savvis.net) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DA8243D45 for ; Thu, 24 Aug 2006 16:53:07 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from localhost (localhost.localdomain [127.0.0.1]) by mailgate1b.savvis.net (Postfix) with ESMTP id A7AAB3BF2A; Thu, 24 Aug 2006 11:53:06 -0500 (CDT) Received: from mailgate1b.savvis.net ([127.0.0.1]) by localhost (mailgate1b.savvis.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 21371-01-56; Thu, 24 Aug 2006 11:53:06 -0500 (CDT) Received: from [10.12.163.251] (unknown [10.12.163.251]) by mailgate1b.savvis.net (Postfix) with ESMTP id 45C973BE7D; Thu, 24 Aug 2006 11:53:06 -0500 (CDT) Message-ID: <44EDD971.8010504@savvis.net> Date: Thu, 24 Aug 2006 09:53:05 -0700 From: Maksim Yevmenkin User-Agent: Thunderbird 1.5.0.2 (X11/20060603) MIME-Version: 1.0 To: Andrew Belashov References: <44EC4D93.6000603@orel.ru> <44EC91AD.1090405@savvis.net> <44ED3A32.6080105@orel.ru> In-Reply-To: <44ED3A32.6080105@orel.ru> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at savvis.net Cc: freebsd-bluetooth@freebsd.org Subject: Re: The bluetooth stack does not work on FreeBSD/sparc64 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, 24 Aug 2006 16:53:07 -0000 Andrew, [...] > Yes, this patch solves a problem. Many thanks! thanks for the report and testing. i have committed fix to -current and will mfc it in 3 days. > I should issue the PR? probably not, but if you decide to issue a pr, please assign it to me (emax). thanks, max