From owner-freebsd-bluetooth@FreeBSD.ORG Mon Apr 4 17:00:36 2005 Return-Path: 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 7D01D16A4CE for ; Mon, 4 Apr 2005 17:00:36 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id E616A43D2F for ; Mon, 4 Apr 2005 17:00:35 +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 072B53BE61; Mon, 4 Apr 2005 12:00:35 -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 03436-01-16; Mon, 4 Apr 2005 12:00:34 -0500 (CDT) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44]) by mailgate1b.savvis.net (Postfix) with ESMTP id CEEE53BE24; Mon, 4 Apr 2005 12:00:34 -0500 (CDT) Received: from s228130hz1ew031.apptix-01.savvis.net ([10.146.4.28]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 4 Apr 2005 12:00:14 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew031.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 4 Apr 2005 11:59:59 -0500 Message-ID: <4251728D.3060302@savvis.net> Date: Mon, 04 Apr 2005 09:59:57 -0700 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Denis Fokin References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Apr 2005 16:59:59.0411 (UTC) FILETIME=[BC3E4830:01C53937] X-Virus-Scanned: amavisd-new at savvis.net cc: freebsd-bluetooth@freebsd.org Subject: Re: Problems with Bluetooth LAN access X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2005 17:00:36 -0000 [moving to bluetooth@] Denis, > I meet a problem, while trying to access my LAN from iPaq 2210 through > FreeBSD 5.3 box via Bluetooth. I have an Tekram-branded USB-BT dongle. > This dongle is successfully recognized in OS and works: > ------------------------------------------------------------------ > sanvean% /etc/rc.bluetooth start ubt0 looks fine to me > I can see my iPaq from FreeBSD good > And even ping it... good > And more, I can see all services, that iPaq provides. > > sanvean% sdptool browse 00:04:3e:80:45:d1 why are you using sdptool? there is nothing wrong with it, but FreeBSD 5.3 has its own sdp server (sdpd(8)) and client (sdpcontrol(8)). > Fine, let's bring up the service: > > sanvean% sdptool add --channel 7 LAN again why sdptool? in 5.3 rfcommm_pppd(8) should register LAN service automatically with local sdpd(8). > Here is my pppd.conf file: > > sanvean% cvery at /etc/ppp/ppp.conf > > default: > set log Phase Chat LCP IPCP CCP tun command > rfcomm-server: > set cd off > set dial > set speed 115200 > set timeout 0 > nat enable yes > set ifaddr 192.168.1.2/0 192.168.1.3/0 > enable dns > open > disable pap > deny pap > disable chap > deny chap looks fine to me. i do not think you need "open" > Now, going to iPaq.... Well, I can see my FreeBSD box, i have discovered > "LAN Access Using PPP" service and I am ready to use it. Let's go! > Password? Forged about it, clear the fields and tap Ok. > "Answering modem has disconnected", Ok! I have typed my FreeBSD login/password - > Still no luck. Have killed 6 hours investigating this - still no luck. just by looking at hcidump i can see that remote side has terminated the connection. i do not think this is the bluetooth related issue. most likely this is ppp related issue. ah, i see you already figured it out. i was just about to suggest you to check for ras :) btw, if you had used "hcidump -X" or "hcidump -A" you would have noticed that right away :) also how did you manage to start rfcomm_pppd(8)? it should exit if it cant register service with local sdpd(8). i do not see you mentioned sdpd(8) anywhere. > Have tried another services: OBEX, Serial - no luck :( > My devices can connect to each other, but cannot communicate. so, is everything works now? max From owner-freebsd-bluetooth@FreeBSD.ORG Mon Apr 4 21:14:12 2005 Return-Path: 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 8E30316A4CE for ; Mon, 4 Apr 2005 21:14:12 +0000 (GMT) Received: from f15.mail.ru (f15.mail.ru [194.67.57.45]) by mx1.FreeBSD.org (Postfix) with ESMTP id E44B043D3F for ; Mon, 4 Apr 2005 21:14:11 +0000 (GMT) (envelope-from sanvean@mail.ru) Received: from mail by f15.mail.ru with local id 1DIYte-000HfX-00 for freebsd-bluetooth@freebsd.org; Tue, 05 Apr 2005 01:14:10 +0400 Received: from [212.1.248.243] by win.mail.ru with HTTP; Tue, 05 Apr 2005 01:14:10 +0400 From: Denis Fokin To: freebsd-bluetooth@freebsd.org Mime-Version: 1.0 X-Mailer: mPOP Web-Mail 2.19 X-Originating-IP: [212.1.248.243] Date: Tue, 05 Apr 2005 01:14:10 +0400 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit Message-Id: Subject: Re: Problems with Bluetooth LAN access X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Denis Fokin List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2005 21:14:12 -0000 Hello, Maksim! First of all thank yoy for your kindness. > why are you using sdptool? there is nothing wrong with it, but FreeBSD > 5.3 has its own sdp server (sdpd(8)) and client (sdpcontrol(8)). I have read a very old manual, nothing was stated there about sdpcontrol. Right from now I will know about this tool :) > > Fine, let's bring up the service: > > > > sanvean% sdptool add --channel 7 LAN > > again why sdptool? in 5.3 rfcommm_pppd(8) should register LAN service > automatically with local sdpd(8). Fully agree! I have figured it out in experimental way, while writting my own script to enable bluetooth service at startup :) > > btw, if you had used "hcidump -X" or "hcidump -A" you would have noticed > that right away :) Again, thank you for a nice hint. > also how did you manage to start rfcomm_pppd(8)? it should exit if it > cant register service with local sdpd(8). i do not see you mentioned > sdpd(8) anywhere. Sorry, I have forget to tell, that both sdpd and hcisecd are started without problems. > > Have tried another services: OBEX, Serial - no luck :( > > My devices can connect to each other, but cannot communicate. > > so, is everything works now? semi-works... OPUSH sessions work. I can do "getdefault" and put my own contacts But FTRN does not work completely. Here is my log: sanvean% sdpcontrol -a 00:04:3e:80:45:d1 browse Record Handle: 0x00010000 Service Class ID List: Serial Port (0x1101) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 1 Bluetooth Profile Descriptor List: Serial Port (0x1101) ver. 1.0 Record Handle: 0x00010001 Service Class ID List: OBEX Object Push (0x1105) Protocol Descriptor List: L2CAP (0x0100) RFCOMM (0x0003) Protocol specific parameter #1: u/int8/bool 2 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX Object Push (0x1105) ver. 1.0 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 3 OBEX (0x0008) Bluetooth Profile Descriptor List: OBEX File Transfer (0x1106) ver. 1.0 Record Handle: 0x00010003 Service Class ID List: GN (0x1117) Protocol Descriptor List: L2CAP (0x0100) Protocol specific parameter #1: u/int/uuid16 15 BNEP (0x000f) Protocol specific parameter #1: u/int/uuid16 256 Protocol specific parameter #2: 0x09 0x08 00 0x09 0x08 0x06 Bluetooth Profile Descriptor List: GN (0x1117) ver. 1.0 Record Handle: 0x00010004 Service Class ID List: PANU (0x1115) Protocol Descriptor List: L2CAP (0x0100) Protocol specific parameter #1: u/int/uuid16 15 BNEP (0x000f) Protocol specific parameter #1: u/int/uuid16 256 Protocol specific parameter #2: 0x09 0x08 00 0x09 0x08 0x06 Bluetooth Profile Descriptor List: PANU (0x1115) ver. 1.0 sanvean% obexapp -c -a 00:04:3e:80:45:d1 -C OPUSH obex> getdefault getdefault: local file> defcard.txt Success, response: OK, Success (0x20) obex> put put: local file> defcard.txt put: remote file> defcard.txt Success, response: OK, Success (0x20) obex> di Success, response: OK, Success (0x20) sanvean% obexapp -c -a 00:04:3e:80:45:d1 -C FTRN Could not connect to the remote OBEX server. Response: Unknown response (0x53). Service: None --------------------------------DUMP OF UNSUCCESSFULL FTRN SESSION--------------------------------------- HCIDump - HCI packet analyzer ver 1.5 device: any snap_len: 65535 filter: 0xffffffff < HCI Command: Create Connection(0x01|0x0005) plen 13 D1 45 80 3E 04 00 18 CC 00 00 00 00 01 > HCI Event: Command Status(0x0f) plen 4 00 01 05 04 > HCI Event: Connect Complete(0x03) plen 11 00 04 00 D1 45 80 3E 04 00 01 00 < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4 04 00 0F 00 < ACL data: handle 0x0004 flags 0x02 dlen 12 L2CAP(s): Connect req: psm 1 scid 0x0089 > HCI Event: Command Complete(0x0e) plen 6 01 0D 08 00 04 00 > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > HCI Event: Max Slots Change(0x1b) plen 3 04 00 05 > ACL data: handle 0x0004 flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0089 result 0 status 0 < ACL data: handle 0x0004 flags 0x02 dlen 12 L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0 > ACL data: handle 0x0004 flags 0x02 dlen 20 L2CAP(s): Config req: dcid 0x0089 flags 0x0000 clen 8 MTU 512 FlushTO 65535 < ACL data: handle 0x0004 flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0 > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > ACL data: handle 0x0004 flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x0089 flags 0x0000 result 0 clen 0 < ACL data: handle 0x0004 flags 0x02 dlen 26 L2CAP(d): cid 0x40 len 22 [psm 1] SDP SSA Req: tid 0x0 len 0x11 pat uuid-16 0x1106 (OBEXObjTrnsf) max 0xffff aid(s) 0x0004 - 0x0004 cont 00 > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > ACL data: handle 0x0004 flags 0x02 dlen 39 L2CAP(d): cid 0x89 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 0x0004 flags 0x02 dlen 12 L2CAP(s): Disconn req: dcid 0x0040 scid 0x0089 < ACL data: handle 0x0004 flags 0x02 dlen 12 L2CAP(s): Connect req: psm 3 scid 0x008a > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > ACL data: handle 0x0004 flags 0x02 dlen 12 L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0089 > ACL data: handle 0x0004 flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x0041 scid 0x008a result 0 status 0 < ACL data: handle 0x0004 flags 0x02 dlen 16 L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 4 MTU 132 > ACL data: handle 0x0004 flags 0x02 dlen 16 L2CAP(s): Config req: dcid 0x008a flags 0x0000 clen 4 MTU 1691 < ACL data: handle 0x0004 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 01 04 00 01 00 > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > ACL data: handle 0x0004 flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x008a flags 0x0000 result 0 clen 0 < ACL data: handle 0x0004 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 01 04 00 01 00 > ACL data: handle 0x0004 flags 0x02 dlen 8 L2CAP(d): cid 0x8a len 4 [psm 3] RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7 < ACL data: handle 0x0004 flags 0x02 dlen 18 L2CAP(d): cid 0x41 len 14 [psm 3] RFCOMM(s): PN CMD: cr 1 dlci 0 pf 0 ilen 10 fcs 0x70 mcc_len 8 dlci 6 frame_type 0 credit_flow 15 pri 7 ack_timer 0 frame_size 127 max_retrans 0 credits 7 > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > ACL data: handle 0x0004 flags 0x02 dlen 18 L2CAP(d): cid 0x8a len 14 [psm 3] RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 dlci 6 frame_type 0 credit_flow 14 pri 0 ack_timer 0 frame_size 127 max_retrans 0 credits 7 < ACL data: handle 0x0004 flags 0x02 dlen 8 L2CAP(d): cid 0x41 len 4 [psm 3] RFCOMM(s): SABM: cr 1 dlci 6 pf 1 ilen 0 fcs 0xd3 > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > ACL data: handle 0x0004 flags 0x02 dlen 8 L2CAP(d): cid 0x8a len 4 [psm 3] RFCOMM(s): UA: cr 1 dlci 6 pf 1 ilen 0 fcs 0x18 < ACL data: handle 0x0004 flags 0x02 dlen 12 L2CAP(d): cid 0x41 len 8 [psm 3] RFCOMM(s): MSC CMD: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2 dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0 < ACL data: handle 0x0004 flags 0x02 dlen 15 L2CAP(d): cid 0x41 len 11 [psm 3] RFCOMM(d): UIH: cr 1 dlci 6 pf 0 ilen 7 fcs 0x8f 80 00 07 11 00 04 00 > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > ACL data: handle 0x0004 flags 0x02 dlen 12 L2CAP(d): cid 0x8a len 8 [psm 3] RFCOMM(s): MSC RSP: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2 dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0 > ACL data: handle 0x0004 flags 0x02 dlen 12 L2CAP(d): cid 0x8a len 8 [psm 3] RFCOMM(s): MSC CMD: cr 0 dlci 0 pf 0 ilen 4 fcs 0xaa mcc_len 2 dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0 < ACL data: handle 0x0004 flags 0x02 dlen 12 L2CAP(d): cid 0x41 len 8 [psm 3] RFCOMM(s): MSC RSP: cr 1 dlci 0 pf 0 ilen 4 fcs 0x70 mcc_len 2 dlci 6 fc 0 rtc 1 rtr 1 ic 0 dv 1 b1 1 b2 1 b3 0 len 0 > ACL data: handle 0x0004 flags 0x02 dlen 9 L2CAP(d): cid 0x8a len 5 [psm 3] RFCOMM(d): UIH: cr 0 dlci 6 pf 1 ilen 0 fcs 0x49 credits 38 > ACL data: handle 0x0004 flags 0x02 dlen 15 L2CAP(d): cid 0x8a len 11 [psm 3] RFCOMM(d): UIH: cr 0 dlci 6 pf 0 ilen 7 fcs 0x55 D3 00 07 10 00 00 00 < ACL data: handle 0x0004 flags 0x02 dlen 9 L2CAP(d): cid 0x41 len 5 [psm 3] RFCOMM(d): UIH: cr 1 dlci 6 pf 1 ilen 0 fcs 0x93 credits 34 < ACL data: handle 0x0004 flags 0x02 dlen 8 L2CAP(d): cid 0x41 len 4 [psm 3] RFCOMM(s): DISC: cr 1 dlci 6 pf 1 ilen 0 fcs 0x32 > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > ACL data: handle 0x0004 flags 0x02 dlen 8 L2CAP(d): cid 0x8a len 4 [psm 3] RFCOMM(s): UA: cr 1 dlci 6 pf 1 ilen 0 fcs 0x18 < ACL data: handle 0x0004 flags 0x02 dlen 8 L2CAP(d): cid 0x41 len 4 [psm 3] RFCOMM(s): DISC: cr 1 dlci 0 pf 1 ilen 0 fcs 0xfd > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > ACL data: handle 0x0004 flags 0x02 dlen 8 L2CAP(d): cid 0x8a len 4 [psm 3] RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7 < ACL data: handle 0x0004 flags 0x02 dlen 12 L2CAP(s): Disconn req: dcid 0x0041 scid 0x008a > HCI Event: Number of Completed Packets(0x13) plen 5 01 04 00 01 00 > ACL data: handle 0x0004 flags 0x02 dlen 12 L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x008a > HCI Event: Disconn Complete(0x05) plen 4 00 04 00 13 --------------------------------DUMP OF UNSUCCESSFULL FTRN SESSION--------------------------------------- Also I have tried to connect to my Motorola v600 phone, but without success. I can successfully upload files to it using OPUSH, but cannot download files. For any my action (using OPUSH and FTRN) I receive Forbidden(0x43) response. Maybe the cause is Motorola's implementation of those protocols? Or some kind of security on the phone? In nearest future I will try to use my phone as GPRS modem. of OPUSH? Bye! Denis From owner-freebsd-bluetooth@FreeBSD.ORG Mon Apr 4 21:25:48 2005 Return-Path: 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 240E416A4CE for ; Mon, 4 Apr 2005 21:25:48 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0B9643D45 for ; Mon, 4 Apr 2005 21:25:47 +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 DF7393BE4E; Mon, 4 Apr 2005 16:25:46 -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 19426-01-73; Mon, 4 Apr 2005 16:25:46 -0500 (CDT) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44]) by mailgate1b.savvis.net (Postfix) with ESMTP id B0D963BE24; Mon, 4 Apr 2005 16:25:46 -0500 (CDT) Received: from s228130hz1ew031.apptix-01.savvis.net ([10.146.4.28]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 4 Apr 2005 16:25:32 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew031.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Mon, 4 Apr 2005 16:25:08 -0500 Message-ID: <4251B0B4.8050805@savvis.net> Date: Mon, 04 Apr 2005 14:25:08 -0700 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Denis Fokin References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 04 Apr 2005 21:25:08.0416 (UTC) FILETIME=[C6BFCC00:01C5395C] X-Virus-Scanned: amavisd-new at savvis.net cc: freebsd-bluetooth@freebsd.org Subject: Re: Problems with Bluetooth LAN access X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2005 21:25:48 -0000 Denis, [...] >>> Have tried another services: OBEX, Serial - no luck :( My devices >>> can connect to each other, but cannot communicate. >> >> so, is everything works now? > > semi-works... > > OPUSH sessions work. I can do "getdefault" and put my own contacts > But FTRN does not work completely. Here is my log: > > sanvean% sdpcontrol -a 00:04:3e:80:45:d1 browse > looks fine to me > sanvean% obexapp -c -a 00:04:3e:80:45:d1 -C OPUSH > obex> getdefault > getdefault: local file> defcard.txt > Success, response: OK, Success (0x20) > obex> put > put: local file> defcard.txt > put: remote file> defcard.txt > Success, response: OK, Success (0x20) > obex> di > Success, response: OK, Success (0x20) that is fine too > sanvean% obexapp -c -a 00:04:3e:80:45:d1 -C FTRN > Could not connect to the remote OBEX server. Response: Unknown response (0x53). Service: None did you try to add '-f' switch? from obexapp(1) man page -f Connect to Folder Browsing Service on the remote OBEX server (client mode only). By default client does not specify any ser- vice in OBEX connect request. > HCIDump - HCI packet analyzer ver 1.5 > device: any snap_len: 65535 filter: 0xffffffff [...] it would be better to produce a binary hcidump dump (-w option) and send it as attachment. > Also I have tried to connect to my Motorola v600 phone, but without success. I can successfully upload files to it using OPUSH, > but cannot download files. For any my action (using OPUSH and FTRN) I receive Forbidden(0x43) response. Maybe the cause is Motorola's > implementation of those protocols? Or some kind of security on the phone? In nearest future I will try to use my phone as GPRS modem. > of OPUSH? no, i do not think this is the problem with your phone. max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Apr 5 17:44:25 2005 Return-Path: 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 CC39C16A4CF for ; Tue, 5 Apr 2005 17:44:25 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF2F043D3F for ; Tue, 5 Apr 2005 17:44: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 36BE13BE3A; Tue, 5 Apr 2005 12:44:24 -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 16042-01-36; Tue, 5 Apr 2005 12:44:24 -0500 (CDT) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44]) by mailgate1b.savvis.net (Postfix) with ESMTP id F21D23BE2C; Tue, 5 Apr 2005 12:44:23 -0500 (CDT) Received: from s228130hz1ew171.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Tue, 5 Apr 2005 12:44:15 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew171.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Tue, 5 Apr 2005 12:44:12 -0500 Message-ID: <4252CE67.90007@savvis.net> Date: Tue, 05 Apr 2005 10:44:07 -0700 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Julian Elischer References: <41D0AF12.5000902@elischer.org> <41D0C192.4010002@savvis.net> <41D0C87E.2090201@elischer.org> <41D0CBAE.4090608@savvis.net> <41D13D7A.2030908@elischer.org> <41D1BE99.20500@savvis.net> <41D1C56F.7040504@elischer.org> <41D1CC19.8070308@savvis.net> <41D22495.5060304@elischer.org> <41D2EB4F.6050600@savvis.net> <41D318BA.3020508@elischer.org> <41D31A8B.7020906@savvis.net> <41D31E4F.2030805@elischer.org> <41D328EA.50001@savvis.net> <41D369FE.6090005@elischer.org> <41D3711A.1020501@savvis.net> <41D375A8.3070704@savvis.net> <41D375E7.9060602@savvis.net> <41D379FC.1020308@savvis.net> <41D38E5E.2040202@elischer.org> <41D3919D.3020508@savvis.net> <41D3BF3A.4020008@elischer.org> <41D42FDC.1010908@savvis.net> <425239DA.1020606@elischer.org> In-Reply-To: <425239DA.1020606@elischer.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 05 Apr 2005 17:44:12.0945 (UTC) FILETIME=[14493010:01C53A07] X-Virus-Scanned: amavisd-new at savvis.net cc: freebsd-bluetooth@freebsd.org Subject: Re: Broadcom 35xx bluetooth dongle. X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2005 17:44:25 -0000 Julian, > ok so it isn;t working any more... > What have I done wrong? > jules# kldload ng_ubt > jules# sh /etc/rc.bluetooth start ubt0 looks fine > jules# hcsecd -d > hcsecd[1152]: Restored link key for the entry, remote bdaddr > 00:0a:28:72:c8:4d, name 'JulianE-cell' looks fine > (back on original window;) > jules# hccontrol -n ubt0hci inquiry > Inquiry result, num_responses=1 looks fine too > jules# hccontrol -n ubt0hci remote_name_request cell > BD_ADDR: JulianE-cell > Name: JulianE-cell > jules# l2ping -a cell -c 3 > 44 bytes from JulianE-cell seq_no=0 time=1571.147 ms result=0 > 44 bytes from JulianE-cell seq_no=1 time=20.375 ms result=0 > 44 bytes from JulianE-cell seq_no=2 time=18.803 ms result=0 looks fine > jules# hccontrol -n ubt0hci read_connection_list > Remote BD_ADDR Handle Type Mode Role Encrypt Pending Queue State that might be ok. locally originated baseband connection will be disconnected automatically after 5 sec (configurable) of inactivity. if it has been 5 sec (or more) since you have terminated l2ping then baseband connection will go down. > jules# hccontrol -n ubt0hci write_authentication_enable 1 > jules# hccontrol -n ubt0hci read_authentication_enable > Authentication Enable: Enabled [1] that's fine. what it means is that local host will authenticate *incoming* connections. > jules# l2control -a cell read_channel_list > l2control: Could not bind socket, bdaddr=00:0a:28:72:c8:4d: Network is down ok, this is wrong. l2control(8) is used to get information about *local* devices. that is you should use "l2control -a BD_ADDR_of_bt_dongle." this is kinda hccontrol(8), but in hccontrol(8) we use name of the local device and in l2control(8) bd_addr of the local device. because you do not have local device with bd_addr 00:0a:28:72:c8:4d attached to the system you get this error message. > jules# sdpcontrol -a cell browse > Could not execute command "browse". Permission denied > jules# hccontrol -n ubt0hci write_authentication_enable 0 > jules# sdpcontrol -a cell browse [...] wow. that weird. did you try to wait a few sec. after first failure and then try again (without changing write_authentication_enable back to 0). i just tried this with my nokia 6820 and it works. beetle# hccontrol -n ubt0hci write_authentication_enable 1 beetle# sdpcontrol -a nokia.phone browse [...] [hcsecd output] hcsecd[4217]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 00:02:ee:df:f7:19 hcsecd[4217]: Found matching entry, remote bdaddr 00:02:ee:df:f7:19, name 'Nokia 6820 phone', link key exists hcsecd[4217]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr 00:02:ee:df:f7:19 [hcidump output] < HCI Command: Create Connection(0x01|0x0005) plen 13 19 F7 DF EE 02 00 18 CC 00 00 00 00 01 > HCI Event: Command Status(0x0f) plen 4 00 01 05 04 > HCI Event: Link Key Request(0x17) plen 6 19 F7 DF EE 02 00 < HCI Command: Link Key Request Reply(0x01|0x000b) plen 22 i'd like you to try the following: 1) hcsecd -d 2) hcidump -w dump 3) hccontrol -n ubt0hci write_authentication_enable 1 4) sdpcontrol -a cell browse if (4) fails wait a few sec and try (4) again. 5) kill hcidump and send me the dump file. > jules# obexapp -f -a cell -C FTRN > jules# < nothing happens. hcsecd on other windo however prints: > > hcsecd[1152]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr > 00:0a:28:72:c8:4d > hcsecd[1152]: Found matching entry, remote bdaddr 00:0a:28:72:c8:4d, > name 'JulianE-cell', link key exists > hcsecd[1152]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr > 00:0a:28:72:c8:4d > > (I have not changed the key as far as I know) hmmm... strange... binary hcidump please? > jules# l2control -a cell read_channel_list > l2control: Could not bind socket, bdaddr=00:0a:28:72:c8:4d: Network is down again that would not work > jules# > (deleted laptop from phone.. recreated with pin in hcsecd.conf) > > jules# obexapp -a cell -f -C 9 > Could not connect to the remote OBEX server. Response: Bad Request > (0x40). Service: File Browsing > jules# how about the following: 1) on your phone delete all 'paired devices' 2) delete /var/db/hcsecd.keys file (or at least delete the key for your cell phone) 3) 'pair' phone and computer > oh oh.. this looks familiar.. > did you check in the changes that got me going last time? > maybe I accidentally refreshed the port... there was no changes to the port for at least two months. i also did not make any changes to the stack itself. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 6 21:33:21 2005 Return-Path: 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 BCE2A16A4CE for ; Wed, 6 Apr 2005 21:33:21 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4162C43D4C for ; Wed, 6 Apr 2005 21:33:21 +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 9ECFC3BF00; Wed, 6 Apr 2005 16:33:20 -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 29502-01-96; Wed, 6 Apr 2005 16:33:20 -0500 (CDT) Received: from out002.email.savvis.net (out002.apptix.savvis.net [216.91.32.45]) by mailgate1b.savvis.net (Postfix) with ESMTP id 6AB8C3BE59; Wed, 6 Apr 2005 16:33:20 -0500 (CDT) Received: from s228130hz1ew031.apptix-01.savvis.net ([10.146.4.28]) by out002.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 6 Apr 2005 16:33:11 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew031.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 6 Apr 2005 16:33:12 -0500 Message-ID: <4254558C.1020708@savvis.net> Date: Wed, 06 Apr 2005 14:33:00 -0700 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org Content-Type: multipart/mixed; boundary="------------040300090805040104050607" X-OriginalArrivalTime: 06 Apr 2005 21:33:12.0871 (UTC) FILETIME=[3C554370:01C53AF0] X-Virus-Scanned: amavisd-new at savvis.net Subject: Recent bluetooth problems X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2005 21:33:21 -0000 This is a multi-part message in MIME format. --------------040300090805040104050607 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Dear Bluetooth Users, recently i have received few email that describe problems with rfcomm_pppd(8), gammu and gnokki. it turns out there was a bug in my code. rfcomm protocol was incorrectly marked as PR_ATOMIC (exchange atomic messages only). the problem was that any data left (after a read(2) call) in the rfcomm socket buffer were incorrectly discarded. the attached patch was committed to -current. i have verified that it fixes gnokii problem, but i'm interested to know if it fixes other problems as well. please try it and let me know if you still have problems. thanks, max --------------040300090805040104050607 Content-Type: text/plain; name="ng_btsocket.c.diff.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="ng_btsocket.c.diff.txt" =================================================================== RCS file: /usr/local/www/cvsroot/FreeBSD/src/sys/netgraph/bluetooth/socket/ng_btsocket.c,v retrieving revision 1.10 retrieving revision 1.11 diff -u -p -r1.10 -r1.11 --- src/sys/netgraph/bluetooth/socket/ng_btsocket.c 2005/01/07 01:45:44 1.10 +++ src/sys/netgraph/bluetooth/socket/ng_btsocket.c 2005/04/06 20:54:05 1.11 @@ -28,7 +28,7 @@ * SUCH DAMAGE. * * $Id: ng_btsocket.c,v 1.4 2003/09/14 23:29:06 max Exp $ - * $FreeBSD: /usr/local/www/cvsroot/FreeBSD/src/sys/netgraph/bluetooth/socket/ng_btsocket.c,v 1.10 2005/01/07 01:45:44 imp Exp $ + * $FreeBSD: /usr/local/www/cvsroot/FreeBSD/src/sys/netgraph/bluetooth/socket/ng_btsocket.c,v 1.11 2005/04/06 20:54:05 emax Exp $ */ #include @@ -182,7 +182,7 @@ static struct protosw ng_btsocket_proto SOCK_STREAM, /* protocol type */ &ng_btsocket_domain, /* backpointer to domain */ BLUETOOTH_PROTO_RFCOMM, /* protocol */ - PR_ATOMIC | PR_CONNREQUIRED, /* flags */ + PR_CONNREQUIRED, /* flags */ NULL, NULL, NULL, /* input, output, ctlinput */ ng_btsocket_rfcomm_ctloutput, /* ctloutput */ NULL, /* ousrreq() */ --------------040300090805040104050607-- From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 6 23:04:27 2005 Return-Path: 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 6741D16A4CE for ; Wed, 6 Apr 2005 23:04:27 +0000 (GMT) Received: from madpilot.net (dadovago8197.dada.it [195.110.114.197]) by mx1.FreeBSD.org (Postfix) with SMTP id F1B4443D45 for ; Wed, 6 Apr 2005 23:04:25 +0000 (GMT) (envelope-from mad@madpilot.net) Received: (qmail 91299 invoked from network); 6 Apr 2005 23:04:23 -0000 Received: from wedge.madpilot.net (192.168.13.11) by 0 with SMTP; 6 Apr 2005 23:04:23 -0000 Received: from wedge.madpilot.net (localhost.madpilot.net [127.0.0.1]) by wedge.madpilot.net (8.13.3/8.13.3) with ESMTP id j36N4HhX059054; Thu, 7 Apr 2005 01:04:17 +0200 (CEST) (envelope-from mad@wedge.madpilot.net) Received: (from mad@localhost) by wedge.madpilot.net (8.13.3/8.13.3/Submit) id j36N4G2l058933; Thu, 7 Apr 2005 01:04:16 +0200 (CEST) (envelope-from mad) Date: Thu, 7 Apr 2005 01:04:16 +0200 From: Guido Falsi To: Maksim Yevmenkin Message-ID: <20050406230416.GA26165@wedge.madpilot.net> References: <4254558C.1020708@savvis.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4254558C.1020708@savvis.net> X-Operating-System: FreeBSD 5.4-STABLE X-PGP-Key: http://www.madpilot.net/~mad/PGP-public-key.asc User-Agent: Mutt/1.5.9i cc: freebsd-bluetooth@freebsd.org Subject: Re: Recent bluetooth problems X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2005 23:04:27 -0000 On Wed, Apr 06, 2005 at 02:33:00PM -0700, Maksim Yevmenkin wrote: > > the attached patch was committed to -current. i have verified that it > fixes gnokii problem, but i'm interested to know if it fixes other > problems as well. please try it and let me know if you still have problems. Just to know, is this patch planned for MFC in -stable in the near future? I'm sorry I'm not using bluetooth in the described scenario so I can't do any testing. In my setup I did not notice any problems so far. -- Guido Falsi From owner-freebsd-bluetooth@FreeBSD.ORG Wed Apr 6 23:08:51 2005 Return-Path: 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 A899516A4CE for ; Wed, 6 Apr 2005 23:08:51 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C93443D41 for ; Wed, 6 Apr 2005 23:08:51 +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 8B59C3C031; Wed, 6 Apr 2005 18:08:50 -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 01185-01-95; Wed, 6 Apr 2005 18:08:50 -0500 (CDT) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44]) by mailgate1b.savvis.net (Postfix) with ESMTP id 5FF443BFA2; Wed, 6 Apr 2005 18:08:50 -0500 (CDT) Received: from s228130hz1ew031.apptix-01.savvis.net ([10.146.4.28]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 6 Apr 2005 18:08:48 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew031.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Wed, 6 Apr 2005 18:08:43 -0500 Message-ID: <42546BFA.10605@savvis.net> Date: Wed, 06 Apr 2005 16:08:42 -0700 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Guido Falsi References: <4254558C.1020708@savvis.net> <20050406230416.GA26165@wedge.madpilot.net> In-Reply-To: <20050406230416.GA26165@wedge.madpilot.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 06 Apr 2005 23:08:43.0729 (UTC) FILETIME=[9430CC10:01C53AFD] X-Virus-Scanned: amavisd-new at savvis.net cc: freebsd-bluetooth@freebsd.org Subject: Re: Recent bluetooth problems X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Apr 2005 23:08:51 -0000 Guido, >> the attached patch was committed to -current. i have verified that >> it fixes gnokii problem, but i'm interested to know if it fixes >> other problems as well. please try it and let me know if you still >> have problems. > > Just to know, is this patch planned for MFC in -stable in the near > future? yes, in required 3 days + time to get approval from re@ > I'm sorry I'm not using bluetooth in the described scenario so I > can't do any testing. In my setup I did not notice any problems so > far. are you using rfcomm at all? if so then you should not see any difference if you had no problems before. if you had problems before then this patch *might* fix them. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Apr 7 17:44:20 2005 Return-Path: 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 061E916A4CE for ; Thu, 7 Apr 2005 17:44:20 +0000 (GMT) Received: from mailgate1b.savvis.net (mailgate1b.savvis.net [216.91.182.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8C68243D53 for ; Thu, 7 Apr 2005 17:44:19 +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 E43273BEF9 for ; Thu, 7 Apr 2005 12:44:18 -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 32000-01-33 for ; Thu, 7 Apr 2005 12:44:18 -0500 (CDT) Received: from out001.email.savvis.net (out001.apptix.savvis.net [216.91.32.44]) by mailgate1b.savvis.net (Postfix) with ESMTP id BB27C3BE2D for ; Thu, 7 Apr 2005 12:44:18 -0500 (CDT) Received: from s228130hz1ew171.apptix-01.savvis.net ([10.146.4.29]) by out001.email.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 7 Apr 2005 12:43:59 -0500 Received: from [10.254.186.111] ([66.35.239.94]) by s228130hz1ew171.apptix-01.savvis.net with Microsoft SMTPSVC(6.0.3790.211); Thu, 7 Apr 2005 12:43:52 -0500 Message-ID: <42557162.9000500@savvis.net> Date: Thu, 07 Apr 2005 10:44:02 -0700 From: Maksim Yevmenkin User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040822 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org References: <4254558C.1020708@savvis.net> <20050406230416.GA26165@wedge.madpilot.net> <42546BFA.10605@savvis.net> <20050407121449.GA64681@wedge.madpilot.net> <425566CD.1040508@savvis.net> <20050407173236.GA712@wedge.madpilot.net> In-Reply-To: <20050407173236.GA712@wedge.madpilot.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Apr 2005 17:43:52.0960 (UTC) FILETIME=[5D333800:01C53B99] X-Virus-Scanned: amavisd-new at savvis.net Subject: Re: Recent bluetooth problems X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2005 17:44:20 -0000 Dear Bluetooth Users, recently i have received a couple of problem reports. both describe the same problem: when using bluetooth to provide LAN access using rfcomm_pppd(8) to the remote clients PPP connection is terminated prematurely. the following error appears in the /var/log/messages file: ng_btsocket_rfcomm_session_send: Could not send data to L2CAP socket, error=40 in both cases one of the peers was Windows machine (client) and other was obviously FreeBSD (server). i'm trying to reproduce the problem here. if you have similar configuration and have experienced this problem could you please provide: 1) detailed description of the bluetooth devices (manufacturer, model, etc.) if possible provide output of 'hccontrol read_local_version_information' and 'hccontrol read_local_supported_features'. 2) FreeBSD dmesg output (better if booted with -v) 3) Windows version and Windows bluetooth software and its version also if you are using similar configuration and you have no problem that would be nice to know too. thanks, max