Re: [tor-relays] Measuring the Accuracy of Tor Relays' Advertised Bandwidths

2019-08-08 Thread NOC
I think that is a bad idea. You don't know enough about a relay to have a clue about what the underlying hardware looks like from any of that metrics. Simple example: You have a 8 core 16 threads cpu, run 4 instances, each node pinned to 2 threads and a 10 gig pipe, you will run each tor relay

Re: [tor-relays] Emerald Onion's new relays

2019-08-14 Thread NOC
Hi On 12.08.2019 23:39, teor wrote: Hi, On 13 Aug 2019, at 05:08, Roman Mamedov > wrote: On Mon, 12 Aug 2019 00:46:50 + Christopher Sheats > wrote: Tor Project, please increase your #IPv6 awareness/outreach similar to how ARIN

Re: [tor-relays] Emerald Onion's new relays

2019-08-18 Thread NOC
On 15.08.2019 00:50, teor wrote: Hi, On 14 Aug 2019, at 03:42, NOC mailto:t...@afo-tm.org>> wrote: On 12.08.2019 23:39, teor wrote: On 13 Aug 2019, at 05:08, Roman Mamedov <mailto:r...@romanrm.net>> wrote: On Mon, 12 Aug 2019 00:46:50 + Christopher Shea

Re: [tor-relays] Hardware specs for a high-bandwidth Tor exit?

2019-11-06 Thread NOC
Hi Christian, a AMD EPYC 7642 should be able to saturate that 20 GBit/s connection fine, Mainboard depends on what you prefer. Supermicro, HP and so on have all Mainboards for that CPU, so choose the one you prefer. On 06.11.2019 00:15, Christian Pietsch wrote: Dear Tor friends, the NGO I a

Re: [tor-relays] Improving Relay IPv6 - RIPE Grant

2019-12-12 Thread NOC
Great, than lets drop all IPv4 only relays from consensus 2020 finally. P.S. whitelist me so it doesn't take days till my emails appear on the mailing list. Thank you On 11.12.2019 03:20, teor wrote: Dear relay operators, I just wanted to let you know that RIPE has announced funding for Th

Re: [tor-relays] Improving Relay IPv6 - RIPE Grant

2019-12-16 Thread NOC
ork without any real reason. On 12/12/2019 5:49 PM, NOC wrote: Great, than lets drop all IPv4 only relays from consensus 2020 finally. P.S. whitelist me so it doesn't take days till my emails appear on the mailing list. Thank you On 11.12.2019 03:20, teor wrote: Dear relay operators,

Re: [tor-relays] Improving Relay IPv6 - RIPE Grant

2019-12-17 Thread NOC
On 16.12.2019 20:37, Ralph Seichter wrote: * NOC: I see a great benefit here, you could default to IPv6 for everything and enable IPv4 only as fallback [...] Preferring IPv6 over IPv4 is not even remotely the same as your original call to "lets drop all IPv4 only relays from consensus

Re: [tor-relays] Improving Relay IPv6 - RIPE Grant

2019-12-22 Thread NOC
On 21.12.2019 21:28, ILikeTor wrote: [..] only two relays per /64, for example? Do you have any plans for that already?[..] That is already a bad practice for IPv4 and is impossible to do for IPv6. There are server providers which give you a single IPv6 address (/128) and there are some which g

Re: [tor-relays] Got my first abuse

2020-04-16 Thread NOC
They raid your home even if the Tor node is run in a datacenter. Sadly the police in germany is still stuck in the 90s and most of them don't know and/or care what Tor is and how it works. On 16.04.2020 12:45, Mario Costa wrote: Where you running an exit from home? It’s really discouraged beca

Re: [tor-relays] Got my first abuse

2020-04-17 Thread NOC
*Gesendet:* Donnerstag, 16. April 2020 um 13:32 Uhr *Von:* "NOC" *An:* tor-relays@lists.torproject.org *Betreff:* Re: [tor-relays] Got my first abuse They raid your home even if the Tor node is run in a datacenter. Sadly the police in germany is still stuck in the 90s and most of them don't

Re: [tor-relays] Got my first abuse

2020-04-17 Thread NOC
On 17.04.2020 11:07, Michael Gerstacker wrote: Am Fr., 17. Apr. 2020 um 10:20 Uhr schrieb NOC <mailto:t...@afo-tm.org>>: I said most not 100%. My exits were in a Datacenter yet they showed up at my home. Actually it depends who it is. The local police here was very friendly

Re: [tor-relays] >23% Tor exit relay capacity found to be malicious - call for support for proposal to limit large scale attacks

2020-07-07 Thread NOC
Hi, great to see that the Tor network can lose ~20% capacity without having impact on the performance of the complete network. So can we get rid of the non dual stack relays now too? ___ tor-relays mailing list tor-relays@lists.torproject.org https:

Re: [tor-relays] new installation of an established TOR relay

2020-12-28 Thread NOC
On Sun, Dec 27, 2020 at 01:50:03PM +0100, RJ Hofmann wrote: caused by a temporary failure of the raspberry I had to completely renew installation of my TOR relay nicknamed mosaik. The new installtion is already up and running, but since I had no copies of keys and fingerprints the new relay is

Re: [tor-relays] Unsubscribing

2021-03-29 Thread NOC
Hello, the Tor staff makes that not easy, e.g. they rendered 50% of my capacity unsable with the change that limits the relays per IPv6. That are 2 Gbit/s less in and 2 Gbit/s out that are sitting idle now. The improvement to run crypto on multiple cores is open for over a decade and beside

Re: [tor-relays] Calling for more Exit Relays

2015-08-25 Thread NOC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The wiki is indeed not very up-to-date. You could go on a search for a provider by contacting different VPS or dedicated server providers yourself. A list I check once in a while is https://www.exoticvps.com/ I select the providers that offer suitab

Re: [tor-relays] Free Domain for Tor Nodes

2015-10-25 Thread NOC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Usually the Contact Info is obfuscated is some way. Tor Weather handles grabbing these just fine too so should not be a problem to automate the process. A lot of Exit operators already use subdomains of their own domains to provide their nodes with

Re: [tor-relays] MyFamily format

2015-10-28 Thread NOC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Just remove the parenthesis from that line and all should work fine. Make it look like this: MyFamily $A401E765D8B24057C3D91109D3C3E8D9E4B8BEAE,$68F162C50F22205FB3B728ACE6747 0B17D7430D6 On 10/29/2015 12:44 AM, starfire wrote: > MyFamily $(A401E76

Re: [tor-relays] IP-Echelon complains about claimed infringement

2015-11-21 Thread NOC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On the nodes I run where I managed to get a SWIP-ed IP address I am already ignoring these automatically generated IP-Echelon abuse complaints. For the nodes which do not have SWIP-ed IP addresses (also a node at myLoc) I reluctantly activated the r

Re: [tor-relays] Unbelieveable

2015-12-04 Thread NOC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 He probably means viewing the total number of connections to and from the relay. This is what I use munin for too: the total number of connections and the total amount of incoming and outgoing bandwidth. I use arm too to make me feel comfortable at

Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors

2015-12-19 Thread NOC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hereby I want to opt-in the following relays which are present on the list: BabylonNetwork02 (fingerprint: 54660C671B47E6986B465B8014BD19E5A34B) BabylonNetwork03 (fingerprint: C79552275DFCD486B942510EF663ED36ACA1A84B) And opt-out the next one f

Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors

2015-12-20 Thread NOC
directory mirrors that will be used I am all ears ;) On 12/20/2015 01:31 PM, Tim Wilson-Brown - teor wrote: > >> On 20 Dec 2015, at 02:55, NOC > <mailto:noc@babylon.network>> wrote: The initial message states >> that the relays should be non-exit replays. All these rel

Re: [tor-relays] Opt-In Trial: Fallback Directory Mirrors

2015-12-20 Thread NOC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Thanks for the information. The load should be no problem at all, great to hear ;) On 20/12/15 14:37, Tim Wilson-Brown - teor wrote: > >> On 20 Dec 2015, at 23:42, NOC > <mailto:noc@babylon.network>> wrote: >> >>

[tor-relays] Webiron at it again...

2015-12-15 Thread Schokomilch NOC
Monday we received their usual spam about our exit-node sending spam, and of course instead of implementing the TorDNSEL on their sites, they rather want us to block a whole /24 range. Anyhow, one line caught our eyes: "Tor: Please note as the abuse from Tor has gotten out of hand, we do not

Re: [tor-relays] Webiron

2016-01-29 Thread Schokomilch NOC
ip + email combinations, e.g. https://www.webiron.com/images/misc/2__._40.6.20_/quanhf@_inamobile.com/webiron-logo_abuse.png https://www.webiron.com/images/misc/_88.93._44.86/noc@_omein.nl/webiron-logo_abuse.png https://www.webiron.com/images/misc/_48.25_.83._6/abuse@mkauf.de/webiron

Re: [tor-relays] Webiron

2016-01-29 Thread Schokomilch NOC
thinks and they don't seems to think so highly of them because it's one of the largest ISP on the webiron list and according to that new feature of webiron, they never open their email. On 2016-01-29 2:13 PM, Schokomilch NOC wrote: We quickly have created a poc to prevent their webbug of

Re: [tor-relays] Relays by AS Names

2016-04-05 Thread Schokomilch NOC
Well, you can think of different countries / hosters you would like to run your exit at and then check on globe how populated that location is: https://globe.torproject.org It's not exactly what you want, but a start. On 05.04.2016 08:24 PM, SuperSluether wrote: I want to host an exit relay,

Re: [tor-relays] Dealing with OVH Abuse Complaints

2016-10-05 Thread Schokomilch NOC
The problem with Belgium isn't finding a Tor friendly provider, the problem is that bandwidth costs a lot of money, very weird considering Belgium is supposed to be a developed nation (up until recently, residential lines had a traffic limit too, maybe they still do): http://www.belgonet.com/

Re: [tor-relays] Reaching out to webiron

2017-02-11 Thread Schokomilch NOC
I'd like to mention a few additional things: Firstly if you look at the source code of their mail, then you will find that the image is hosted at a unique URL. Automatically loading the image will let them know that you opened the mail. They also publish this info in their abuse feed e.g.: h