From owner-freebsd-bluetooth@FreeBSD.ORG Sun Dec 11 15:11:50 2005 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 D4DE816A420 for ; Sun, 11 Dec 2005 15:11:50 +0000 (GMT) (envelope-from pi@c0mplx.org) Received: from home.c0mplx.org (home.c0mplx.org [213.178.180.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 308FF43D66 for ; Sun, 11 Dec 2005 15:11:47 +0000 (GMT) (envelope-from pi@c0mplx.org) Received: from pi by home.c0mplx.org with local (Exim 4.52) id 1ElSrb-0009FO-FY for freebsd-bluetooth@freebsd.org; Sun, 11 Dec 2005 16:11:47 +0100 Date: Sun, 11 Dec 2005 16:11:47 +0100 From: Kurt Jaeger To: freebsd-bluetooth@freebsd.org Message-ID: <20051211151147.GC3159@home.c0mplx.org> References: <20050903212613.GD76888@home.c0mplx.org> <20050903213035.GE76888@home.c0mplx.org> <4321DAAC.3030905@savvis.net> <20050911081028.GA29501@home.c0mplx.org> <4325D9BD.3090208@savvis.net> <20050912203711.GA2512@home.c0mplx.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050912203711.GA2512@home.c0mplx.org> Subject: Re: 3Com PCMCIA 3CRWB6096B ? 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: Sun, 11 Dec 2005 15:11:51 -0000 Hi! > > if you could please undo your changes to the ng_bt3c(4) driver, plug > > your card back and send me the dmesg output of sio(4) driver that would > > be nice. > > I'll do this and report back. [this took quite a bit of time] Hmm, seems strange, but the system detects a sio4 after boot: sio4: irq maps: 0x401 0x409 0x401 0x401 sio4: at port 0x300-0x307,0x3e8-0x3ef irq 3 drq 3 on isa0 sio4: type 16550A If I input the card, the following appears: pcib1: device pccard1 requested decoded memory range 0x90000000-0x903fffff pccard1: CIS version PC Card Standard 7.1 pccard1: CIS info: 3Com, 3CRWB6096B Bluetooth PC Card, , pccard1: Manufacturer code 0x101, product 0x41 pccard1: function 0: serial port, ccr addr f8 mask f pccard1: function 0, config table entry 1: I/O card; irq mask ffff; iomask 4, io space 0-f; maxtwins 7; rdybsy_active io8 irqshare irqlevel pccard1: function 0, config table entry 2: I/O card; irq mask ffff; iomask 4, io space 0-f; maxtwins 7; rdybsy_active io8 irqshare irqlevel pcib1: device pccard1 requested decoded memory range 0x90000000-0x903fffff sio5: <3Com 3CRWB6096B Bluetooth PC Card> at port 0x100-0x10f irq 10 function 0 config 1 on pccard1 device_attach: sio5 attach returned 6 -- pi@c0mplx.org +49 171 3101372 15 years to go ! From owner-freebsd-bluetooth@FreeBSD.ORG Sun Dec 11 19:16:02 2005 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 57F7316A41F for ; Sun, 11 Dec 2005 19:16:02 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out0.tiscali.nl (smtp-out0.tiscali.nl [195.241.79.175]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42E6943D46 for ; Sun, 11 Dec 2005 19:16:01 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [82.171.39.195] (helo=guido.klop.ws) by smtp-out0.tiscali.nl with smtp (Tiscali http://www.tiscali.nl) id 1ElWfw-0000hd-7c for ; Sun, 11 Dec 2005 20:16:00 +0100 Received: (qmail 2216 invoked from network); 11 Dec 2005 19:15:58 -0000 Received: from localhost.thuis.klop.ws (HELO outgoing.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 11 Dec 2005 19:15:58 -0000 Date: Sun, 11 Dec 2005 20:15:56 +0100 To: freebsd-bluetooth@freebsd.org From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: User-Agent: Opera M2/8.51 (FreeBSD, build 1462) Subject: rfcomm_pppd with hp ipaq hw6515 with GPRS 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: Sun, 11 Dec 2005 19:16:02 -0000 Hello, I'm trying to connect my laptop to the GPRS network of Telfort in The Netherlands via an ipaq pda with bluetooth. Bluetooth works. 'rfcomm_pppd -a pda -c -C DUN -l rfcomm' connects to the pda. The pda shows a popup about the connection, but it dissapears faster than I can read it. And then a popup with 'DUN connection has disconnected'. Does anybody have this working? With what config? Ronald. uname -a FreeBSD laptop.klop.ws 6.0-STABLE FreeBSD 6.0-STABLE #0: Sat Nov 5 23:29:59 CET 2005 root@laptop.klop.ws:/usr/obj/usr/src/sys/LAPTOP i386 I added the rfcomm_pppd manpage settings to ppp.conf # This is IMPORTANT option enable force-scripts # You might want to change these set authname set authkey set phone "*99***1#" # You might want to adjust dial string as well set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \ \"\" AT OK-AT-OK ATE1Q0 OK \\dATD\\T TIMEOUT 40 CONNECT" set login set timeout 30 enable dns resolv rewrite set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR My ppp.log says this. Dec 11 20:13:06 laptop ppp[797]: Phase: Using interface: tun0 Dec 11 20:13:06 laptop ppp[797]: Phase: deflink: Created in closed state Dec 11 20:13:06 laptop ppp[797]: tun0: Command: default: ident user-ppp VERSION (built COMPILATIONDATE) Dec 11 20:13:06 laptop ppp[797]: tun0: Command: default: set device /dev/cuad4 Dec 11 20:13:06 laptop ppp[797]: tun0: Command: default: set speed 115200 Dec 11 20:13:06 laptop ppp[797]: tun0: Command: default: set dial ABORT BUSY ABORT NO\sCARRIER TIMEOUT 5 "" AT OK-AT-OK ATE1Q0 OK \dATDT\T TIMEOUT 40 CONNECT Dec 11 20:13:06 laptop ppp[797]: tun0: Command: default: set timeout 180 Dec 11 20:13:06 laptop ppp[797]: tun0: Command: default: enable dns Dec 11 20:13:06 laptop ppp[797]: tun0: Command: rfcomm: enable force-scripts Dec 11 20:13:06 laptop ppp[797]: tun0: Command: rfcomm: set authname Dec 11 20:13:06 laptop ppp[797]: tun0: Command: rfcomm: set authkey Dec 11 20:13:06 laptop ppp[797]: tun0: Command: rfcomm: set phone *99***1# Dec 11 20:13:06 laptop ppp[797]: tun0: Command: rfcomm: set dial ABORT BUSY ABORT NO\sCARRIER TIMEOUT 5 "" AT OK-AT-OK ATE1Q0 OK \dATD\T TIMEOUT 40 CONNECT Dec 11 20:13:06 laptop ppp[797]: tun0: Command: rfcomm: set login Dec 11 20:13:06 laptop ppp[797]: tun0: Command: rfcomm: set timeout 30 Dec 11 20:13:06 laptop ppp[797]: tun0: Command: rfcomm: enable dns Dec 11 20:13:06 laptop ppp[797]: tun0: Command: rfcomm: resolv rewrite Dec 11 20:13:06 laptop ppp[797]: tun0: IPCP: Primary nameserver set to 255.255.255.255 Dec 11 20:13:06 laptop ppp[797]: tun0: Command: rfcomm: set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 Dec 11 20:13:06 laptop ppp[797]: tun0: Command: rfcomm: add default HISADDR Dec 11 20:13:06 laptop ppp[797]: tun0: Warning: Add route failed: 0.0.0.0/0 already exists Dec 11 20:13:06 laptop ppp[797]: tun0: Phase: PPP Started (direct mode). Dec 11 20:13:06 laptop ppp[797]: tun0: Phase: bundle: Establish Dec 11 20:13:06 laptop ppp[797]: tun0: Phase: deflink: closed -> opening Dec 11 20:13:06 laptop ppp[797]: tun0: Phase: deflink: Connected! Dec 11 20:13:06 laptop ppp[797]: tun0: Phase: deflink: opening -> dial Dec 11 20:13:06 laptop ppp[797]: tun0: Chat: Phone: *99***1# Dec 11 20:13:06 laptop ppp[797]: tun0: Chat: deflink: Dial attempt 1 of 1 Dec 11 20:13:06 laptop ppp[797]: tun0: Chat: Send: AT^M Dec 11 20:13:06 laptop ppp[797]: tun0: Chat: Expect(5): OK Dec 11 20:13:06 laptop ppp[797]: tun0: Chat: Received: ^M Dec 11 20:13:06 laptop ppp[797]: tun0: Chat: Received: OK^M Dec 11 20:13:06 laptop ppp[797]: tun0: Chat: Send: ATE1Q0^M Dec 11 20:13:06 laptop ppp[797]: tun0: Chat: Expect(5): OK Dec 11 20:13:06 laptop ppp[797]: tun0: Chat: Received: ^M Dec 11 20:13:06 laptop ppp[797]: tun0: Chat: Received: OK^M Dec 11 20:13:06 laptop ppp[797]: tun0: Chat: Send: ATD*99***1#^M Dec 11 20:13:08 laptop ppp[797]: tun0: Chat: Expect(40): CONNECT Dec 11 20:13:26 laptop ppp[797]: tun0: Chat: Received: ATD*99***1#^M^M Dec 11 20:13:26 laptop ppp[797]: tun0: Chat: Received: CONNECT^M Dec 11 20:13:26 laptop ppp[797]: tun0: Phase: deflink: dial -> carrier Dec 11 20:13:26 laptop ppp[797]: tun0: Phase: deflink: carrier -> login Dec 11 20:13:26 laptop ppp[797]: tun0: Phase: deflink: login -> lcp Dec 11 20:13:26 laptop ppp[797]: tun0: LCP: FSM: Using "deflink" as a transport Dec 11 20:13:26 laptop ppp[797]: tun0: LCP: deflink: State change Initial --> Closed Dec 11 20:13:26 laptop ppp[797]: tun0: LCP: deflink: State change Closed --> Stopped Dec 11 20:13:27 laptop ppp[797]: tun0: LCP: deflink: LayerStart Dec 11 20:13:27 laptop ppp[797]: tun0: LCP: deflink: SendConfigReq(1) state = Stopped Dec 11 20:13:27 laptop ppp[797]: tun0: LCP: ACFCOMP[2] Dec 11 20:13:27 laptop ppp[797]: tun0: LCP: PROTOCOMP[2] Dec 11 20:13:27 laptop ppp[797]: tun0: LCP: ACCMAP[6] 0x00000000 Dec 11 20:13:27 laptop ppp[797]: tun0: LCP: MRU[4] 1500 Dec 11 20:13:27 laptop ppp[797]: tun0: LCP: MAGICNUM[6] 0x109b429b Dec 11 20:13:27 laptop ppp[797]: tun0: LCP: deflink: State change Stopped --> Req-Sent Dec 11 20:13:30 laptop ppp[797]: tun0: LCP: deflink: SendConfigReq(1) state = Req-Sent Dec 11 20:13:30 laptop ppp[797]: tun0: LCP: ACFCOMP[2] Dec 11 20:13:30 laptop ppp[797]: tun0: LCP: PROTOCOMP[2] Dec 11 20:13:30 laptop ppp[797]: tun0: LCP: ACCMAP[6] 0x00000000 Dec 11 20:13:30 laptop ppp[797]: tun0: LCP: MRU[4] 1500 Dec 11 20:13:30 laptop ppp[797]: tun0: LCP: MAGICNUM[6] 0x109b429b Dec 11 20:13:33 laptop ppp[797]: tun0: LCP: deflink: SendConfigReq(1) state = Req-Sent Dec 11 20:13:33 laptop ppp[797]: tun0: LCP: ACFCOMP[2] Dec 11 20:13:33 laptop ppp[797]: tun0: LCP: PROTOCOMP[2] Dec 11 20:13:33 laptop ppp[797]: tun0: LCP: ACCMAP[6] 0x00000000 Dec 11 20:13:33 laptop ppp[797]: tun0: LCP: MRU[4] 1500 Dec 11 20:13:33 laptop ppp[797]: tun0: LCP: MAGICNUM[6] 0x109b429b Dec 11 20:13:36 laptop ppp[797]: tun0: LCP: deflink: SendConfigReq(1) state = Req-Sent Dec 11 20:13:36 laptop ppp[797]: tun0: LCP: ACFCOMP[2] Dec 11 20:13:36 laptop ppp[797]: tun0: LCP: PROTOCOMP[2] Dec 11 20:13:36 laptop ppp[797]: tun0: LCP: ACCMAP[6] 0x00000000 Dec 11 20:13:36 laptop ppp[797]: tun0: LCP: MRU[4] 1500 Dec 11 20:13:36 laptop ppp[797]: tun0: LCP: MAGICNUM[6] 0x109b429b Dec 11 20:13:39 laptop ppp[797]: tun0: LCP: deflink: SendConfigReq(1) state = Req-Sent Dec 11 20:13:39 laptop ppp[797]: tun0: LCP: ACFCOMP[2] Dec 11 20:13:39 laptop ppp[797]: tun0: LCP: PROTOCOMP[2] Dec 11 20:13:39 laptop ppp[797]: tun0: LCP: ACCMAP[6] 0x00000000 Dec 11 20:13:39 laptop ppp[797]: tun0: LCP: MRU[4] 1500 Dec 11 20:13:39 laptop ppp[797]: tun0: LCP: MAGICNUM[6] 0x109b429b Dec 11 20:13:42 laptop ppp[797]: tun0: LCP: deflink: LayerFinish Dec 11 20:13:42 laptop ppp[797]: tun0: LCP: deflink: State change Req-Sent --> Stopped Dec 11 20:13:42 laptop ppp[797]: tun0: LCP: deflink: State change Stopped --> Closed Dec 11 20:13:42 laptop ppp[797]: tun0: LCP: deflink: State change Closed --> Initial Dec 11 20:13:42 laptop ppp[797]: tun0: Phase: deflink: Disconnected! Dec 11 20:13:42 laptop ppp[797]: tun0: Phase: deflink: lcp -> logout Dec 11 20:13:42 laptop ppp[797]: tun0: Phase: deflink: logout -> hangup Dec 11 20:13:42 laptop ppp[797]: tun0: Phase: deflink: Disconnected! Dec 11 20:13:42 laptop ppp[797]: tun0: Phase: deflink: Connect time: 36 secs: 9 octets in, 270 octets out Dec 11 20:13:42 laptop ppp[797]: tun0: Phase: deflink: 1 packets in, 5 packets out Dec 11 20:13:42 laptop ppp[797]: tun0: Phase: total 7 bytes/sec, peak 22 bytes/sec on Sun Dec 11 20:13:34 2005 Dec 11 20:13:42 laptop ppp[797]: tun0: Phase: deflink: hangup -> closed Dec 11 20:13:42 laptop ppp[797]: tun0: Phase: bundle: Dead Dec 11 20:13:42 laptop ppp[797]: tun0: Phase: PPP Terminated (normal). -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-bluetooth@FreeBSD.ORG Sun Dec 11 19:50:58 2005 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 BF38616A420 for ; Sun, 11 Dec 2005 19:50:58 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out1.tiscali.nl (smtp-out1.tiscali.nl [195.241.79.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id E7F4543DA3 for ; Sun, 11 Dec 2005 19:50:43 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [82.171.39.195] (helo=guido.klop.ws) by smtp-out1.tiscali.nl with smtp (Tiscali http://www.tiscali.nl) id 1ElXDT-00058B-P3 for ; Sun, 11 Dec 2005 20:50:39 +0100 Received: (qmail 2335 invoked from network); 11 Dec 2005 19:50:38 -0000 Received: from localhost.thuis.klop.ws (HELO outgoing.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 11 Dec 2005 19:50:38 -0000 To: freebsd-bluetooth@freebsd.org References: Message-ID: Date: Sun, 11 Dec 2005 20:50:37 +0100 From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Opera M2/8.51 (FreeBSD, build 1462) Subject: Re: rfcomm_pppd with hp ipaq hw6515 with GPRS 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: Sun, 11 Dec 2005 19:50:58 -0000 On Sun, 11 Dec 2005 20:15:56 +0100, Ronald Klop wrote: > Hello, > > I'm trying to connect my laptop to the GPRS network of Telfort in The > Netherlands via an ipaq pda with bluetooth. > > Bluetooth works. > 'rfcomm_pppd -a pda -c -C DUN -l rfcomm' connects to the pda. > The pda shows a popup about the connection, but it dissapears faster > than I can read it. And then a popup with 'DUN connection has > disconnected'. > > Does anybody have this working? With what config? > > Ronald. Ok, I am trying this for a day-and-half (not fulltime) and 5 minutes after I send the previous e-mail I see a typo. In the rfcomm_pppd manpage the 'set dial' string should contain ATDT in stead of ATD. Plus for me the phone number '*99#' works and '*99***1#' doesn't, but I thing that might be pda specific. Thanks for the marvelous functionality of all this bluetooth stuff. I can now connect to a wireless network (GPRS) by a wireless network (BT). :-) Ronald. -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-bluetooth@FreeBSD.ORG Sun Dec 11 19:57:26 2005 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 E1CCD16A41F for ; Sun, 11 Dec 2005 19:57:26 +0000 (GMT) (envelope-from office@pershing.be) Received: from out-2.mail.amis.net (out-2.mail.amis.net [212.18.32.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1957343D76 for ; Sun, 11 Dec 2005 19:57:10 +0000 (GMT) (envelope-from office@pershing.be) Received: from localhost (in-4.mail.amis.net [212.18.32.23]) by out-2.mail.amis.net (Postfix) with ESMTP id 96C1410968A for ; Sun, 11 Dec 2005 20:57:07 +0100 (CET) Received: from in-4.mail.amis.net ([127.0.0.1]) by localhost (in-4.mail.amis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 09156-04 for ; Sun, 11 Dec 2005 20:57:04 +0100 (CET) Received: from smtp.amis.net (smtp.amis.net [IPv6:2001:15c0::41]) by in-4.mail.amis.net (Postfix) with ESMTP id C219CB4796 for ; Sun, 11 Dec 2005 20:57:04 +0100 (CET) Received: from office.pershing.be (cpe-212-18-59-182.dynamic.amis.net [212.18.59.182]) by smtp.amis.net (Postfix) with SMTP id A5287396801 for ; Sun, 11 Dec 2005 20:57:04 +0100 (CET) From: Branko To: freebsd-bluetooth@freebsd.org In-Reply-To: References: Organization: SOL X-Mailer: SOLmail ver 5.0.1 X-Operating-System: SOLos hack proof operating system Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20051211195704.A5287396801@smtp.amis.net> Date: Sun, 11 Dec 2005 20:57:04 +0100 (CET) X-Virus-Scanned: by amavisd-new at amis.net X-Spam-Status: No, score=-5.784 required=5 tests=[ALL_TRUSTED=-3.3, AWL=0.115, BAYES_00=-2.599] X-Spam-Score: -5.784 X-Spam-Level: Subject: Re: rfcomm_pppd with hp ipaq hw6515 with GPRS 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: Sun, 11 Dec 2005 19:57:27 -0000 On Sun, 11 Dec 2005 20:50:37 +0100 "Ronald Klop" wrote: > On Sun, 11 Dec 2005 20:15:56 +0100, Ronald Klop > wrote: > > > Hello, > > > > I'm trying to connect my laptop to the GPRS network of Telfort in The > > Netherlands via an ipaq pda with bluetooth. > > > > Bluetooth works. > > 'rfcomm_pppd -a pda -c -C DUN -l rfcomm' connects to the pda. > > The pda shows a popup about the connection, but it dissapears faster > > than I can read it. And then a popup with 'DUN connection has > > disconnected'. > > > > Does anybody have this working? With what config? > > > > Ronald. > > Ok, I am trying this for a day-and-half (not fulltime) and 5 minutes after > I send the previous e-mail I see a typo. > In the rfcomm_pppd manpage the 'set dial' string should contain ATDT in > stead of ATD. U must contact your mobile provider to get this strings :) > Plus for me the phone number '*99#' works and '*99***1#' doesn't, but I > thing that might be pda specific. Yes it is phone/pda specific > Thanks for the marvelous functionality of all this bluetooth stuff. I can > now connect to a wireless network (GPRS) by a wireless network (BT). :-) > > Ronald. > > -- > Ronald Klop > Amsterdam, The Netherlands > _______________________________________________ > 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 Mon Dec 12 04:40:18 2005 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 284BE16A41F for ; Mon, 12 Dec 2005 04:40:18 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE8BC43D5F for ; Mon, 12 Dec 2005 04:40:16 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [192.168.1.254] (really [70.32.199.60]) by mta9.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051212044016.DHSK11358.mta9.adelphia.net@[192.168.1.254]>; Sun, 11 Dec 2005 23:40:16 -0500 Message-ID: <439CFF28.3070505@savvis.net> Date: Sun, 11 Dec 2005 20:40:08 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ronald Klop References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: rfcomm_pppd with hp ipaq hw6515 with GPRS 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: Mon, 12 Dec 2005 04:40:18 -0000 Ronald, >> I'm trying to connect my laptop to the GPRS network of Telfort in The >> Netherlands via an ipaq pda with bluetooth. >> >> Bluetooth works. >> 'rfcomm_pppd -a pda -c -C DUN -l rfcomm' connects to the pda. >> The pda shows a popup about the connection, but it dissapears faster >> than I can read it. And then a popup with 'DUN connection has >> disconnected'. >> >> Does anybody have this working? With what config? > > Ok, I am trying this for a day-and-half (not fulltime) and 5 minutes > after I send the previous e-mail I see a typo. > In the rfcomm_pppd manpage the 'set dial' string should contain ATDT in > stead of ATD. the typo has been fixed in -current. i will mfc it to releng_5,6 shortly. thanks for noticing. i'm sorry about the typo and the time you had to spend on this. > Plus for me the phone number '*99#' works and '*99***1#' doesn't, but I > thing that might be pda specific. correct. this number might change depending on phone/pda model. that is why the man page has '# You might want to change these'. > Thanks for the marvelous functionality of all this bluetooth stuff. I > can now connect to a wireless network (GPRS) by a wireless network > (BT). :-) have you tried the other way around? i.e. use bluetooth lan client on your pda and have freebsd act as a bluetooth access point. does it work? the reason i'm asking is because few people report that there are some interoperability problems and i'm trying to build the list of devices that have this problem. i really want to get one of the problem devices so i can take a look and fix it. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Mon Dec 12 17:48:47 2005 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 034C316A41F for ; Mon, 12 Dec 2005 17:48:47 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4F48443D6B for ; Mon, 12 Dec 2005 17:48:46 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jBCHmbI10293; Mon, 12 Dec 2005 12:48:38 -0500 Message-ID: <439DB7F3.3080107@savvis.net> Date: Mon, 12 Dec 2005 09:48:35 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kurt Jaeger References: <20050903212613.GD76888@home.c0mplx.org> <20050903213035.GE76888@home.c0mplx.org> <4321DAAC.3030905@savvis.net> <20050911081028.GA29501@home.c0mplx.org> <4325D9BD.3090208@savvis.net> <20050912203711.GA2512@home.c0mplx.org> <20051211151147.GC3159@home.c0mplx.org> In-Reply-To: <20051211151147.GC3159@home.c0mplx.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: 3Com PCMCIA 3CRWB6096B ? 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: Mon, 12 Dec 2005 17:48:47 -0000 Kurt, >>>if you could please undo your changes to the ng_bt3c(4) driver, plug >>>your card back and send me the dmesg output of sio(4) driver that would >>>be nice. >> >>I'll do this and report back. > > [this took quite a bit of time] > > Hmm, seems strange, but the system detects a sio4 after boot: > > sio4: irq maps: 0x401 0x409 0x401 0x401 > sio4: at port 0x300-0x307,0x3e8-0x3ef irq 3 drq 3 on isa0 > sio4: type 16550A ok. it seems that version 2 has sio(4) compatible uart. does it work if you start bluetooth on sio4? > If I input the card, the following appears: > > pcib1: device pccard1 requested decoded memory range 0x90000000-0x903fffff > pccard1: CIS version PC Card Standard 7.1 > pccard1: CIS info: 3Com, 3CRWB6096B Bluetooth PC Card, , > pccard1: Manufacturer code 0x101, product 0x41 > pccard1: function 0: serial port, ccr addr f8 mask f > pccard1: function 0, config table entry 1: I/O card; irq mask ffff; iomask 4, io > space 0-f; maxtwins 7; rdybsy_active io8 irqshare irqlevel > pccard1: function 0, config table entry 2: I/O card; irq mask ffff; iomask 4, io > space 0-f; maxtwins 7; rdybsy_active io8 irqshare irqlevel > pcib1: device pccard1 requested decoded memory range 0x90000000-0x903fffff > sio5: <3Com 3CRWB6096B Bluetooth PC Card> at port 0x100-0x10f irq 10 function 0 > config 1 on pccard1 > device_attach: sio5 attach returned 6 you are not alone :( for whatever reason sio(4) and pccard never worked for me after NEWCARD went in :( you might try to ask Warner (imp) what is going on here. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Mon Dec 12 20:13:42 2005 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 6977C16A41F for ; Mon, 12 Dec 2005 20:13:42 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from smtp-out2.tiscali.nl (smtp-out2.tiscali.nl [195.241.79.177]) by mx1.FreeBSD.org (Postfix) with ESMTP id F009B43D5A for ; Mon, 12 Dec 2005 20:13:41 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from [82.171.39.195] (helo=guido.klop.ws) by smtp-out2.tiscali.nl with smtp (Tiscali http://www.tiscali.nl) id 1Elu3I-0007Zi-J9 for ; Mon, 12 Dec 2005 21:13:40 +0100 Received: (qmail 927 invoked from network); 12 Dec 2005 20:13:39 -0000 Received: from localhost.thuis.klop.ws (HELO outgoing.local) (127.0.0.1) by localhost.thuis.klop.ws with SMTP; 12 Dec 2005 20:13:39 -0000 To: freebsd-bluetooth@freebsd.org References: <439CFF28.3070505@savvis.net> Message-ID: Date: Mon, 12 Dec 2005 21:13:38 +0100 From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <439CFF28.3070505@savvis.net> User-Agent: Opera M2/8.51 (FreeBSD, build 1462) Subject: Re: rfcomm_pppd with hp ipaq hw6515 with GPRS 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: Mon, 12 Dec 2005 20:13:42 -0000 On Mon, 12 Dec 2005 05:40:08 +0100, Maksim Yevmenkin wrote: > Ronald, > > have you tried the other way around? i.e. use bluetooth lan client on > your pda and have freebsd act as a bluetooth access point. does it work? > the reason i'm asking is because few people report that there are some > interoperability problems and i'm trying to build the list of devices > that have this problem. i really want to get one of the problem devices > so i can take a look and fix it. > > thanks, > max I'll try this. But I don't understand the phone very much. I got it from my work and there is no manual with it. But I've setup a ppp server before, so I think it should be about the same. Ronald. -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-bluetooth@FreeBSD.ORG Tue Dec 13 01:41:08 2005 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 24EA016A420 for ; Tue, 13 Dec 2005 01:41:08 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from olive.qinip.net (olive.qinip.net [62.100.30.40]) by mx1.FreeBSD.org (Postfix) with ESMTP id A06DC43D5A for ; Tue, 13 Dec 2005 01:41:06 +0000 (GMT) (envelope-from ronald-freebsd8@klop.yi.org) Received: from henk.klop.ws (h8441134153.dsl.speedlinq.nl [84.41.134.153]) by olive.qinip.net (Postfix) with ESMTP id 6E53B18052 for ; Tue, 13 Dec 2005 02:41:04 +0100 (MET) Received: from laptop.klop.ws (unknown [10.0.2.3]) by henk.klop.ws (Postfix) with SMTP id AB1D91F77 for ; Tue, 13 Dec 2005 02:41:04 +0100 (CET) Received: (qmail 768 invoked from network); 7 Dec 2005 02:52:54 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 7 Dec 2005 02:52:54 -0000 Date: Wed, 07 Dec 2005 03:52:51 +0100 To: freebsd-bluetooth@freebsd.org References: <9307f5f20512030807x6eadc73cq9d9acc9dd5503a5b@mail.gmail.com> <4391E320.2090006@savvis.net> <9307f5f20512031333x61e9d141u85ea578711740712@mail.gmail.com> <43936F6B.1090003@savvis.net> <1133819097.4559.15.camel@localhost.localdomain> <4394E242.7030401@savvis.net> <9307f5f20512051937h26e4a99awb00083dccca21180@mail.gmail.com> <4395D6E6.6090103@savvis.net> From: "Ronald Klop" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-ID: In-Reply-To: <4395D6E6.6090103@savvis.net> User-Agent: Opera M2/8.50 (FreeBSD, build 1358) Subject: Re: Automatic bluetooth device initialization 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, 13 Dec 2005 01:41:08 -0000 If I understand it well. 1. Write a d-bus interface for bluetooth. 2. Write a FreeBSD Bluetooth/d-bus. 3. Write a Linux Bluetooth/d-bus. 4. Write a KDE d-bus link. 5. write a GNOME d-bus link. 6. Nobody will complain. Another option. 1. Rewrite libkbluetooth with ifdef _BSD_ options. 2. Rewrite libgnomebluetooth with ifdef _BSD_ options. 3. Nobody will complain. So, everything is open. Somebody has (a lot of|some) work to do. But a lot of people will be very happy when it is all done. Ronald. PS: I didn't mention Solaris or other possible Unix/POSIX based bluetooth stacks. On Tue, 06 Dec 2005 19:22:30 +0100, Maksim Yevmenkin wrote: > Paul, > >>> perhaps, we are talking about different things here. i do not >>> really understand what multiple language bindings have do with >>> bluetooth device initialization and lower level api. >> since coding gui applications in C is the second most boring thing on >> earth (the first being writing gui applications in asm :-) it's a >> good idea to do it in a higher level language, and since those >> clients have to communicate over dbus with the daemon, you'll need >> dbus bindings for your language of choice, and dbus does have them. > > perhaps i'm wrong, but you seem to be thinking about this in terms of > gui. if so, then i can compare it to building a house starting from the > roof. without foundation and walls it will fall down. > > gui, imo, should be the very last thing to worry about. it will be > trivial to write any gui when you have defined low level api. if you > like you can use d-bus or whatever messaging protocol of the day. > >>> it very much possible that d-bus is very well suited for >>> inter-application communications in kde/gnome/whatever desktop. >>> after all, this is what it is being developed for. what i do not >>> understand is why d-bus is being pushed all the way down and even >>> suggested as replacement for hci? >> I think marcel was talking about a dbus replacement for hcid, the >> linux bluetooth daemon. (after all HCI is part of the bluetooth >> specification and you can't replace that one :-) > > again, what is _wrong_ with raw hci sockets? > >>> instead of creating numerous d-bus bluetooth applications that know >>> how to work on particular system, why not just create one d-bus >>> bluetooth application that uses common low level bluetooth api? >> yes, that's how it would work in an ideal world... in this world, >> bluez has one way of doing things, freebsd has another, for example >> freebsd had its SDP api rewritten from scratch even if sdp has very >> little low-level programming involved and could easily have borrowed >> the bluez sdp code, but we all know licensing issues are a Bad Thing >> so let's not get over this again please. In the end, if you have a >> well-defined d-bus interface, you'll have applications that DO run >> regardless of the os. >> >>> what about not-kde/gnome/whatever applications (i.e. non-d-bus)? >>> are those just out of luck? >> fell free to suggest alternatives, but all the major linux >> distributions now have dbus, freebsd does have it, solaris will come >> along (but I don't know if opensolaris has a bluetooth stack yet ;-) >> and after 1.0 is out it will become quite a standard (no, I don't >> like creating dependencies, and I like even less adding new >> "standards", I _have_ been looking for alternatives, if there was a >> common low-level api probably noone wouldn't need a d-bus layer in >> the middle but this is not the case so...) > > as i tried to explain, the alternative would be common low level api. > > please, PLEASE, accept the fact that other (than linux) systems do > things _differently_. please do not think that you could just port d-bus > and/or whatever to freebsd/solaris/etc. but rather understand that the > major requirement is that bluetooth should be usable on out-of-the-box > system. in particular, on freebsd that means, i do not have to install > _any_ third party application, etc. > > if/when d-bus will be included into the base freebsd installation, i > will not have any problem with it. until then _any_ work based on > _optional_ software will be _optional_. which means we will have to > maintain two sets of bluetooth tools/libraries/etc. one is d-bus based > and other is not. imo, this is not going to solve the problem. > >>> i admit kde/gnome folks did a lot of work by integrating bluetooth, >>> but their work can not be re-used :( >> yes, that's the point >> >>> i wish their work would be in a form of re-usable user space >>> modules. i wish they would make it so anybody can just pick this or >>> that module and re-use it. for example, if i want to run obex file >>> server, i do not have to run kde/gnome/d-bus etc. >> but you could make a server which runs on top of the dbus interface, >> which isn't that bad. strictly speaking the only requirement is dbus, >> regardless of your favourite desktop manager; of course _clients_ may >> be more or less integrated into a particular desktop enviroment, for >> example some developer might want to implement an obex _client_ as a >> KIOslave for kde, another as a nautilus-vfs extension, yet another as >> something else, but the fact that there are soo many desktop >> environments to chose from (like the fact that every operating system >> has his own low-level api for the bluetooth stack) and that there's >> no established standard among them is something we have to live with >> :-( > > like i said, d-bus is likely not going to help you here. at least, not > on freebsd. everybody should sit down and talk. perhaps even write a > draft and send it to bluetooth sig, so they can publish it as a standard. > > 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.org" -- Ronald Klop Amsterdam, The Netherlands From owner-freebsd-bluetooth@FreeBSD.ORG Tue Dec 13 15:29:36 2005 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 C0F9216A424 for ; Tue, 13 Dec 2005 15:29:36 +0000 (GMT) (envelope-from bt@old.com.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 276D943D82 for ; Tue, 13 Dec 2005 15:29:16 +0000 (GMT) (envelope-from bt@old.com.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBDFTFHY019825 for ; Tue, 13 Dec 2005 17:29:15 +0200 (EET) (envelope-from bt@old.com.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 22069-02 for ; Tue, 13 Dec 2005 17:29:12 +0200 (EET) Received: from home (82.193.110.225.ipnet.kiev.ua [82.193.110.225]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBDFQEv0019762 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 13 Dec 2005 17:26:17 +0200 (EET) (envelope-from bt@old.com.ua) Date: Tue, 13 Dec 2005 17:26:16 +0200 (EET) From: Dmitry Dyomin X-X-Sender: old@home.old.com.ua To: freebsd-bluetooth@freebsd.org Message-ID: <20051213171917.N10381@home.old.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at ip.net.ua Subject: BT LAN connection with Symbian phones 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, 13 Dec 2005 15:29:37 -0000 Hello. I'm trying to connect my SE p900 to LAN via rfcomm_pppd. And I'm stuck upon a pack of 'Magic is same' errors I'm getting on the following command: rfcomm_pppd -S -a 0ld -C 7 -l rfcomm-server -u 1 I've tried to search google, this group, still did not fount the solution for this. Could anyone help me with this? Thanks. uname -a FreeBSD home.old.com.ua 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Fri Dec 2 03:19:07 EET 2005 root@home.old.com.ua:/usr/obj/usr/src/sys/HOME i386 rfcomm-server part of ppp.conf: rfcomm-server: set timeout 0 set lqrperiod 10 set ifaddr 10.0.0.1 10.0.0.2 enable lqr accept lqr disable pap deny pap disable chap deny chap accept dns and ppp.log: Dec 13 17:08:25 home ppp[10283]: tun1: LCP: QUALPROTO[8] proto c025, interval 10000ms Dec 13 17:08:25 home ppp[10283]: tun1: LCP: deflink: SendConfigNak(14) state = Req-Sent Dec 13 17:08:25 home ppp[10283]: tun1: LCP: MAGICNUM[6] 0xbde71b8b Dec 13 17:08:25 home ppp[10283]: tun1: LCP: deflink: RecvConfigNak(14) state = Req-Sent Dec 13 17:08:25 home ppp[10283]: tun1: LCP: MAGICNUM[6] 0xbde71b8b Dec 13 17:08:25 home ppp[10283]: tun1: LCP: Magic 0xbde71b8b is NAKed! Dec 13 17:08:25 home ppp[10283]: tun1: LCP: deflink: SendConfigReq(15) state = Req-Sent Dec 13 17:08:25 home ppp[10283]: tun1: LCP: ACFCOMP[2] Dec 13 17:08:25 home ppp[10283]: tun1: LCP: PROTOCOMP[2] Dec 13 17:08:25 home ppp[10283]: tun1: LCP: ACCMAP[6] 0x00000000 Dec 13 17:08:25 home ppp[10283]: tun1: LCP: MRU[4] 1500 Dec 13 17:08:25 home ppp[10283]: tun1: LCP: MAGICNUM[6] 0xff235ef9 Dec 13 17:08:25 home ppp[10283]: tun1: LCP: QUALPROTO[8] proto c025, interval 10000ms Dec 13 17:08:25 home ppp[10283]: tun1: LCP: deflink: RecvConfigReq(15) state = Req-Sent Dec 13 17:08:25 home ppp[10283]: tun1: LCP: ACFCOMP[2] Dec 13 17:08:25 home ppp[10283]: tun1: LCP: PROTOCOMP[2] Dec 13 17:08:25 home ppp[10283]: tun1: LCP: ACCMAP[6] 0x00000000 Dec 13 17:08:25 home ppp[10283]: tun1: LCP: MRU[4] 1500 Dec 13 17:08:25 home ppp[10283]: tun1: LCP: MAGICNUM[6] 0xff235ef9 Dec 13 17:08:25 home ppp[10283]: tun1: LCP: Magic is same (ff235ef9) - 15 times Dec 13 17:08:32 home ppp[10283]: tun1: LCP: QUALPROTO[8] proto c025, interval 10000ms Dec 13 17:08:32 home ppp[10283]: tun1: LCP: deflink: SendConfigNak(15) state = Req-Sent Dec 13 17:08:32 home ppp[10283]: tun1: LCP: MAGICNUM[6] 0xff235ef9 Dec 13 17:08:32 home ppp[10283]: tun1: Phase: deflink: Too many LCP NAKs sent - abandoning negotiation Dec 13 17:08:32 home ppp[10283]: tun1: LCP: deflink: SendIdent(0) state = Req-Sent Dec 13 17:08:32 home ppp[10283]: tun1: LCP: MAGICNUM 6382fd51 Dec 13 17:08:32 home ppp[10283]: tun1: LCP: TEXT user-ppp 3.4.2 (built Dec 2 2005) Dec 13 17:08:32 home ppp[10283]: tun1: LCP: deflink: SendTerminateReq(15) state = Req-Sent Dec 13 17:08:32 home ppp[10283]: tun1: LCP: deflink: State change Req-Sent --> Closing Dec 13 17:08:32 home ppp[10283]: tun1: LCP: deflink: RecvConfigNak(15) state = Closing Dec 13 17:08:32 home ppp[10283]: tun1: LCP: deflink: RecvIdent(0) state = Closing Dec 13 17:08:32 home ppp[10283]: tun1: LCP: deflink: RecvIdent: magic 0x6382fd51 is wrong, expecting 0x00000000 Dec 13 17:08:32 home ppp[10283]: tun1: LCP: MAGICNUM 00000000 Dec 13 17:08:32 home ppp[10283]: tun1: LCP: TEXT user-ppp 3.4.2 (built Dec Dec 13 17:08:32 home ppp[10283]: tun1: LCP: deflink: RecvTerminateReq(15) state = Closing Dec 13 17:08:32 home ppp[10283]: tun1: LCP: deflink: SendTerminateAck(15) state = Closing From owner-freebsd-bluetooth@FreeBSD.ORG Tue Dec 13 18:08:12 2005 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 4065D16A423 for ; Tue, 13 Dec 2005 18:08:12 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7675843D6D for ; Tue, 13 Dec 2005 18:07:57 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jBDI7AI19154; Tue, 13 Dec 2005 13:07:12 -0500 Message-ID: <439F0DCC.7090009@savvis.net> Date: Tue, 13 Dec 2005 10:07:08 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitry Dyomin References: <20051213171917.N10381@home.old.com.ua> In-Reply-To: <20051213171917.N10381@home.old.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: BT LAN connection with Symbian phones 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, 13 Dec 2005 18:08:12 -0000 Dmitry, > I'm trying to connect my SE p900 to LAN via rfcomm_pppd. > And I'm stuck upon a pack of 'Magic is same' errors I'm getting on > the following command: > > rfcomm_pppd -S -a 0ld -C 7 -l rfcomm-server -u 1 i'm going to assume that you would like to make your freebsd machine act as a server, i.e. bluetooth access point. if this is the case then you have to run rfcomm_pppd(8) in _server_ mode, i.e. you need to add '-s' (lower case s) to the rfcomm_pppd(8) command like. the '-S' (upper case s) makes rfcomm_pppd(8) to register SP (Serial Port) service in _server_ mode. i'm also going to assume that you are using gnubox application on your p900 phone to dial out. you need to use 2box direct mode. keep in mind that rfcomm_pppd(8) in server mode will not dial out. it will wait for the client to dial in. in other words you have to initiate connection from your phone. also keep in mind that sdpd(8) has to be running, otherwise rfcomm_pppd(8) can not register services and will fail to run. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Dec 13 19:11:06 2005 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 83EB116A428 for ; Tue, 13 Dec 2005 19:11:06 +0000 (GMT) (envelope-from bt@old.com.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id D835743D9B for ; Tue, 13 Dec 2005 19:10:56 +0000 (GMT) (envelope-from bt@old.com.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBDJAcvv027309; Tue, 13 Dec 2005 21:10:38 +0200 (EET) (envelope-from bt@old.com.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 24213-01-8; Tue, 13 Dec 2005 21:10:37 +0200 (EET) Received: from home (82.193.110.225.ipnet.kiev.ua [82.193.110.225]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBDJ9hXi027187 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Dec 2005 21:09:44 +0200 (EET) (envelope-from bt@old.com.ua) Date: Tue, 13 Dec 2005 21:09:46 +0200 (EET) From: Dmitry Dyomin X-X-Sender: old@home.old.com.ua To: Maksim Yevmenkin In-Reply-To: <439F0DCC.7090009@savvis.net> Message-ID: <20051213210626.W12029@home.old.com.ua> References: <20051213171917.N10381@home.old.com.ua> <439F0DCC.7090009@savvis.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: freebsd-bluetooth@freebsd.org Subject: Re: BT LAN connection with Symbian phones 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, 13 Dec 2005 19:11:06 -0000 On Tue, 13 Dec 2005, Maksim Yevmenkin wrote: > i'm going to assume that you would like to make your freebsd machine act as a > server, i.e. bluetooth access point. if this is the case then you have to run > rfcomm_pppd(8) in _server_ mode, i.e. you need to add '-s' (lower case s) to > the rfcomm_pppd(8) command like. the '-S' (upper case s) makes rfcomm_pppd(8) > to register SP (Serial Port) service in _server_ mode. Oh, I thought it's the same as -s, just opens additional service. > > i'm also going to assume that you are using gnubox application on your p900 > phone to dial out. you need to use 2box direct mode. keep in mind that > rfcomm_pppd(8) in server mode will not dial out. it will wait for the client > to dial in. in other words you have to initiate connection from your phone. Oops, I was not even aware of gnubox :) And tried to somehow initiate connection from FreeBSD box before :) Just installed it and finally connected to my FreeBSD. Thank you very much! From owner-freebsd-bluetooth@FreeBSD.ORG Tue Dec 13 19:35:04 2005 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 E86B616A41F for ; Tue, 13 Dec 2005 19:35:04 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8534143D46 for ; Tue, 13 Dec 2005 19:35:04 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jBDJWVI21104; Tue, 13 Dec 2005 14:32:33 -0500 Message-ID: <439F21CD.8040902@savvis.net> Date: Tue, 13 Dec 2005 11:32:29 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitry Dyomin References: <20051213171917.N10381@home.old.com.ua> <439F0DCC.7090009@savvis.net> <20051213210626.W12029@home.old.com.ua> In-Reply-To: <20051213210626.W12029@home.old.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: BT LAN connection with Symbian phones 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, 13 Dec 2005 19:35:05 -0000 Dmitry Dyomin wrote: > On Tue, 13 Dec 2005, Maksim Yevmenkin wrote: > >> i'm going to assume that you would like to make your freebsd machine >> act as a server, i.e. bluetooth access point. if this is the case then >> you have to run rfcomm_pppd(8) in _server_ mode, i.e. you need to add >> '-s' (lower case s) to the rfcomm_pppd(8) command like. the '-S' >> (upper case s) makes rfcomm_pppd(8) to register SP (Serial Port) >> service in _server_ mode. > > Oh, I thought it's the same as -s, just opens additional service. not exactly. rfcomm_pppd(8) can register SP service (in addition to LAN service) to implement so called 'mrouter mode'. you can use it if you do not want to install gnubox application on your phone. in this scenario, you still need to run rfcomm_pppd(8) in _server_ mode, but in order to make the phone to open LAN connection you need to "jump start" it by connecting to the phone SP service. what happens next is that the phone closes the connection and then it "dials" back, looks for SP service on freebsd and connects. at this point rfcomm_pppd(8) start ppp(8) and phone connects. you also need to change your dns server settings to make sure phone can resolve 'wsockhost.mrouter' name (at least nokia 3650 kills ppp connection if it can resolve it). this whole mess can be avoided by just using gnubox. gnubox modifies communication database settings on some symbian phones so it is possible to create access point which will use bluetooth instead of gprs/gsm data. >> i'm also going to assume that you are using gnubox application on your >> p900 phone to dial out. you need to use 2box direct mode. keep in mind >> that rfcomm_pppd(8) in server mode will not dial out. it will wait for >> the client to dial in. in other words you have to initiate connection >> from your phone. > > Oops, I was not even aware of gnubox :) And tried to somehow initiate > connection from FreeBSD box before :) it is possible if you use 'mrouter' mode, which is a big mess, imo. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Tue Dec 13 19:47:21 2005 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 C02BF16A438 for ; Tue, 13 Dec 2005 19:47:21 +0000 (GMT) (envelope-from bt@old.com.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A7D843D94 for ; Tue, 13 Dec 2005 19:47:01 +0000 (GMT) (envelope-from bt@old.com.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBDJktYt028419; Tue, 13 Dec 2005 21:46:55 +0200 (EET) (envelope-from bt@old.com.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 24448-03-3; Tue, 13 Dec 2005 21:46:53 +0200 (EET) Received: from home (82.193.110.225.ipnet.kiev.ua [82.193.110.225]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBDJiWRC028347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 13 Dec 2005 21:44:33 +0200 (EET) (envelope-from bt@old.com.ua) Date: Tue, 13 Dec 2005 21:44:34 +0200 (EET) From: Dmitry Dyomin X-X-Sender: old@home.old.com.ua To: Maksim Yevmenkin In-Reply-To: <439F21CD.8040902@savvis.net> Message-ID: <20051213213826.H12364@home.old.com.ua> References: <20051213171917.N10381@home.old.com.ua> <439F0DCC.7090009@savvis.net> <20051213210626.W12029@home.old.com.ua> <439F21CD.8040902@savvis.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: freebsd-bluetooth@freebsd.org Subject: Re: BT LAN connection with Symbian phones 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, 13 Dec 2005 19:47:22 -0000 On Tue, 13 Dec 2005, Maksim Yevmenkin wrote: > this whole mess can be avoided by just using gnubox. gnubox modifies > communication database settings on some symbian phones so it is possible to > create access point which will use bluetooth instead of gprs/gsm data. Yes, thank you very much for detailed explanation. I can now connect to FreeBSD, but link drops if I try to send any data. I've got this in /var/log/messages: Dec 13 21:36:22 home kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x1, len=124. Queue full Dec 13 21:36:22 home kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x1, len=34. Queue full Dec 13 21:36:23 home kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x1, len=35. Queue full Dec 13 21:36:24 home kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x1, len=35. Queue full After this links dies. Looks similar to unanswered mail in this list: http://lists.freebsd.org/pipermail/freebsd-bluetooth/2005-January/000204.html Any idea what's going wrong? Thank you. From owner-freebsd-bluetooth@FreeBSD.ORG Tue Dec 13 20:23:49 2005 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 C3CEA16A41F for ; Tue, 13 Dec 2005 20:23:49 +0000 (GMT) (envelope-from bt@old.com.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2ED7B43DA1 for ; Tue, 13 Dec 2005 20:23:08 +0000 (GMT) (envelope-from bt@old.com.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBDKN3BB029453 for ; Tue, 13 Dec 2005 22:23:03 +0200 (EET) (envelope-from bt@old.com.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 24598-07-3 for ; Tue, 13 Dec 2005 22:23:02 +0200 (EET) Received: from home (82.193.110.225.ipnet.kiev.ua [82.193.110.225]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBDKMUWJ029410 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 13 Dec 2005 22:22:31 +0200 (EET) (envelope-from bt@old.com.ua) Date: Tue, 13 Dec 2005 22:22:32 +0200 (EET) From: Dmitry Dyomin X-X-Sender: old@home.old.com.ua To: freebsd-bluetooth@freebsd.org In-Reply-To: <20051213213826.H12364@home.old.com.ua> Message-ID: <20051213222041.O12614@home.old.com.ua> References: <20051213171917.N10381@home.old.com.ua> <439F0DCC.7090009@savvis.net> <20051213210626.W12029@home.old.com.ua> <439F21CD.8040902@savvis.net> <20051213213826.H12364@home.old.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at ip.net.ua Subject: Re: BT LAN connection with Symbian phones 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, 13 Dec 2005 20:23:49 -0000 On Tue, 13 Dec 2005, Dmitry Dyomin wrote: > Dec 13 21:36:22 home kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x1, > len=124. Queue full > Sorry, please ignore my previous mail. I had wrong ifaddr in ppp.conf. From owner-freebsd-bluetooth@FreeBSD.ORG Wed Dec 14 20:22:06 2005 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 2DD5316A41F for ; Wed, 14 Dec 2005 20:22:06 +0000 (GMT) (envelope-from bt@old.com.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CF86243D6A for ; Wed, 14 Dec 2005 20:22:03 +0000 (GMT) (envelope-from bt@old.com.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBEKM1hH080066 for ; Wed, 14 Dec 2005 22:22:01 +0200 (EET) (envelope-from bt@old.com.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 43006-02-3 for ; Wed, 14 Dec 2005 22:22:01 +0200 (EET) Received: from home (82.193.110.225.ipnet.kiev.ua [82.193.110.225]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBEKLJdm080029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 14 Dec 2005 22:21:19 +0200 (EET) (envelope-from bt@old.com.ua) Date: Wed, 14 Dec 2005 22:19:48 +0200 (EET) From: Dmitry Dyomin X-X-Sender: old@home.old.com.ua To: freebsd-bluetooth@freebsd.org In-Reply-To: <20051213213826.H12364@home.old.com.ua> Message-ID: <20051214220823.D54073@home.old.com.ua> References: <20051213171917.N10381@home.old.com.ua> <439F0DCC.7090009@savvis.net> <20051213210626.W12029@home.old.com.ua> <439F21CD.8040902@savvis.net> <20051213213826.H12364@home.old.com.ua> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at ip.net.ua Subject: Re: BT LAN connection with Symbian phones 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, 14 Dec 2005 20:22:06 -0000 On Tue, 13 Dec 2005, Dmitry Dyomin wrote: > I've got this in /var/log/messages: > > Dec 13 21:36:22 home kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame 0x1, > len=124. Queue full Unfortunately I have to ask for help with this issue once again. I established the connection without any problems after trying gnubox. I tested it by pointing the phone's opera to the local apache server, I got fine results and actually thought everything was just perfect. Still when I tried to access the page bigger than just 404 apache error page (which I tried first), I got the same 'Queue full' stuff like above. The connection was dropped after these errors. I tried to find the way out myself, but in vain. Is there any way to increase net.bluetooth.hci.sockets.raw.queue_maxlen or whatever is controlling the queue length? Maybe some other workarounds you could suggest? Thank you. From owner-freebsd-bluetooth@FreeBSD.ORG Wed Dec 14 22:19:46 2005 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 5342916A41F for ; Wed, 14 Dec 2005 22:19:46 +0000 (GMT) (envelope-from plunky@rya-online.net) Received: from mail09.svc.cra.dublin.eircom.net (mail09.svc.cra.dublin.eircom.net [159.134.118.25]) by mx1.FreeBSD.org (Postfix) with SMTP id C2FEB43D5E for ; Wed, 14 Dec 2005 22:19:45 +0000 (GMT) (envelope-from plunky@rya-online.net) Received: (qmail 25091 messnum 2880624 invoked from network[83.70.176.191/unknown]); 14 Dec 2005 22:19:43 -0000 Received: from unknown (HELO rya-online.net) (83.70.176.191) by mail09.svc.cra.dublin.eircom.net (qp 25091) with SMTP; 14 Dec 2005 22:19:43 -0000 Received: (nullmailer pid 1454 invoked by uid 1000); Wed, 14 Dec 2005 22:19:20 -0000 Date: Wed, 14 Dec 2005 22:19:19 +0000 (GMT) To: freebsd-bluetooth@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Message-Id: <1134598760.901248.1323.nullmailer@galant.ukfsn.org> From: Iain Hibbert Subject: bt3cfw(8) 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, 14 Dec 2005 22:19:46 -0000 Hi, I have a question - I've been writing some bluetooth protocol code for NetBSD and one of the devices I have is the 3Com PC Card so I have a driver for that based on the FreeBSD and BlueZ drivers. Regarding the firmware copyright inclusion issue, I was wondering if 3Com had ever been asked for permission to redistribute the firmware code with a BSD system, or if it was just taken that they would not? iain From owner-freebsd-bluetooth@FreeBSD.ORG Wed Dec 14 23:30:50 2005 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 F1F5716A41F for ; Wed, 14 Dec 2005 23:30:50 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1336A43D72 for ; Wed, 14 Dec 2005 23:30:43 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jBENToI23723; Wed, 14 Dec 2005 18:29:51 -0500 Message-ID: <43A0AAE6.30203@savvis.net> Date: Wed, 14 Dec 2005 15:29:42 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Dmitry Dyomin References: <20051213171917.N10381@home.old.com.ua> <439F0DCC.7090009@savvis.net> <20051213210626.W12029@home.old.com.ua> <439F21CD.8040902@savvis.net> <20051213213826.H12364@home.old.com.ua> <20051214220823.D54073@home.old.com.ua> In-Reply-To: <20051214220823.D54073@home.old.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: BT LAN connection with Symbian phones 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, 14 Dec 2005 23:30:51 -0000 Dmitry Dyomin wrote: > On Tue, 13 Dec 2005, Dmitry Dyomin wrote: > >> I've got this in /var/log/messages: >> >> Dec 13 21:36:22 home kernel: ng_ubt_rcvdata: ubt0 - Dropping HCI frame >> 0x1, len=124. Queue full > > > Unfortunately I have to ask for help with this issue once again. > > I established the connection without any problems after trying gnubox. > I tested it by pointing the phone's opera to the local apache server, I got > fine results and actually thought everything was just perfect. > > Still when I tried to access the page bigger than just 404 apache error > page (which I tried first), I got the same 'Queue full' stuff like above. > The connection was dropped after these errors. how fast is you freebsd machine? are you running with debugging options enabled (i.e. witness etc.)? > I tried to find the way out myself, but in vain. > > Is there any way to increase net.bluetooth.hci.sockets.raw.queue_maxlen or > whatever is controlling the queue length? > Maybe some other workarounds you could suggest? # ngctl msg ubt0: set_qlen "{ queue=2 qlen=50 }" # ngctl status ubt0: queue=1 means CMD (command) queue queue=2 means ACL queue queue=3 means SCO queue thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Wed Dec 14 23:33:20 2005 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 3505C16A41F for ; Wed, 14 Dec 2005 23:33:20 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from ismybrain.com (ismybrain.com [64.246.42.25]) by mx1.FreeBSD.org (Postfix) with ESMTP id CC6CA43D70 for ; Wed, 14 Dec 2005 23:33:18 +0000 (GMT) (envelope-from maksim.yevmenkin@savvis.net) Received: from [10.254.186.111] (localhost.localdomain [127.0.0.1]) by ismybrain.com (8.11.6/8.11.6) with ESMTP id jBENWqI23837; Wed, 14 Dec 2005 18:32:53 -0500 Message-ID: <43A0AB9E.7060808@savvis.net> Date: Wed, 14 Dec 2005 15:32:46 -0800 From: Maksim Yevmenkin User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050404) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Iain Hibbert References: <1134598760.901248.1323.nullmailer@galant.ukfsn.org> In-Reply-To: <1134598760.901248.1323.nullmailer@galant.ukfsn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bluetooth@freebsd.org Subject: Re: bt3cfw(8) 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, 14 Dec 2005 23:33:20 -0000 Iain, > I have a question - I've been writing some bluetooth protocol code for > NetBSD and one of the devices I have is the 3Com PC Card so I have a > driver for that based on the FreeBSD and BlueZ drivers. > > Regarding the firmware copyright inclusion issue, I was wondering if 3Com > had ever been asked for permission to redistribute the firmware code with > a BSD system, or if it was just taken that they would not? yes, someone (i think it was Julian Elischer) asked 3Com about it. as far as i know, it went nowhere. thanks, max From owner-freebsd-bluetooth@FreeBSD.ORG Thu Dec 15 08:32:23 2005 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 9188E16A41F for ; Thu, 15 Dec 2005 08:32:23 +0000 (GMT) (envelope-from bt@old.com.ua) Received: from tigra.ip.net.ua (tigra.ip.net.ua [82.193.96.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id CBB5943D73 for ; Thu, 15 Dec 2005 08:32:19 +0000 (GMT) (envelope-from bt@old.com.ua) Received: from localhost (rocky.ip.net.ua [82.193.96.2]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBF8WCIn005729; Thu, 15 Dec 2005 10:32:12 +0200 (EET) (envelope-from bt@old.com.ua) Received: from tigra.ip.net.ua ([82.193.96.10]) by localhost (rocky.ipnet [82.193.96.2]) (amavisd-new, port 10024) with LMTP id 54290-02-3; Thu, 15 Dec 2005 10:32:12 +0200 (EET) Received: from home (82.193.110.225.ipnet.kiev.ua [82.193.110.225]) by tigra.ip.net.ua (8.12.11/8.12.11) with ESMTP id jBF8SiXk005620 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Dec 2005 10:28:45 +0200 (EET) (envelope-from bt@old.com.ua) Date: Thu, 15 Dec 2005 10:28:45 +0200 (EET) From: Dmitry Dyomin X-X-Sender: old@home.old.com.ua To: Maksim Yevmenkin In-Reply-To: <43A0AAE6.30203@savvis.net> Message-ID: <20051215102658.I57298@home.old.com.ua> References: <20051213171917.N10381@home.old.com.ua> <439F0DCC.7090009@savvis.net> <20051213210626.W12029@home.old.com.ua> <439F21CD.8040902@savvis.net> <20051213213826.H12364@home.old.com.ua> <20051214220823.D54073@home.old.com.ua> <43A0AAE6.30203@savvis.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: by amavisd-new at ip.net.ua Cc: freebsd-bluetooth@freebsd.org Subject: Re: BT LAN connection with Symbian phones 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, 15 Dec 2005 08:32:23 -0000 On Wed, 14 Dec 2005, Maksim Yevmenkin wrote: >> Still when I tried to access the page bigger than just 404 apache error >> page (which I tried first), I got the same 'Queue full' stuff like above. >> The connection was dropped after these errors. > > how fast is you freebsd machine? are you running with debugging options > enabled (i.e. witness etc.)? CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (3084.39-MHz 686-class CPU) No debugging enabled. >> Is there any way to increase net.bluetooth.hci.sockets.raw.queue_maxlen or >> whatever is controlling the queue length? > > # ngctl msg ubt0: set_qlen "{ queue=2 qlen=50 }" > # ngctl status ubt0: Thank you very much! This solved my issue.