Delivery-Date: Mon, 27 Oct 2014 13:00:51 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID
	autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 557321E0BBF;
	Mon, 27 Oct 2014 13:00:50 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 0FE682F19C;
	Mon, 27 Oct 2014 17:00:45 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 7B7302ED72
 for <tor-talk@lists.torproject.org>; Mon, 27 Oct 2014 17:00:41 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id rwyNEtCIjM2j for <tor-talk@lists.torproject.org>;
 Mon, 27 Oct 2014 17:00:41 +0000 (UTC)
Received: from mail-vc0-x231.google.com (mail-vc0-x231.google.com
 [IPv6:2607:f8b0:400c:c03::231])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 52A682DA91
 for <tor-talk@lists.torproject.org>; Mon, 27 Oct 2014 17:00:41 +0000 (UTC)
Received: by mail-vc0-f177.google.com with SMTP id hq11so2593648vcb.36
 for <tor-talk@lists.torproject.org>; Mon, 27 Oct 2014 10:00:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=x0BNp+p5NzD46CU0Qm86vg3fHQES2IL+Ij+PCJAQ94o=;
 b=gtKISMhJYKNayK+DxhO3LujakgArj9XroBXfVnFoc/4fUSAwtyu0SN6xn0hsvG9C1F
 u0/Mf48BoRW9A8VWtgjIjqnxyaRWO9R2eaDwP63dZlVLm5d1GXyZxAWZvLmUsht4ub59
 YpD4hsAAM+8AntLqkyMqPBovP1P/bnRj7wvnJzqRcJ5iTaLGc6GNph07nViPqFY7gFtV
 H+cOUHYr6RQawDgOtGVqRTh4Xyn6DgcMQkx0RLTlnyBOcE8KzxRB7mWKHV166/SxyUiq
 bHy459gvR1gnTVrjT3qQky19Sn1TlpCSSS4IPAhmAaeKvdasDUN0rbL7xzwNDXAEYEzb
 MwoQ==
MIME-Version: 1.0
X-Received: by 10.52.37.18 with SMTP id u18mr7278385vdj.17.1414429238672; Mon,
 27 Oct 2014 10:00:38 -0700 (PDT)
Received: by 10.221.64.74 with HTTP; Mon, 27 Oct 2014 10:00:38 -0700 (PDT)
In-Reply-To: <1414128957.1286791.182745789.27EF00B3@webmail.messagingengine.com>
References: <1414128957.1286791.182745789.27EF00B3@webmail.messagingengine.com>
Date: Mon, 27 Oct 2014 13:00:38 -0400
Message-ID: <CAD2Ti2_DYRJZ-+sg1Zgwp0cuU6g_q-aZF+z9ets0=_kv6am-1Q@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Cc: ambrop7@gmail.com
Subject: Re: [tor-talk] using UDPGW and tun2socks over Tor
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On Fri, Oct 24, 2014 at 1:35 AM, Nathan Freitas <nathan@freitas.net> wrote:
> Is there any reason we shouldn't consider supporting UDP over Tor with
> Orbot, by tunneling the packets using the combination of badvpn's
> tun2socks and udpgw ("udp gateway") feature?

There's no reason raw IP itself (any/none of its numbered protocols)
shouldn't / couldn't be transported over Tor using OpnVPN (at least
until Tor itself is extended as such).

> This has come up as we are
> implementing the Android VPNService, and discovered how easy to
> implement and well performing the badvpn UDP tunneling capability is.

> This means we can support SIP calling over Tor, video conference and
> streaming, among other applications...

> https://code.google.com/p/badvpn/
> https://code.google.com/p/badvpn/wiki/tun2socks
> https://github.com/ambrop72/badvpn

... Not necessarily, unless you're statically mapping all the people
(IP's) you want to communicate with beforehand, (which you can't with
random unknown participants ie: Bittorrent, or people on dynamic or
mobile), you're currently constrained by address collisions:
- Trying to pack the entire IPv4 address space you might want to
'call' into your tiny 10.0.0.0/24 adapter space. Same for put entire IPv6
space into your private IPv6/48 adapter space.
- Similarly what you're going to do when Tor moves to wider than
80bit onion addressing which currently fits nicely into a private IPv6/48.
(Need a secure IPv6<->onion address mapping layer pushed into a
DHT/blockchain or just resorting to trusting some volunteer run in-net
lookup service.)

edit: Just noticed badvpn's mention of pushing a *VM* on a 10 address
through socks with this, at least for TCP, which is simpler. As opposed
to pushing any app on the raw iron through a *VPN* which could be
constrained as above. Left this anyway for thought in related things.

> It does mean that someone would have to operate the
> gateway/infrastructure portion of udpgw at a capacity necessary to
> handle all udp streaming traffic sent for all Orbot users, but I would
> consider that to be feasible. Perhaps udpgw instances can be run along
> side all Tor exit nodes?

Read below thread flowing on both tor-talk and tor-relays, flows over
May and June, with better specification/answers in later posts.
https://lists.torproject.org/pipermail/tor-relays/2014-May/004516.html
Subject: Ops request: Deploy OpenVPN terminators
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

