From owner-freebsd-bluetooth@FreeBSD.ORG Fri Jun 4 19:46:08 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 0067C1065677 for ; Fri, 4 Jun 2010 19:46:08 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from mail2.timeinc.net (mail2.timeinc.net [64.236.74.30]) by mx1.freebsd.org (Postfix) with ESMTP id B5D7A8FC22 for ; Fri, 4 Jun 2010 19:46:07 +0000 (UTC) Received: from mail.timeinc.net (mail.timeinc.net [64.12.55.166]) by mail2.timeinc.net (8.13.8/8.13.8) with ESMTP id o54Jk6cD000538 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Jun 2010 15:46:06 -0400 Received: from ws-mteterin.dev.pathfinder.com (ws-mteterin.dev.pathfinder.com [209.251.223.173]) by mail.timeinc.net (8.13.8/8.13.8) with SMTP id o54Jk6A3024014; Fri, 4 Jun 2010 15:46:06 -0400 Message-ID: <4C0957FE.1030206@aldan.algebra.com> Date: Fri, 04 Jun 2010 15:46:06 -0400 From: "Mikhail T." Organization: Virtual Estates, Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; uk; rv:1.9.1.9) Gecko/20100317 Lightning/1.0b1 Thunderbird/3.0.4 MIME-Version: 1.0 To: Maksim Yevmenkin References: <4C081B71.30801@aldan.algebra.com> In-Reply-To: X-Mailman-Approved-At: Fri, 04 Jun 2010 20:16:46 +0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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: Fri, 04 Jun 2010 19:46:08 -0000 04.06.2010 13:43, Maksim Yevmenkin ???????(??): > 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? Even if available from the manufacturer, they may be disabled by the service provider... It may be simpler if the communication was over some other, widely available, profile. A customized daemon (perhaps even a patched-up ppp) would then run on the computer behind the tun-interface, relaying network-requests over the bluetooth (or cable) link for a piece of software on the device to turn into network packets, which would appear to the rest of the world as originating from the device itself. > 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... -mi