From owner-freebsd-bluetooth@FreeBSD.ORG Wed Mar 5 22:08:37 2008 Return-Path: Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AFA841065674 for ; Wed, 5 Mar 2008 22:08:37 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by mx1.freebsd.org (Postfix) with ESMTP id 3FBAF8FC29 for ; Wed, 5 Mar 2008 22:08:37 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: by fg-out-1718.google.com with SMTP id 16so1559164fgg.35 for ; Wed, 05 Mar 2008 14:08:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=xtiH6yt0ked5EfN/5cKq1sbIwQdE5AFFnEeM/tBFOAs=; b=WAO6osInH6fSOTzPVtLyD5/LeoETZyuA70b1+zszY7aQ+WoCHYyU6ka1C1T4+ScUspNqBPkpqo3NE/cC2lrPAeGHRxSlr45xVIV/GvCoxEeCgdxUKM1dJsSeINDbf3Xczxk3eu8hD7aZ+0w4zLiBgfPrOX0cutVqK241X78UAoI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BAdvOc4mQ9hZW7QiIjbNPkmESFiPy1DXnZiZM2A4pvAjfVFrPAiDTYLpJfm65r0KcVasf9LbB9jtD3rssN8XOz9xZFDoPHwQFvDVJK8/7KOipqUwbwFNcCwyOwziJr47iKUjXKyTGVkkjqTjsg9yzanoDm9S81vwc6Kz+VisLCo= Received: by 10.86.97.7 with SMTP id u7mr3628730fgb.54.1204754915938; Wed, 05 Mar 2008 14:08:35 -0800 (PST) Received: by 10.86.23.12 with HTTP; Wed, 5 Mar 2008 14:08:35 -0800 (PST) Message-ID: Date: Wed, 5 Mar 2008 14:08:35 -0800 From: "Maksim Yevmenkin" To: "eng. Anatoli Marinov" In-Reply-To: <335adcd30803051345v2cd6952ak5ba0dc11577b69ab@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <335adcd30803050335k162b5014kac786a2442f06e10@mail.gmail.com> <335adcd30803051345v2cd6952ak5ba0dc11577b69ab@mail.gmail.com> Cc: "freebsd-bluetooth@freebsd.org" Subject: Re: DUN over bluethoot 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, 05 Mar 2008 22:08:38 -0000 On Wed, Mar 5, 2008 at 1:45 PM, eng. Anatoli Marinov wrote: > I've applied the patch and I think now I am one step forward but still > does not have whole connectivity. > > The dump now is: [....] this dump is not very useful to me. it does not show anything interesting except the fact that RFCOMM connection was established and there were a few data packets going in both directions. you need to send me a binary dump or at least have hcidump print content of the each RFCOMM data packet (-x and -a switches). did you adjust your ppp.conf default section to include chat script? basically, in DUN profile the client will send few AT commands on which PPP should respond with OK. finally the client will send ATDTxxxx, i.e. will try to dial a number to which PPP should respond CONNECT. after this PPP client will start talking PPP. in any case, since there was an RFCOMM connection, you should increase debug level in ppp.conf and check /var/log/ppp.log to see what client has actually tried to send. i suspect that you did not adjust your chat script properly and the client simply gives up because it thinks there is no modem on the other end. > Maybe I have to try without DUN I found something called PAN it is > located here http://maemo.org/community/wiki/HOWTO-BluetoothNetworking/ > and will try it tomorrow PAN is not supported in FreeBSD at the moment. if you can't get DUN to work, you need to use LAN profile. like i said before, LAN profile assumes null-modem type connection, i.e. both client and server start talking PPP as soon as RFCOMM connection is established. > Will inform you with my progress. Please if you find something wrong > in the dump please tell me. BTW, http://maemo.org/community/wiki/howto-bluetoothnetworking-dun-ppp/ talks about /etc/ppp/peers/at-command.pl script which does exactly what i've trying to explain to you. it basically responds OK to any string that starts with AT, and CONNECT to any string that starts with ATD. you need to do similar thing with chat script inside ppp.conf. thanks, max p.s. please keep "freebsd-bluetooth@freebsd.org" in cc list