From owner-freebsd-bluetooth@FreeBSD.ORG Tue Jun 8 00:49:54 2010 Return-Path: Delivered-To: bluetooth@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FD681065670 for ; Tue, 8 Jun 2010 00:49:54 +0000 (UTC) (envelope-from maksim.yevmenkin@gmail.com) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 52E588FC19 for ; Tue, 8 Jun 2010 00:49:54 +0000 (UTC) Received: by pxi7 with SMTP id 7so1752567pxi.13 for ; Mon, 07 Jun 2010 17:49:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=SOUeHoqPlJKfcOhskYj6alQ9zBAbdcc/2QXSCLjPatI=; b=rFdFgcFRfYjqRId/CaZpRtRYbhhwNcD3Uex1N2hazv60IZdj4Dv4CMuyDWrJ3slm4/ 3hamgoWt7lXUSu5VxPgbFc4Iso8+PvTlZLl0XFZ1SXrRrd5CXOHVvteGcgUC8VPmc8by amYtOaRiloHKz0+82nddaYO0Sj+DZ0iRXLkRg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=e4Vgl0J0bjRRVg262WGXQoXTZS8Cayar22t9jJDpvGbC6DUqPgdjSfZT8NvFUvXxdU Glw+kH0MR9uE5gFP67LdQybdHNaRAwu7zRZw3JN08e5d8aNF8pUSTEUt4tg8yuohpLlF muq4+YOm6G5GmgEcwahOyALRzQW5XBpJAeWMA= MIME-Version: 1.0 Received: by 10.141.139.11 with SMTP id r11mr8352618rvn.61.1275958193529; Mon, 07 Jun 2010 17:49:53 -0700 (PDT) Received: by 10.140.142.13 with HTTP; Mon, 7 Jun 2010 17:49:53 -0700 (PDT) In-Reply-To: <4C0957FE.1030206@aldan.algebra.com> References: <4C081B71.30801@aldan.algebra.com> <4C0957FE.1030206@aldan.algebra.com> Date: Mon, 7 Jun 2010 17:49:53 -0700 Message-ID: From: Maksim Yevmenkin To: "Mikhail T." Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: bluetooth@freebsd.org Subject: Re: NAT over bluetooth for mobile devices 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, 08 Jun 2010 00:49:54 -0000 On Fri, Jun 4, 2010 at 12:46 PM, Mikhail T. wro= te: > 04.06.2010 13:43, Maksim Yevmenkin =D0=BD=D0=B0=D0=BF=D0=B8=D1=81=D0=B0= =D0=B2(=D0=BB=D0=B0): > >> i don't really think its has to be that complicated. all we really >> want to do here is to turn mobile device (i.e. phone) into a >> "gateway". that is mobile device needs to be multihomed (local >> network, and, cellular data network). local network can be bluetooth, >> wifi or even plain usb/serial cable. for bluetooth we can use lan or >> pan profiles. wifi, obviously, "just works" most of the time. > > Do those profiles (almost) always exist on otherwise suitable devices? Ev= en > if available from the manufacturer, they may be disabled by the service > provider... any particular device may or may not implement any particular profile. of course, as you have pointed out, service provider (i.e. network operator) may request device manufacturer to disable certain features. > It may be simpler if the communication was over some other, widely > available, profile. A customized daemon (perhaps even a patched-up ppp) well, that's the point. standard bluetooth profiles that provide local network connectivity are pretty much dun, lan and panu/nap/gn. those are likely to be disabled. > would then run on the computer behind the tun-interface, relaying > network-requests over the bluetooth (or cable) link for a piece of softwa= re > on the device to turn into network packets, which would appear to the res= t > of the world as originating from the device itself. like i said, i don't think it matters. data connection is always originated from the device. i don't think service provider can actually tell whether or not device is used as 'modem' or as a 'gateway'. hence the request to completely disable certain bluetooth services. >> the trick is the second part, i.e. "natd" part that runs on the mobile >> device. > > Absolutely... I don't have the slightest idea, where to even begin such a > thing... mobile device sdk :) blackberry actually has java me at the lowest level. it supposedly confirms to midp and cldc. how bad can it be really? :) the other problem is that such application would probably never be allowed by service providers and/or device manufacturer :) thanks, max