Would Tor relays work in a dynamic manner switching from one to another from time to time? I am at the beginning of my research regarding a Tor network and I could use some support from you, guys. I would read a bit about entry, middle and exit relays as well as layers of encryption, but I need more realistic explaination how all of these operate in a practice. Thank you!

On Sun, Apr 10, 2016 at 11:01 PM, <tor-relays-request@lists.torproject.org> wrote:
Send tor-relays mailing list submissions to
        tor-relays@lists.torproject.org

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
or, via email, send a message with subject or body 'help' to
        tor-relays-request@lists.torproject.org

You can reach the person managing the list at
        tor-relays-owner@lists.torproject.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of tor-relays digest..."


Today's Topics:

   1. Potwin, Kansas (Kenneth Freeman)
   2. First (positive) experiences with a Tor Relay on  Raspberry
      Pi3 (fr33d0m4all)
   3. Re: First (positive) experiences with a Tor Relay on
      Raspberry Pi3 (Yawning Angel)
   4. First Relay (KAW)
   5. First Relay (KAW)
   6. Re: First Relay (pa011)
   7. Re: First (positive) experiences with a Tor Relay on
      Raspberry Pi3 (Tom Jorquera)


----------------------------------------------------------------------

Message: 1
Date: Sun, 10 Apr 2016 10:56:52 -0600
From: Kenneth Freeman <kencf0618@riseup.net>
To: tor-relays@lists.torproject.org
Subject: [tor-relays] Potwin, Kansas
Message-ID: <570A85D4.2060107@riseup.net>
Content-Type: text/plain; charset="utf-8"

So this is why 114 Tor exit nodes are apparently operating from Potwin,
Kansas! Figured it was a digital artifact. The article doesn't mention
Tor itself, but the nominal fount really jumps out on TorFlow.

http://fusion.net/story/287592/internet-mapping-glitch-kansas-farm/

https://torflow.uncharted.software/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xDD79757F.asc
Type: application/pgp-keys
Size: 3129 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/cf9f1a4a/attachment-0001.key>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/cf9f1a4a/attachment-0001.sig>

------------------------------

Message: 2
Date: Sun, 10 Apr 2016 17:52:20 +0000
From: fr33d0m4all <fr33d0m4all@riseup.net>
To: tor-relays@lists.torproject.org
Subject: [tor-relays] First (positive) experiences with a Tor Relay on
        Raspberry Pi3
Message-ID: <570A92D4.5000006@riseup.net>
Content-Type: text/plain; charset=utf-8

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi,
I've just moved my Tor relay installation from my alix1.c embedded
system (500Mhz CPU with 256Mb ram) which was able to offer only 4Mbps
(100% CPU utilization) to a new Raspberry Pi3 (quad-core 1.2Ghz 64-bit
cpu with 1 GB ram). Some days ago I've seen some messages on the ML
about Pi2 performance (if I remember well) and I'd like to share my
first experiences with Pi3. I have only 20Mbps connection in the
uplink direction, so I'm offering about 15Mbps for Tor relay and I've
just seen that it is able to offer 14Mbps with 40% of a single core
utilization.. In conclusion, I think that a single relay on Pi3 can
offer about 30-40 Mbps, and if you run 4 tor relays on the same Pi3
you can offer more than 100Mbps which is definitely not bad for such a
small system. The only drawback is that you need to find a good way
for keeping it cold, since after 1 hour of 1 core at 100% I've reached
about 70?C with heatsinks on the CPU.

I just wanted to share my experience with you, hope you find it
interesting :)

Have a nice week
   Fr33d0m4All

- --

_____________________________________________________________

 PGP Key: 0DA8 7293 D561 3AEE A3C0  7F63 101F 316A F30E ECB4
 IRC Nick: fr33d0m4all (OFTC & Freenode)
_____________________________________________________________
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXCpLUAAoJEBAfMWrzDuy0KpQQAKG1Su24A3O1keFdPGk2zdzw
lwEk+pSvRzfoHfmocv5ia9PQ8ZtBws3QfaxfZOYIA0DxdKVK7Rcs+r0ekL6VtAdp
y3HU3SlAoCxFDsHycsPhuXZPmQqU/+OAS0lrzo2KrKk/lN/K+b2YYzLfJ+9SWzE1
kg4dcCnWfQrMsLLK72R9qIjSmDsXDGzzNRq0qM3nDjDmE5GPmMJajSbWsHP12v/q
BnA786RdB/CDiFVifGPYsKEuughpJ1ryVSRm3LdmTdIjZ+u/sxz0/TQrmj7idgdr
TenFk4rf0NbiLU/7sruNJNYPFHvUMUOC8Xu7wBJU2LTF/8fcjYOaQp2UWch4aGQa
nM4tMetvhEmoGxcEmJSsi2CHdLkMZ8G67gfufb7Gmsmd59q0KvRQktPxqnJ0GJIs
20x2PX2qzXX7P4mKL8nO0aX32OP+1xScuSH/85Lu6Nnh1jL+T81QPjk/CUHB86ho
gbuGt154KEnMoKx+w3aXrzSKVH5kRMgWhIcbRt/xELWprx2zsxGM+gIOCdLQ/vXi
PugDblYL8sa8Uds6cz0fjNsuCBI19X0NlnmGFAbU9qOHEhUzYpuF4VlH7sOkL0n2
HWkJTSIjizjZCS0PDPeaqj3lOtoFJiYcAxef+HnGEI/5dameIBB/MDJyOrf+oRfL
1kNo6Zd5KqJesnljCac5
=pk6h
-----END PGP SIGNATURE-----


------------------------------

Message: 3
Date: Sun, 10 Apr 2016 18:28:30 +0000
From: Yawning Angel <yawning@schwanenlied.me>
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] First (positive) experiences with a Tor
        Relay on Raspberry Pi3
Message-ID: <20160410182830.2be8c166@schwanenlied.me>
Content-Type: text/plain; charset="utf-8"

On Sun, 10 Apr 2016 17:52:20 +0000
fr33d0m4all <fr33d0m4all@riseup.net> wrote:
> I've just moved my Tor relay installation from my alix1.c embedded
> system (500Mhz CPU with 256Mb ram) which was able to offer only 4Mbps
> (100% CPU utilization) to a new Raspberry Pi3 (quad-core 1.2Ghz 64-bit
> cpu with 1 GB ram). Some days ago I've seen some messages on the ML
> about Pi2 performance (if I remember well) and I'd like to share my
> first experiences with Pi3. I have only 20Mbps connection in the
> uplink direction, so I'm offering about 15Mbps for Tor relay and I've
> just seen that it is able to offer 14Mbps with 40% of a single core
> utilization.. In conclusion, I think that a single relay on Pi3 can
> offer about 30-40 Mbps, and if you run 4 tor relays on the same Pi3
> you can offer more than 100Mbps which is definitely not bad for such a
> small system. The only drawback is that you need to find a good way
> for keeping it cold, since after 1 hour of 1 core at 100% I've reached
> about 70?C with heatsinks on the CPU.

If you build tor against OpenSSL 1.1 on that target you will get a
massive increase in performance due to support for the ARMv8 hardware
AES acceleration.

This requires 0.2.8.x from the maint-028 branch (or master if you're
brave) since I recently fixed tor (again) to compile with this version
of the library, but the changes will be in the next 0.2.8 release
candidate.

Regards,

--
Yawning Angel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/3ff32d8d/attachment-0001.sig>

------------------------------

Message: 4
Date: Sun, 10 Apr 2016 15:09:07 -0400
From: "KAW" <kawhunter@sigaint.org>
To: tor-relays@lists.torproject.org
Subject: [tor-relays] First Relay
Message-ID: <5390b0454b7f2274504046a39fa5f5d6.webmail@localhost>
Content-Type: text/plain;charset=iso-8859-1

Got my first relay running for 4 days now :D


-KAW



------------------------------

Message: 5
Date: Sun, 10 Apr 2016 15:08:37 -0400
From: "KAW" <kawhunter@sigaint.org>
To: tor-relays@lists.torproject.org
Subject: [tor-relays] First Relay
Message-ID: <b68a0e7f3801df57a5ea88fdaad3fd97.webmail@localhost>
Content-Type: text/plain;charset=iso-8859-1

Got my first relay running for 4 days now :D


-KAW



------------------------------

Message: 6
Date: Sun, 10 Apr 2016 22:14:37 +0200
From: pa011 <pa011@web.de>
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] First Relay
Message-ID: <570AB42D.5010403@web.de>
Content-Type: text/plain; charset="windows-1252"

Congratulation - I know that feeling very well ...one after another.... :-)

Am 10.04.2016 um 21:08 schrieb KAW:
> Got my first relay running for 4 days now :D
>
>
> -KAW
>
> _______________________________________________
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xC8C330E7.asc
Type: application/pgp-keys
Size: 3104 bytes
Desc: not available
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/01474be3/attachment-0001.key>

------------------------------

Message: 7
Date: Sun, 10 Apr 2016 23:01:21 +0200
From: Tom Jorquera <tom@jorquera.net>
To: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] First (positive) experiences with a Tor
        Relay on Raspberry Pi3
Message-ID: <570ABF21.7090504@jorquera.net>
Content-Type: text/plain; charset="windows-1252"; Format="flowed"

On 10/04/2016 20:28, Yawning Angel wrote:
> On Sun, 10 Apr 2016 17:52:20 +0000
> fr33d0m4all <fr33d0m4all@riseup.net> wrote:
>> I've just moved my Tor relay installation from my alix1.c embedded
>> system (500Mhz CPU with 256Mb ram) which was able to offer only 4Mbps
>> (100% CPU utilization) to a new Raspberry Pi3 (quad-core 1.2Ghz 64-bit
>> cpu with 1 GB ram). Some days ago I've seen some messages on the ML
>> about Pi2 performance (if I remember well) and I'd like to share my
>> first experiences with Pi3. I have only 20Mbps connection in the
>> uplink direction, so I'm offering about 15Mbps for Tor relay and I've
>> just seen that it is able to offer 14Mbps with 40% of a single core
>> utilization.. In conclusion, I think that a single relay on Pi3 can
>> offer about 30-40 Mbps, and if you run 4 tor relays on the same Pi3
>> you can offer more than 100Mbps which is definitely not bad for such a
>> small system. The only drawback is that you need to find a good way
>> for keeping it cold, since after 1 hour of 1 core at 100% I've reached
>> about 70?C with heatsinks on the CPU.
> If you build tor against OpenSSL 1.1 on that target you will get a
> massive increase in performance due to support for the ARMv8 hardware
> AES acceleration.
>
> This requires 0.2.8.x from the maint-028 branch (or master if you're
> brave) since I recently fixed tor (again) to compile with this version
> of the library, but the changes will be in the next 0.2.8 release
> candidate.
>
> Regards,
>
>
>
> _______________________________________________
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

To follow up on your experience

I am currently running a relay from a rasp3 with a bandwidth limit of 24
Mb/s.

I am using the tor package from raspbian (Tor 0.2.5.12).

arm currently gives me the following informations:
cpu: usually between 20.0% and 40%
mem: 160 MB (17.3%)
for a current average down and up of 35.3 Mb/sec and 36.1 Mb/sec (due to
my high burst rating I suppose)

The 15 mins load average of the raspy (which mostly runs tor) is 0.38.
It may be biased by me running arm, which seems rather CPU intensive, to
look things up for a while.

I am not monitoring the temperature. The CPU seems a little hot to the
touch, but not overly so. The rasp has an uptime of 14 days.

All in all it seems to handle the load rather well!

Regards,

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20160410/532b3761/attachment.html>

------------------------------

Subject: Digest Footer

_______________________________________________
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


------------------------------

End of tor-relays Digest, Vol 63, Issue 20
******************************************



--
A security is a process of maintaining an acceptable level of the risk.

Milica Đekić

Cybersecurity researcher
Twitter: @MilicaDjekic9
Cell: +381 63 1963627