From owner-freebsd-bluetooth@FreeBSD.ORG Fri Dec 28 12:05:34 2007 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 EC46816A418 for ; Fri, 28 Dec 2007 12:05:34 +0000 (UTC) (envelope-from frederic.praca@freebsd-fr.org) Received: from smtp8-g19.free.fr (smtp8-g19.free.fr [212.27.42.65]) by mx1.freebsd.org (Postfix) with ESMTP id 7E7B913C455 for ; Fri, 28 Dec 2007 12:05:34 +0000 (UTC) (envelope-from frederic.praca@freebsd-fr.org) Received: from smtp8-g19.free.fr (localhost [127.0.0.1]) by smtp8-g19.free.fr (Postfix) with ESMTP id 1CDD117F572; Fri, 28 Dec 2007 13:05:33 +0100 (CET) Received: from imp6-g19.free.fr (imp6-g19.free.fr [212.27.42.6]) by smtp8-g19.free.fr (Postfix) with ESMTP id 0EC5017F566; Fri, 28 Dec 2007 13:05:32 +0100 (CET) Received: by imp6-g19.free.fr (Postfix, from userid 33) id C932D438F; Fri, 28 Dec 2007 13:05:32 +0100 (CET) Received: from coruscant.dnsalias.net (coruscant.dnsalias.net [88.169.125.217]) by imp.free.fr (IMP) with HTTP for ; Fri, 28 Dec 2007 13:05:32 +0100 Message-ID: <1198843532.4774e68c9a6cb@imp.free.fr> Date: Fri, 28 Dec 2007 13:05:32 +0100 From: =?iso-8859-1?b?RnLpZOlyaWM=?= PRACA To: Maksim Yevmenkin References: <20071227225845.6c49ec38@localhost> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.2.8 X-Originating-IP: 88.169.125.217 Cc: freebsd-bluetooth@freebsd.org Subject: Re: DUN server on Freebsd 6 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: Fri, 28 Dec 2007 12:05:35 -0000 Selon Maksim Yevmenkin : > hello, > > > I want to do what described here (http://www.fenrus.org/tomtom/ ) with > > my FreeBSD station. I managed to change my USB dongle bluetooth class > > type into GSM class type but rfcomm-pppd declares itself to sdpd as LAN > > Access Using PPP not as DUN. The problem is that Tomtom just look for a > > GSM bluetooth device with DUN capability. > > > > Anybody has any idea on this problem ? > > the problem is that tomtom assumes that there is a modem on the other > end of bluetooth link. clearly this feature was designed to work with > cell phones. basically, cell phone acts as a bluetooth modem in this > case. in the article you have referenced, the author simply uses chat > script to trick tomtom into believing that it talks to the modem. Ok, that's what I understood. > rfcomm_pppd(8) only registers LAN service (and SP for weird nokia > mrouter) but it does not know anything about DUN, because it was never > supposed to do it. in any case, if you have coding skills, it should Well, I should have as it's my job ;-) > be trivial to teach rfcomm_pppd(8) to register DUN service as well. I'll give it a try and maybe provide a patch. > just provide another option to rfcomm_pppd(8) and use SP service as an > example. to fake modem you will need to use ppp(8) chat script and > 'enable force-scripts' option. Thanks a lot for your quick answer. I still have another option which is to patch the Tomtom itself :D Seems to be less trivial as I have to go deep in the Tomtom linux code ;-) > thanks, You're welcome > max Fred