Delivery-Date: Tue, 12 Aug 2014 05:16:38 -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 D469D1E0A50;
	Tue, 12 Aug 2014 05:16:36 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id DAA6F303B0;
	Tue, 12 Aug 2014 09:16:32 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 28AF330286
 for <tor-talk@lists.torproject.org>; Tue, 12 Aug 2014 09:16:29 +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 UO1UxP6DOp_D for <tor-talk@lists.torproject.org>;
 Tue, 12 Aug 2014 09:16:29 +0000 (UTC)
Received: from mail.poivron.org (poivron.org [91.194.60.101])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.poivron.org",
 Issuer "StartCom Class 2 Primary Intermediate Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id EB9A0301F5
 for <tor-talk@lists.torproject.org>; Tue, 12 Aug 2014 09:16:28 +0000 (UTC)
Received: from [127.0.0.1] (localhost [127.0.0.1]) with ESMTPSA id 0B567C00733
Date: Tue, 12 Aug 2014 09:16:19 +0000
From: Lunar <lunar@torproject.org>
To: tor-talk@lists.torproject.org
Message-ID: <20140812091619.GG10859@localhost.localdomain>
Mail-Followup-To: tor-talk@lists.torproject.org
References: <53E31EFE.3010603@rawbw.com>
MIME-Version: 1.0
In-Reply-To: <53E31EFE.3010603@rawbw.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: Re: [tor-talk] Why tor doesn't support UDP?
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: multipart/mixed; boundary="===============5905368843026725731=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


--===============5905368843026725731==
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="doKZ0ri6bHmN2Q5y"
Content-Disposition: inline


--doKZ0ri6bHmN2Q5y
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Yuri:
> It is well known that tor only supports DNS UDP requests, and not
> other UDP.
>=20
> Tor could relay UDP through the same path as TCP. And the chosen exit
> node could act as a UDP gateway, much like regular routers relay UDP
> packets from different LAN hosts. Routers substitute source port of
> UDP packets and later map back the ip/port in response packets. It
> could be easily imagined how tor could do just the same.
> When I use the virtual machine connected to network through the tor,
> only http apps work, and all UDP apps fail. Even skype is unable to
> connect.
>=20
> So what is the reason that UDP isn't supported?

There are many reasons. I guess patches would be happily discussed if
you had some. SOCKS5 supports UDP, TransPort could be made to support
UDP too. Then there's circuit handling and session tracking=C2=A0=E2=80=94 =
the
connection is never opened or closed with UDP.

But then, the underlying connections between relays are still going to
be TCP. Previous research on switching to datagram designs:
http://static.usenix.org/event/sec09/tech/full_papers/reardon.pdf
https://research.torproject.org/techreports/datagram-comparison-2011-11-07.=
pdf
https://research.torproject.org/techreports/libutp-2013-10-30.pdf

--=20
Lunar                                             <lunar@torproject.org>

--doKZ0ri6bHmN2Q5y
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJT6dtjAAoJEEgU3sIrMHw8wD4P/Rdcf/5SrRtLqzyD3GJKxqB6
+N85eQ9TkT41ATB6Ii1Fc+PD3IWlm/afdFeSHX+irkl3k6v9qcIeI/WJ2mMqJ4YC
IhZL54tXPIuQpAwMEeNfYRaxahlvKbFOg9rcyt32+Z/vnZkuDj939NRSEBLmBihd
3fwdf3iWhaijForiwzdz1g0Q1t6GcC1YrdLqAjfdoR2K9Grq10MWL65GceLkhgG3
qWAQluAgYhF0EMn0hMc/cesLvHQjb5gcX3mRrMwu9PZMJzxrBXGhVTt+LUQ/wExs
DXiIqFHD4HWRvzTMCl2sjm8PE9DKBpP+qFYj4BRQlDRgIPFa9nQUWZHNNvS5YPab
VqZEJQ8PJA+Wch7dgO23V3zQ5Itk7R3nl2vELXMFv45D2vSStsvItuyCMSP5WfvR
H0pFob2sS8nSd85Gf4vSLQZlJWeIW1w5Eri4fI2oaAbSIXkedQvWwAdxkVtDe8QE
bChBdVLMGxdNGEGiTGlMK76HHyEGEdYN7/zu0pIoclnjMLhsEWxjAdxFJXlM30F2
cBldVehgyCHqnJwmYTb9LCJH4oVG1+m47Sx/NsYz8NlVSjG9yvb1D7G6mcwLQ1SD
bGzLQ9buwcmT6zOIX5GLsVrM6GrGr1gnO5urqAYfaEDblR4q/8dboIshPGqpsQ3Z
1ZIlRsvpwECR07EAKOg9
=4FXC
-----END PGP SIGNATURE-----

--doKZ0ri6bHmN2Q5y--

--===============5905368843026725731==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============5905368843026725731==--

