Delivery-Date: Tue, 28 Apr 2015 22:52:41 -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.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD
	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 2C37D1E0E83
	for <archiver@seul.org>; Tue, 28 Apr 2015 22:52:40 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 0E47E34522;
	Wed, 29 Apr 2015 02:52:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A648E34522
 for <tor-talk@lists.torproject.org>; Wed, 29 Apr 2015 02:52:32 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
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 j9yAPVF4J8J3 for <tor-talk@lists.torproject.org>;
 Wed, 29 Apr 2015 02:52:32 +0000 (UTC)
Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com
 [IPv6:2a00:1450:4010:c04::232])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 49BD033B12
 for <tor-talk@lists.torproject.org>; Wed, 29 Apr 2015 02:52:32 +0000 (UTC)
Received: by lbbzk7 with SMTP id zk7so10391421lbb.0
 for <tor-talk@lists.torproject.org>; Tue, 28 Apr 2015 19:52:29 -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
 :content-type; bh=PIunCCP0UagpeT6uPbKjzMkZa1L2roVl7v3iBaRxRJI=;
 b=KmHyAZk4HwUInzXI0G9dGJt2NTBmpDg2FMzBVdNpSggwMAicf4x0lGqrGy9KLS9ToT
 zoBjCrgUoLdsTdZQH2ISvwvmduhnqVvRzitB4hHcLltN1ZN/YNtZrvsgAiqDvA3euzmL
 JSIldwy3xCyKb2/sIlKgzBXvpBhGxh98546g87jao/36a8NltJProv5O62UTK8LQ6L5o
 x7KNposcauYikud4PYKVrJgBeKMJY60gL/rh6ElTc5HuZ61HdS8e1zlpuWm4oJDLhtOX
 05y+xqUFuhAfJEO++CLrN0E5aBdJXmC5BdKBU34/rdryoG7GhUxAuEWK07hleNbvt8V6
 iiIw==
MIME-Version: 1.0
X-Received: by 10.152.170.136 with SMTP id am8mr17537587lac.102.1430275949116; 
 Tue, 28 Apr 2015 19:52:29 -0700 (PDT)
Received: by 10.25.90.65 with HTTP; Tue, 28 Apr 2015 19:52:28 -0700 (PDT)
In-Reply-To: <97ebff92c1da78d9a8268ba4461d1fca@cryptolab.net>
References: <c10fc6c80a006ef3410fdbe2bb68323e@466buer.de>
 <553CE16D.1010106@autistici.org>
 <e2350d34fb959783cd986017027df2bb@466buer.de>
 <553D5F81.8010003@rawbw.com>
 <97ebff92c1da78d9a8268ba4461d1fca@cryptolab.net>
Date: Tue, 28 Apr 2015 19:52:28 -0700
Message-ID: <CAJVRA1T_3nse2qZaZCCxky8Q4_xGyE6d997qwQbjcb8pFPAvuw@mail.gmail.com>
From: coderman <coderman@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] hiddden service on openwrt
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 4/27/15, Griffin Boyce <griffin@cryptolab.net> wrote:
> ...
>    I've run hidden services successfully on TP-Link WDR-4300 -- they have
> 8mb of flash (storage), 128mb ram, and 2 usb ports.  With an added flash
> drive it's basically a small server.  For the size-conscious, you can
> also run a hidden service on a TP-Link 3040, but it gets a lot trickier
> as you only have 32mb of ram to work with.

8mb flash, 32mb ram is probably the lower bound for a useful Tor
client / hs host device. remember to omit geoip from the tor pkg :)



> ... For all sorts of reasons I
> wouldn't recommend being a bridge/middle/exit node while running a
> hidden service (especially on a router, which is already extremely
> resource-constrained).

i would state this as: never use these devices as relay.
 and only as bridge if not already running hidden svc,
  and not more than a few distinct onions per device.


a longer hidden service performance discussion spans:

"Hidden Services are in a peculiar situation. While they see a loyal
fan-base, there are no dedicated Tor developers to take care of them."
 - https://blog.torproject.org/blog/hidden-services-need-some-love

"[tor-dev] Hidden Service Scaling"
 - https://lists.torproject.org/pipermail/tor-dev/2013-October/thread.html#5556

"[tor-talk] Hidden Services - how to implement something like Round Robin DNS?"
 - https://lists.torproject.org/pipermail/tor-talk/2014-September/thread.html#34951

"Rumors that hidden services have trouble scaling to 100 concurrent connections"
 - https://bugs.torproject.org/8902
  https://trac.torproject.org/projects/tor/attachment/ticket/8902/torhs-pyloris-nov9.tgz


finally, consider:
Increase NumEntryGuards to 3 or 5
 and Increase MaxClientCircuitsPending 300



>    OpenWRT and Commotion both ...

you'll want to squeeze the best reduction across toolchain (uClibc
opts) and application (for example, ConstrainedSockets opts) even
system tuning (ulimits, /proc). some of this is on the Torouter page:
https://trac.torproject.org/projects/tor/wiki/doc/Torouter the rest on
the list archives...

in general terms, there is not a good set of measurements for Tor
client/hs serv performance. most performance attention focuses on
relays or crypto primitives.

i'd like to run common Tor client/hs-serv benchmarks across a variety
of platforms. in particular the i.MX53 and i.MX6 line as step up
compute wise from these units. e.g.
http://www.inversepath.com/usbarmory.html for a nice i.MX53 device.

best regards,
-- 
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

