Delivery-Date: Fri, 24 Oct 2014 01:36:12 -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.8 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD,UNPARSEABLE_RELAY 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 374291E0B81;
	Fri, 24 Oct 2014 01:36:10 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 54A873105F;
	Fri, 24 Oct 2014 05:36:06 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3DEEF30939
 for <tor-talk@lists.torproject.org>; Fri, 24 Oct 2014 05:36:02 +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 mOa2jC0RycEw for <tor-talk@lists.torproject.org>;
 Fri, 24 Oct 2014 05:36:02 +0000 (UTC)
Received: from gil.mayfirst.org (gil.mayfirst.org [216.66.23.48])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 2145D2EFE7
 for <tor-talk@lists.torproject.org>; Fri, 24 Oct 2014 05:36:02 +0000 (UTC)
Received: from gil.mayfirst.org (localhost [127.0.0.1])
 by gil.mayfirst.org (Postfix) with ESMTP id A43C85E6A
 for <tor-talk@lists.torproject.org>; Fri, 24 Oct 2014 01:35:58 -0400 (EDT)
Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender:
 nathanfreitas@gil.mayfirst.org) with ESMTPSA id 89F105E52
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailauth.nyi.internal (Postfix) with ESMTP id BF6ED20923
 for <tor-talk@lists.torproject.org>; Fri, 24 Oct 2014 01:35:57 -0400 (EDT)
Received: from web2 ([10.202.2.212])
 by compute1.internal (MEProxy); Fri, 24 Oct 2014 01:35:57 -0400
Received: by web2.nyi.internal (Postfix, from userid 99)
 id 961B15402B3; Fri, 24 Oct 2014 01:35:57 -0400 (EDT)
Message-Id: <1414128957.1286791.182745789.27EF00B3@webmail.messagingengine.com>
X-Sasl-Enc: /y9AnQ+i9iJ5Ct9hjBpT/2EYeXFAu6jQJwkCzAIR/rgi 1414128957
From: Nathan Freitas <nathan@freitas.net>
To: tor-talk@lists.torproject.org
MIME-Version: 1.0
X-Mailer: MessagingEngine.com Webmail Interface - ajax-c1967a3d
Date: Fri, 24 Oct 2014 01:35:57 -0400
X-Virus-Scanned: ClamAV using ClamSMTP
Subject: [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>


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? 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.

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?

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

+n

-- 
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

