Re: [tor-relays] Tor non-exit list

Hi Carsten, Although I understand why you're directing your comments to Dan, because his site is popular, but you should note that even if he decides to take that list down, his site is not the only way for people to get their hands on the list. In fact anyone with basic know-how can extract them

Re: [tor-relays] Way to be notified when relay goes offline?

Or, like me, you can run your own monitoring service: https://github.com/louislam/uptime-kuma docker-compose.yml  content: ``` version: '3.8' services:   uptime-kuma:     image: louislam/uptime-kuma:latest     container_name: uptime-kuma     volumes:   - uptime-kuma:/app/data     ports:   

[tor-relays] A new kind of attack?

I've noticed a new kind of possible attack on some of my relays, as early as Dec.23 which causes huge spikes of outbound traffic that eventually maxes out RAM and crashes Tor. The newest one today lasted for 5 hours switching between two of the three relays on the same IP. During the attack, Tor b

Re: [tor-relays] Relay that's been running for a long time suddenly saying it's new?

It's not just you. 3 of my relays show as new for the past few days and they still do. It doesn't seem to affect the traffic though so I'm assuming it's just a reporting issue and Authorities don't see your relay as new. On 1/12/2024 1:00 PM, Keifer Bly wrote: > Hi, > > So my relay > at  > https:

Re: [tor-relays] Relay data limit

Hi Dan, There's of course another option. Change your provider unless it's important to you to use them in particular. The market is full of good deals with very good bandwidth allowances. I really don't understand how some providers can get away with using bandwidth as money grab. I use my own b

Re: [tor-relays] Exit operators on the 0.4.8.x series, please upgrade to 0.4.8.10 ASAP!

And epel repo for Centos and Almalinux pretty please... On 12/8/2023 3:20 PM, Georg Koppen wrote: > Hello exit node operators! > > Today (2023-12-08) the Network Team has released a new Tor version, > 0.4.8.10[1]. This update contains a fix to a remotely triggerable > crash bug (TROVE-2023-007) a

Re: [tor-relays] Relay no longer acting as a gaurd node?

Just wondering, you haven't set a bandwidth limit on that node, have you? Setting an AccountingMax directive will cause you to lose your Guard flag since your server can't be available at all times. On 11/9/2023 10:03 AM, Jonathan Proulx wrote: > Hi All, > > A little while ago one of my relays sw

Re: [tor-relays] Receiving abuse reports for Non-Exit Relay

As others have mentioned, this does not look like a Tor issue to me. It more seems like a compromised or misconfigured server. You mentioned you reinstalled the OS. Did you use the same root password? My suggestion is that you go about this step by step. First reinstall the OS with a different roo

Re: [tor-relays] Relay Bandwidth

Hi, The reason you find the answers confusing is because the whole thing is confusing. A lot of what you see advertised by hosts is somehow misleading. For example they advertise a 1000 mb/s network speed and then they give you 3 TB of bandwidth. The truth is that even if you have a sustained netw

Re: [tor-relays] Questions about 4 Relays per IP and the ddos mitigation scripts

flags, so an attacker can't > just spin up 8 new relays per IP.) > > Also, it might be good to have a more conservative (higher) rate limit > by default and > let users turn it down as necessary. > -- > Danny > > On Tue, Feb 7, 2023 at 8:34 AM Chris Enk

Re: [tor-relays] Questions about 4 Relays per IP and the ddos mitigation scripts

> DDoS rate limit filters do not require an all or nothing approach, > different source IPs can be handled differently > see toralf's use of onionoo to feed ipsets as an example. > I would recommend to use tor's controlport as a source of information instead > though > because onionoo is not meant

Re: [tor-relays] Questions about 4 Relays per IP and the ddos mitigation scripts

@nusenu Thank you very much for taking the time to help me understand things better. I can use all the help I can get.     > You can also not be sure whether it is an actual authenticated relay to relay     > connection or a client to relay connection just by looking at the source IP.     > In

[tor-relays] Questions about 4 Relays per IP and the ddos mitigation scripts

Hello Everyone, Before I make changes to [my scripts](https://github.com/Enkidu-6/tor-ddos), I need to understand a few things and any help is much appreciated. - First, Does an Exit relay with zero Guard probability and zero middle relay probability need to initiate circuits with a Guard or midd

Re: [tor-relays] inet_csk_bind_conflict

html > > > > ExitPolicy reject 23.129.64.128/25:*,reject6 > [2613:18c:0:192::]/64:*,accept *:*,accept6 *:* > > > > MyFamily > > # end of torrc > > > > -- > Christopher Sheats (yawnbox) > Executive Director > Emerald Onion > Signal: +1 206.739

Re: [tor-relays] Tor DDoS Mitigation iptables scripts update. Version 4.0.1

https://github.com/Enkidu-6/tor-ddos/blob/dev/multiple/two-or.sh Let me know how it goes if you decide to have a go at it. Cheers. On 12/3/2022 6:29 AM, Anders Trier Olesen wrote: > Hi Chris > > > Not at all. That's how I'm running my own relays. Just run the > > **combin

Re: [tor-relays] inet_csk_bind_conflict

). 16 hours later, Tor dropped > below 2 Mbps. > > I've removed all of these new settings and restarted. > > -- > Christopher Sheats (yawnbox) > Executive Director > Emerald Onion > Signal: +1 206.739.3390 > Website: https://emeraldonion.org/ > Mastodon: htt

Re: [tor-relays] inet_csk_bind_conflict

Hi, As I'm sure you've already gathered, your system is maxing out trying to deal with all the connection requests. When inet_csk_get_port is called and the port is found to be occupied then inet_csk_bind_conflict is called to resolve the conflict. So in normal circumstances you shouldn't see it i

Re: [tor-relays] Tor DDoS Mitigation iptables scripts update. Version 4.0.1

) for the repository on github in case you have any questions, suggestions or simply need further help. On 12/1/2022 11:57 AM, Anders Trier Olesen wrote: > Hi Chris > > We run all the 12 dotsrc relays on a single host with many IP > addresses. Would we need to change anything? > >

[tor-relays] Tor DDoS Mitigation iptables scripts update. Version 4.0.1

Background: A set of bash scripts used to apply iptables rules to fight the current DDoS attacks. They require no dependencies to install except iptable/nftables which all Linux flavors already have and require no particular expertise. The issue was discussed here: [issue 40093](https://gitlab.to

Re: [tor-relays] preventing DDoS is more than just network filtering

On 11/10/2022 2:38 AM, Scott Bennett wrote: Toralf F?rster wrote: On 11/8/22 10:57, Chris wrote: The main reason is that a simple SYN flood can quickly fill up your conntrack table and then legitimate packets are

[tor-relays] Tor DDoS Mitigation iptables scripts updated to version 3.0.0

Background: A set of bash scripts used to apply iptables rules to fight the current DDoS attacks. They require no dependencies to install except iptable/nftables which all Linux flavors already have and require no particular expertise

Re: [tor-relays] List number of circuits per connection

You may want to check these links: https://gitlab.torproject.org/tpo/community/support/-/issues/40093 https://github.com/Enkidu-6/tor-ddos https://github.com/toralf/torutils On 10/19/2022 8:47 AM, Logforme wrote: I run the relay 8F6A

Re: [tor-relays] many connections

block list. On 10/6/2022 1:13 PM, Richie wrote: Hoi, Chris, oh wow, that seems to help a lot. Uptime 1/2 hour now, load 50-60% and six IPs collected according to compare.sh. No signs of overload yet. Thanks a lot, and i'

Re: [tor-relays] many connections

Hi Richie I was a bit lost myself having to deal with the scripts and additional packages to install. So I put something together for myself based on the same rules and added a few twists but in a simple text n00b proof format. It's as simple a

Re: [tor-relays] Tor project helping to attempt to cancel Richard Stallman

Roman Mamedov wrote on 3/26/21 11:10 AM: Could be important to note that no harassment allegations were ever aimed at RMS himself, he's just being attacked for posting a personal opinion about unrelated events. The mattress on the floor of his MIT office and the 30 year history of him hitting

Re: [tor-relays] Tor project helping to attempt to cancel Richard Stallman

I've already tripled the bandwidth and burst settings on my US exit relay that I've been running for many years in honor of the poutrage flounces we've seen today niftybunny wrote on 3/25/21 3:37 PM: I will spin up 2 relays for every relay this guy and other RMS supporters will shut down. n

Re: [tor-relays] Exit relay operators please help test #2667 branch

Have a tor exit running in the US ; fingerprint is 3DE567C1350C0E858C6147AECB06EA9B3EAF3261 and OR address is 71.174.105.126:9001 Just built and launched the ticket-2667 branch; came up as: [notice] Tor 0.4.6.0-alpha-dev running on Linux with Libevent 2.0.21-stable, OpenSSL 1.0.1t, Zlib 1.

Re: [tor-relays] Log warning : possible (zlib) compression bomb on middle relays

Same on my US exit relay: Nov 02 04:03:50.000 [warn] Possible zlib bomb; abandoning stream. Nov 02 04:03:50.000 [warn] Possible zlib bomb; abandoning stream. Christoph Graf November 2, 2020 at 11:59 AM Same here on my bridge: Nov  2 06:21:04 raspipfupf Tor[

[tor-relays] Cherryservers (formerly balticservers) account terminated for exit relay

I just heard from the hosting provider cherryservers.com that they are terminating my account (after 2.5 years) where I run the exit relay "ostwaldripening" (46.166.162.53), because they no longer wish to host tor exit nodes. I tried to create an account on trac.torproject.org to edit the "Good

[tor-relays] Best practice for tor-exit node when I switch internet providers?

up with a new address. -Chris ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] 10 Years Torservers.net: Death or Future?

On Saturday, 4 May 2019 11:57:24 CEST Moritz Bartl wrote: > The only capacity I can offer is that we *need* someone to step up, and grab > me at some event in meatspace. Ideally at that point that person is willing > to have the A record pointed at some new place under their control, and we > ca

Re: [tor-relays] Kitten1 and kitten2 compromised (guard/hs/fallback directory)

On Saturday, 20 May 2017 17:31:25 CEST Anders Andersson wrote: > On Sat, May 20, 2017 at 5:20 PM, aeris wrote: > >> Could you please share some more information about the incident? > > > > From what I know and what I can speak about : > > > > A big and sensible French company was infected with W

Re: [tor-relays] Relay has Low Consensus and No Exit Flag Following Upgrade

The update was over 30 days ago. How long should I wait? C On 7 May 2017 4:59 p.m., "Roger Dingledine" wrote: > On Sun, May 07, 2017 at 02:20:42PM +0100, Chris wrote: > > However, it no longer has the exit node flag and the consensus is very > > low (20). It also is

Re: [tor-relays] Relay has Low Consensus and No Exit Flag Following Upgrade

Why is that? Perhaps they tried to measure and it failed? On 7 May 2017 2:39 p.m., "nusenu" wrote: > > I recently upgraded my tor exit relay's tor version to 0.2.8.12. > > > > The uptime is 51 days and it has valid, running and stable flags. > > > > However, it no longer has the exit node flag

[tor-relays] Relay has Low Consensus and No Exit Flag Following Upgrade

g the upgrade has broken it as I had some SELinux issues binding to the ports before - which I resolved. There are no errors in ARM although the log is non existent? - permissions error? The fingerprint is 575F2C60045805ABFDB2B7D7A78982F9571BC277 Where should I start to fix this? Best Wishes,

Re: [tor-relays] CentOS Tor exit node broken after updating to 2.8.12

Good suggestion, I was indeed getting AVC errors. - Changing to 443 didn't help though. I have returned to the default OrPort of 9001 for now which works and I will try adding 443 to selinux for tor at a later date. Thanks, Chris On 25/02/17 09:23, nusenu wrote: > getsebool

[tor-relays] CentOS Tor exit node broken after updating to 2.8.12

ports lower than 1024 but it made no difference. I suspect this an issue with the configuration of the server rather than tor. Where should I start? Best, Chris -- Protect your privacy: encrypt your communications GPG: CF7F98B2 ___ tor-relays mailing

Re: [tor-relays] Exit Node Geographical Location

Okay, So I've found a ISP in Kenya that says they're happy to host a tor exit node. The ping is 270ms from a Canadian ISP, 16 hops. 183ms from Germany, 13 hops. Ultimately, am I making the tor network better or worse, if I were to set up some tor nodes here? - Chris On Fri, Dec 9, 20

Re: [tor-relays] Exit Node Geographical Location

ty but usuage remains low for me in > more isolated areas e.g Bangalore,Africa > > regards > > Mark B > > > > On 8 Dec 2016, at 09:53, Chris Adams wrote: > > > > Hello, > > > > I want to start up another exit node. I have a few choices for which >

Re: [tor-relays] Creanova hosting Finland

ttps://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > -- Chris Adams <http://chrisada.co.uk> ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Exit Node Geographical Location

Hello, I want to start up another exit node. I have a few choices for which country it's in. I currently live in a country with quite a high exit node/population density. Are there any advantages to distributing nodes around the globe in terms of performance/privacy? Are there some countries whe

Re: [tor-relays] 7 relays gone because of spammers

ing to Tor. -Chris On Wed, Feb 25, 2015 at 1:35 PM, Speak Freely wrote: > Hello fellow relay runners, > > This morning OVH decided to kill 7 of my relays due to spamming, and > block all access to all services. I ran the Reduced Exit policy for all > of my relays. > > Due to

Re: [tor-relays] "Very Safe" Exit Policy

y car insurance works in the US with 'points' might make sense, but that would totally break the whole point of Tor - to provide anonymity for its users. Bleah. Pesky humans :) -Chris On Tue, Feb 17, 2015 at 11:55 AM, Roger Dingledine wrote: > On Tue, Feb 17, 2015 at 11:02:45AM

Re: [tor-relays] "Very Safe" Exit Policy

; > https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt > > Hope that helps, > Jeremy Sadly, anyone concerned about their ISP flipping out can't afford to have these ports open. I tried running an exit for a bit and it lasted a few weeks before some brainless wonder hijacked

Re: [tor-relays] tor weather not sending emails?

I've also stopped getting emails from Tor weather for my relay. It has been months since I got anything. On Tue Feb 10 2015 at 12:18:11 Nusenu wrote: > Hi, > > I subscribed to tor weather to get notifications in case something is > wrong with a relay. > > Although the relay had several downtimes

[tor-relays] Avoiding using my own Exit

ay be lacking clarity. Cheers, Chris ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Less Traffic on my relay

, you'll need to slightly modify things, but it should help you get started at least :) Good luck! Chris On 7 Oct 2014 14:57, "Tor Zilla" wrote: > Hi Julien, > > Thanks a lot for your reply. > > I got your point now.. > > You are right. I am using a DSL connect

Re: [tor-relays] Arch Linux packages?

https://www.archlinux.org/packages/community/x86_64/tor/ https://aur.archlinux.org/packages/arm/ Chris Bero On Sun, Oct 5, 2014 at 8:54 AM, Eric Hocking wrote: > Hi all, > I looked through the Arch Linux repository, and wasn’t able to find any > packages for Tor or arm. Does a

Re: [tor-relays] Scramblesuit

Thanks, will look at that link - sounds interesting indeed! Maybe something to play with in the future. On 2 Oct 2014 01:24, "isis" wrote: > Chris Whittleston transcribed 5.0K bytes: > > I'm right in thinking that running scramblesuit is not going to do > anything >

Re: [tor-relays] Scramblesuit

bfsproxy --log-file > /var/log/tor/scramblesuit.log --log-min-severity info managed > > > -- > ♥Ⓐ isis agora lovecruft > _ > GPG: 4096R/A3ADB67A2CDB8B35 > Current Keys: https://blog.patternsinthevoid.net/isis.txt > >

Re: [tor-relays] Correctly setting up arm

looks like installing deb.torproject.org-keyring will help prevent those issues in the future. I'll update my Pi relay tutorial with this and the updated arm instructions https://docs.google.com/document/d/1bf_D_j1O-9ckTS9DY8ngIdiFwHta6Q5Uj_5dvOiavCQ/edit?usp=sharing Thanks again both, Chris

Re: [tor-relays] Correctly setting up arm

Aha - thanks Grace, that explains the initial error for sure! Chris On 22 September 2014 21:53, Grace H. wrote: > On Mon, 22 Sep 2014 21:34:40 +0100 > Chris Whittleston wrote: > > > Am I missing something when it comes to setting up > > CookieAuthentication? I guess I

[tor-relays] Correctly setting up arm

ontrolPassword by generating a has using tor --hash-password and editing torrc accordingly. Am I missing something when it comes to setting up CookieAuthentication? I guess I must be...although it seems strange that I was getting that error even with CookieAuthentication disabled. Any insight apprec

Re: [tor-relays] BBC and UK Lottery blocking ip addresses running relay

That's great news Dan, keep us posted! Chris On 18 Sep 2014 21:40, "Dan Hanley" wrote: > >> I have just received a slightly more positive reply: > > "At present, our GeoIP data provider classes Tor nodes as proxies, > regardless of whether or not they

Re: [tor-relays] BBC and UK Lottery blocking ip addresses running relay nodes

14 I suspect you'll end up having to explain that you're running a relay in the end anyway, but you never know. Chris On 17 September 2014 21:48, Matt Puckey wrote: > Stephen Mollett: > > [...] > > "Thank you for contacting the BBC iPlayer support team. > >

Re: [tor-relays] BBC and UK Lottery blocking ip addresses running relay nodes

fixing the BBC issue may resolve your Lottery problem...but we can't be sure. I'd get whatever contact details you can from them and explain the problem, what a middle relay is, how it's just you etc and see what they say. Good luck, Chris On 11 September 2014 17:23, Dan Hanley wro

Re: [tor-relays] Contacting Apple About a Block IP Address

as already suggested, notify them off the issue and politely explain where they can find out more about Tor. I found Twitter to be a surprisingly good channel for contacting the BBC tech guys. Good luck getting it resolved, Chris On 13 Aug 2014 18:22, "Jesse Victors" wrote: > > ---

Re: [tor-relays] BBC iPlayer blocked for UK middle relay operators?

FYI - I've just sent another email/contact form to them asking if running a Tor relay could be an issue and explaining in detail the differences between middle and exit relays etc. We shall see if this yields any more useful response from them. I'll keep you posted. On 28 June 2014 16

Re: [tor-relays] BBC iPlayer blocked for UK middle relay operators?

across all platforms. Once again, thanks for taking the time to contact us. ----- Chris On 28 June 2014 15:52, Paul Blakeman wrote: > Hi all > > Matthew’s advice is correct. > Switching to “modem only” DOES achieve getting a dynamic IP

Re: [tor-relays] BBC iPlayer blocked for UK middle relay operators?

C support about this under I get a response other than 'have you tried turning your router off and on' or 'check your IP is registered in the UK with your ISP' - ugh... Thanks for the info all On 28 June 2014 13:23, Paul Blakeman wrote: > Chris > > I have had sev

[tor-relays] BBC iPlayer blocked for UK middle relay operators?

ering if the provider BBC use for iPlayer might have started just blocking all Tor IPs recently - including middle relays. Chris ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Relay down, "rejected", help

Thanks for pointing this 'unsafe' use of arm out guys - I just checked and it somehow snuck into my Pi relay tutorial docs also. I'll update them when I have had chance to do some testing early next week. Best, Chris On 19 Apr 2014 21:50, "Michael Wolf" wrote: >

Re: [tor-relays] A few questions about my setting up my first Tor relay.

That sounds great Nastase, please share the results! Chris On 18 Apr 2014 23:14, "Nastase G. Eduard" wrote: > Well, this really convinced me on using Raspberry as a relay. Very nice > guide. Due to the very low power consumption I'm thinking on setting relays > th

Re: [tor-relays] A few questions about my setting up my first Tor relay.

power requirements and doesn't need you to leave one of your other machines on all the time. If you're curious about this option, I've written up some pretty detailed instructions here: https://docs.google.com/document/d/1bf_D_j1O-9ckTS9DY8ngIdiFwHta6Q5Uj_5dvOiavCQ/edit?usp=sharing Good lu

Re: [tor-relays] Recommended reject lines for relays affected by Heartbleed

tion about. But I wanted to > > make sure about this, as I couldn't find anything on the Tor FAQ. > > Apologies if this is answered somewhere else. > > > > Thanks, Hugh > -BEGIN PGP SIGNATURE- > Version: GnuPG v2.0.22 (GNU/Linux) > > iEYEARECAAYFAlNP+74ACgkQAO6N0EYmC9a3OgCgrwgZqo6B

Re: [tor-relays] Recommended reject lines for relays affected by Heartbleed

FYI guys - The Guardian just published an article about the effect of Heartbleed on the network: Tor may be forced to cut back capacity after Heartbleed bug http://gu.com/p/3zfqj On 17 Apr 2014 12:51, "Steve Snyder" wrote: > On 04/17/2014 12:17 AM, Roger Dingledine wrote: > >> On Wed, Apr 16, 2

Re: [tor-relays] NHS UK blocking Tor?

contacted Ross also so we'll see if he has any insight or advice. Here is their reply: - Dear Chris, Thank you for contacting the NHS Choices Service desk Unfortunately the issue you have raised seem to be to with your interne

Re: [tor-relays] NHS UK blocking Tor?

ning on at least explaining the difference between middle and exit relays. Chris On 15 April 2014 00:50, Pepijn Le Heux wrote: > > On 15 apr. 2014, at 00:50, Scott Bennett wrote: > > > Chris Whittleston wrote: > > > >> Can someone else running a relay from their home

[tor-relays] NHS UK blocking Tor?

s does turn out to be them blocking Tor - advice on how to approach contacting them to resolve this would be appreciated. Thanks, Chris -- *Dr Chris Whittleston 栗主* Department of Chemistry University of Cambridge Lensfield Road, Cambridge, CB2 1EW Email: cs..

Re: [tor-relays] Heartbleed" Exchange of keys now or later?

I've also noticed a big uptick in traffic in the last 24/48 hours which has somewhat overwhelmed my poor Raspberry Pi :( guess we sit tight and wait for things to settle. On 9 Apr 2014 15:27, "Sebastian Urbach" wrote: > Hi, > > I recall that Roger Dingledine pointed out that this is a stress situ

Re: [tor-relays] Relays vulnerable to OpenSSL bug: Please upgrade

Yup - looks like I just missed it before, updated - now to clear keys and reboot. Thanks, Chris On 8 April 2014 20:48, Alexander Dietrich wrote: > I just got 1.0.1e-2+rvt+deb7u5, try again? > > Best regards, > > Alexander > > --- > PGP Key: 0xC55A356B | https://diet

Re: [tor-relays] Relays vulnerable to OpenSSL bug: Please upgrade

he pi would be appreciated. Chris On 8 April 2014 18:46, elrippo wrote: > Indeed, you should check you /var/lib/tor/keys directory to be empty before > restarting your service again. > > ATTENTION!!! > On a Debian box, i got the "warning" to restart the openssh and ope

Re: [tor-relays] Raspberry Pi binary .debs - 0.2.4.21

ee what else you are working on :) Chris On 24 March 2014 21:17, Gordon Morehouse wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi, Chris! > > Chris Whittleston: > > Thanks for this Gordon M - just thought I'd add that if it's useful >

Re: [tor-relays] Raspberry Pi binary .debs - 0.2.4.21

mitted anything important - please let me know. I know it's long (and goes through some pretty simple stuff), but the idea was to make it accessible to people who weren't otherwise likely to give setting up a relay a try. Chris On 22 March 2014 22:33, Gordon Morehouse wrote: > -

Re: [tor-relays] Botnet issues and upgrading to 0.2.4.x

Thanks for the replies guys - I've not has a storm in the last few days, but if/when my Pi gets knocked offline again, I'll dig into those mitigation strategies. Think in the meantime I need to do a bit more reading about how the network maintains stability etc Best, Chris On 20 Oc

Re: [tor-relays] Botnet issues and upgrading to 0.2.4.x

3Mbps bandwidth use > for several hours when MaxAdvertisedBandwidth is 200 kbps). It seems > from past discussions on the mailing list, this is still an unresolved > issue. > > On Mon 14 Oct 2013 04:43:50 PM EDT, Chris Whittleston wrote: > > Thanks Logforme - yeah I was trying that before I

Re: [tor-relays] Botnet issues and upgrading to 0.2.4.x

help all! Chris On 14 October 2013 21:43, Chris Whittleston wrote: > Thanks Logforme - yeah I was trying that before I sent the first email in > this chain, but maybe I didn't go low enough with the advertised bandwidth. > When the 0.2.4 compilation is done (it's still

Re: [tor-relays] Botnet issues and upgrading to 0.2.4.x

Thanks Logforme - yeah I was trying that before I sent the first email in this chain, but maybe I didn't go low enough with the advertised bandwidth. When the 0.2.4 compilation is done (it's still chugging along) I'll try going lower and see if it helps. Chris On 14 October 2013

Re: [tor-relays] Botnet issues and upgrading to 0.2.4.x

I see - so I'll probably still see the problem with a huge number of circuits being created after I've finished building 0.2.4. Is there any way to limit this, I'm guessing reducing the bandwidth wouldn't actually help? I guess I'll look into how much further I can overclo

Re: [tor-relays] Botnet issues and upgrading to 0.2.4.x

Aha - makes sense, I'll just build it myself. Thanks for the quick response. So - the new handshake in 0.2.4.x doesn't help with the ongoing issues? On that page I linked it was suggested it might... Chris On 14 October 2013 20:33, Roger Dingledine wrote: > On Mon, Oct 14, 2013

[tor-relays] Botnet issues and upgrading to 0.2.4.x

tor: line 111: 972 https://www.torproject.org/docs/debian#development4 Illegal instruction $DAEMON $VERIFY_ARGS 1>&2 Tor is not starting and I'm unsure how to proceed - help appreciated! :) Chris ___ tor-relays mailing list tor-relays@lists.torpr

Re: [tor-relays] Sitevalley is no longer Tor-friendly

your call. A *lot* of people run bridge nodes there, myself included. -Chris (Running an exit relay in the US cost effectively seems quite difficult) On Thu, Jul 18, 2013 at 11:51 AM, mick wrote: > On Thu, 18 Jul 2013 10:49:46 -0400 > Tom Ritter allegedly wrote: > > > Sendi

Re: [tor-relays] Final Warning Notice

Lunar- On Wed, Jul 10, 2013 at 12:26 AM, Lunar wrote: > Chris Sheats: >> Hey tor-relays, >> >> The past few months, since I upgraded my net connection to 1Gbps, I've >> hit the top 40 fastest relays and the top 20 fastest exit nodes, >> peaking to over 17

Re: [tor-relays] Final Warning Notice

Mike- On Thu, Jul 11, 2013 at 8:43 AM, Mike Perry wrote: > Lunar: >> Chris Sheats: >> > Hey tor-relays, >> > >> > The past few months, since I upgraded my net connection to 1Gbps, I've >> > hit the top 40 fastest relays and the top 20 fastest exi

[tor-relays] Final Warning Notice

do apologize for any inconvenience this change may cause you. Please feel free to contact me directly if you have any questions. Sincerely, Operations Manager CondoInternet -- Chris Sheats yawn...@gmail.com ___ tor-relays mailing list to

Re: [tor-relays] Support for Relay Operators (signed)

What are the benefits/support of this network? Cheers On May 3, 2013 7:11 AM, "Moritz Bartl" wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > The last mail was not signed, because the Mail Merge addon does not > work together with Enigmail. Sorry. > > - cut > > Hi, > > I

Re: [tor-relays] Tor node monitoring

Sending your tor process a 'kill -USR1' yields a wealth of interesting info in the logs, although this isn't what you want I know :) On Tue, Apr 16, 2013 at 6:34 PM, Alex Beal wrote: > Hello All, > > I was wondering what, if any, software you use for monitoring your relays. > It would be nice

[tor-relays] Problems with Debian package and low ports

I am having some problems with tor (version 0.2.3.25-1), I get warnings when it resumes form hibernation: Feb 11 00:00:00.000 [warn] Could not bind to 0.0.0.0:80: Permission denied Feb 11 00:00:00.000 [notice] Opening OR listener on 0.0.0.0:443 Can anyone help?

Re: [tor-relays] iptables for relays not behind a nat

ufw status verbose sudo ufw reload And of course any other ports that you use, like I do serve my "This is an Exit Router" page from the same host, so: sudo ufw allow 80/tcp sudo ufw reload Cheers On Wed, Jan 30, 2013 at 12:29 PM, Chris Baines wrote: > Can anyone help with equi

[tor-relays] iptables for relays not behind a nat

Can anyone help with equivalents of the iptables rules given here https://trac.torproject.org/projects/tor/wiki/doc/TorFAQ#HowcanImakemyrelayaccessibletopeoplestuckbehindrestrictivefirewalls but for a relay on a vps with a static ip? Thanks, Chris

[tor-relays] Registration for tor relay list

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