From owner-freebsd-mobile Wed Mar 12 16: 7:10 2003 Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4F2B337B401 for ; Wed, 12 Mar 2003 16:07:06 -0800 (PST) Received: from a119-77.dialup.iol.cz (a119-77.dialup.iol.cz [194.228.77.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 04E2843F93 for ; Wed, 12 Mar 2003 16:06:43 -0800 (PST) (envelope-from pav@oook.cz) Received: from [127.0.0.1] (localhost.oook.cz [127.0.0.1]) by pav.oook.cz (8.12.6/8.12.6) with ESMTP id h2D10laA001976; Thu, 13 Mar 2003 01:01:28 GMT (envelope-from pav@oook.cz) Subject: RE: Anycom bluetooth progress From: Pav Lucistnik To: Maksim Yevmenkin Cc: freebsd-mobile@freebsd.org In-Reply-To: <790A8B1F40ACA848939EBD247AE490302794E6@scl8ex04.int.exodus.net> References: <790A8B1F40ACA848939EBD247AE490302794E6@scl8ex04.int.exodus.net> Content-Type: text/plain Organization: Message-Id: <1047517246.1717.13.camel@pav.oook.cz> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 13 Mar 2003 01:00:47 +0000 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On po, 2003-03-10 at 23:12, Maksim Yevmenkin wrote: > > I noticed there is no rc.bluetooth in march tarball, so I reused it and > > userland tools from february tarball. > > oops my fault. i have uploaded updated tarball at the same location. > please DO NOT use old userspace and new kernel. this WILL NOT work. > you should > > 1) download new tarball > 2) update haders /usr/include/netgraph/bluetooth/include > 3) build and install new kernel and userspace (usr.{s}bin)/bluetooth Done. Now l2ping works for me. > > My goal is to get GPRS working over bluetooth and T39 mobile phone. > > note: you also will need the attached ppp patch. How do I make dialup over my phone? I tried # rfcomm_pppd -a 00:80:37:29:19:a4 -c -C 1 -d -l rfcomm-dialup rfcomm_pppd[1787]: Could not connect socket. Connection refused (61) # hcidump -x HCIDump - HCI packet analyzer ver 1.4 device: any snap_len: 65535 filter: 0xffffffff < ACL data: handle 0x0029 flags 0x02 dlen 12 L2CAP(s): Connect req: psm 3 scid 0x0043 > HCI Event: Number of Completed Packets(0x13) plen 5 01 29 00 01 00 > ACL data: handle 0x0029 flags 0x02 dlen 16 L2CAP(s): Connect rsp: dcid 0x0041 scid 0x0043 result 0 status 0 < ACL data: handle 0x0029 flags 0x02 dlen 16 L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 4 MTU 132 > HCI Event: Number of Completed Packets(0x13) plen 5 01 29 00 01 00 > ACL data: handle 0x0029 flags 0x02 dlen 17 > ACL data: handle 0x0029 flags 0x01 dlen 1 L2CAP(s): Config rsp: scid 0x0043 flags 0x0000 result 0 clen 4 MTU 132 > ACL data: handle 0x0029 flags 0x02 dlen 16 L2CAP(s): Config req: dcid 0x0043 flags 0x0000 clen 4 MTU 132 < ACL data: handle 0x0029 flags 0x02 dlen 14 L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 0 < ACL data: handle 0x0029 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 29 00 01 00 > HCI Event: Number of Completed Packets(0x13) plen 5 01 29 00 01 00 > ACL data: handle 0x0029 flags 0x02 dlen 8 L2CAP(d): cid 0x43 len 4 [psm 3] RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7 < ACL data: handle 0x0029 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 2 frame_type 0 credit_flow 15 pri 0 ack_timer 0 frame_size 127 max_retrans 0 credits 7 > HCI Event: Number of Completed Packets(0x13) plen 5 01 29 00 01 00 > ACL data: handle 0x0029 flags 0x02 dlen 17 > ACL data: handle 0x0029 flags 0x01 dlen 2 L2CAP(d): cid 0x43 len 15 [psm 3] RFCOMM(s): PN RSP: cr 0 dlci 0 pf 0 ilen 10 fcs 0xaa mcc_len 8 dlci 2 frame_type 0 credit_flow 0 pri 7 ack_timer 0 frame_size 127 max_retrans 0 credits 0 < ACL data: handle 0x0029 flags 0x02 dlen 8 L2CAP(d): cid 0x41 len 4 [psm 3] RFCOMM(s): SABM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x59 > HCI Event: Number of Completed Packets(0x13) plen 5 01 29 00 01 00 > ACL data: handle 0x0029 flags 0x02 dlen 8 L2CAP(d): cid 0x43 len 4 [psm 3] RFCOMM(s): DM: cr 1 dlci 2 pf 1 ilen 0 fcs 0x73 < ACL data: handle 0x0029 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 29 00 01 00 > ACL data: handle 0x0029 flags 0x02 dlen 8 L2CAP(d): cid 0x43 len 4 [psm 3] RFCOMM(s): UA: cr 1 dlci 0 pf 1 ilen 0 fcs 0xd7 < ACL data: handle 0x0029 flags 0x02 dlen 12 L2CAP(s): Disconn req: dcid 0x0041 scid 0x0043 > HCI Event: Number of Completed Packets(0x13) plen 5 01 29 00 01 00 > ACL data: handle 0x0029 flags 0x02 dlen 12 L2CAP(s): Disconn rsp: dcid 0x0041 scid 0x0043 I suppose phone refused connection because it's not paired with my computer. I had to pair my Palm handheld with phone when I used it. I found hcsecd, read it's manpage, added this to /usr/local/etc/hcsecd.conf: device { bdaddr 00:80:37:29:19:a4; name "Pavi T39"; key nokey; pin "1234"; } and started hcsecd. Tried pairing on phone, using code "1234". Pairing failed, hcsecd's output was silent, here is hcidump: > HCI Event: Connect Request(0x04) plen 10 A4 19 29 37 80 00 04 02 52 01 < HCI Command: Accept Connection Request(0x01|0x0009) plen 7 A4 19 29 37 80 00 00 > HCI Event: Command Status(0x0f) plen 4 00 01 09 04 > HCI Event: Connect Complete(0x03) plen 11 1A 29 00 A4 19 29 37 80 00 01 00 What now? -- Pav Lucistnik To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message