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