Re: [tor-relays] High speed Tor relay advice

Hey, That's neat! Thanks for contributing. How many CPU's / CPU cores does this new server have and does it use AES-NI? How much RAM? Does it have multiple public IP addresses? Currently it's complicated for a single Tor process to saturate a 10Gb/s line, because it's not yet able to use all CPU

Re: [tor-relays] High speed Tor relay advice

CPU: 6x Xeon E5-2620v3 vCores > RAM: 10GB > > I only get one IP address to myself by default. I could probably get > more though if I feel it is worth it. > > > On 14/08/16 15:27, s7r wrote: >> Hey, >> >> That's neat! Thanks for contributing. >> &g

Re: [tor-relays] Do middle nodes create multiple connections to the same Exit node? (with different source port)

It should open a single connection with the exit node (TLS link) and use that link for multiple (as many as needed) circuits. So if there are two users using the same middle node and same exit simultaneously, the middle node should have one connection to the exit node (TLS link) with two different

Re: [tor-relays] Useful metrics for relay operators

On 9/1/2016 12:18 PM, patacca wrote: [SNIP] > > I would find very useful a mail notification when the ed25519 key's > expiration date is near and the OfflineMasterKey is enabled. > Also if the expiry information could be shown on atlas that would be nice. The expiration date of the temporary ed2

Re: [tor-relays] Moving multiple instances to another VPS

Hello, Thanks for running exits! Pay attention that each instance has its own datadirectory, this means you need to have multiple 'keys' subdirectories depending on the number of your instances. Usually /var/lib/tor should contain some subfolders like 1, 2 or instance1, instance2, whatever and ea

Re: [tor-relays] Question about relay speed

On 10/3/2016 12:00 AM, Green Dream wrote: > You could also turn the old relay into a bridge. I've read that low > bandwidth machines are often better serving the network as bridges, > although I don't know what the cutoff value for "low bandwidth" is in > this case. I recommend, if you decide to

Re: [tor-relays] Second relay on same ESX

Hello, Thanks for running relays. Patrick DERWAEL wrote: > Hi guys, > > I'm running a relay in a VM on a physical server which is largely under used > Current advertised bandwidth 26MB, consensus 76500 > I'm considering running a second relay (2nd VM) on the very same > hardware, but this bring

Re: [tor-relays] Changing exit to bridge

Volker Mink wrote: > Thanks so far. > Does it keep my stats in Atlas when i change it from an exit to a bridge? > What do i have to change in the torrc-file? > > https://atlas.torproject.org/#details/E20FF09A9A800B16C1C7C16E8C0DF95F46F649B0 > Note that if the IP address was an exit relay or rela

Re: [tor-relays] Another relay is using the same name as mine.

Alan wrote: > I just need some advice. I'm running 3 relays, one is called Andromeda. > Today I find out there is another relay called Andromeda. > > https://atlas.torproject.org/#search/Andromeda > mine is running from ip 144.217.161.119 > > Is it a problem with relays using the same name? > Sho

Re: [tor-relays] "Bug: Duplicate call to circuit_mark_for_close"

tor wrote: > Hi, > > I'm troubleshooting a Linux relay where the Tor service is having > problems. External monitoring alerts indicate both the ORPort and > DirPort are unreachable (TCP connection timeout). I can ssh in and the > Tor service is still running. The node seems to have increased memor

Re: [tor-relays] decrease in traffic

Hi, Trey Nolen wrote: > I'm new to running a Tor relay and started one about a month ago.   I've > got 50 Mbps dedicated to it and at first it climbed in traffic pretty > steadily until it got to around 25-30 Mbps being used.   Since then, it > has declined steadily and is down to about 350 KBps n

Re: [tor-relays] decrease in traffic

Trey Nolen wrote: > >> First of all, thanks for running a relay. >> >> Based on my experience, what usually happens is that the provider of >> your VPS observed during a period of time you used more than N mbps >> constantly and all the time, so they capped your VPS at some KB/s limit. >> There a

Re: [tor-relays] So long and thanks for all the abuse complaints

Zack Weinberg wrote: > On Mon, Dec 4, 2017 at 10:57 AM, Ralph Seichter > wrote: >> On 04.12.17 11:59, James wrote: >> >>> As a private individual, after just receiving my 4th abuse complaint >>> in as many days it's time to stop running my exit node. >> Thanks for running the exit and I am sorry

Re: [tor-relays] [err] tor_assertion_failed_(): Bug: src/or/connection.c:5113

Hi, This looks like it's worth a ticket on trac. I've searched and there are no open reports about this, just a ~5 year old one that is closed (#9017). So this happened only when you had IPv6Exit enabled (1) and you had to switch to 0 to avoid it? Toralf Förster wrote: > Got this today: > > Fe

Re: [tor-relays] Tor Relay Setup

Gabe D. wrote: > Feb 24 10:45:08.668 [notice] Tor 0.3.2.9 (git-64a719dd25a21acb) running on > Linux with Libevent 2.0.19-stable, OpenSSL 1.0.1t, > Zlib 1.2.7, Liblzma N/A, and Libzstd N/A. > Feb 24 10:45:08.668 [notice] Tor can't help you if you us

Re: [tor-relays] whonix tor-relay - help needed

peter.zehet...@liwest.at wrote: > Hi there! > > I try to configure a tor relay on an whonix-gateway but I allways > receive the answer that my server has not managed to confirm that its > ORPort and its DIRPort are rechable. > > How can I fix this? > > Thanks Peter > If you're using whonix-gat

Re: [tor-relays] default exit notice HTML page on exits?

nusenu wrote: > > > Eran Sandler: >> I certainly think it should be added by default. > > I agree that an html page giving some basic information about > tor on every exit relay IP makes sense. > > If there are no major concerns from other operators to enable > this _by default_ I will open a

Re: [tor-relays] Directory Server and bandwidth accounting

f traffic, seriously. My 100mbit relays made on virtual servers consume 6-7TB of total traffic per month. Use the accountingmax argument and you should be fine, it's better than capping bandwidth and it is a great help for the network. Thanks for running a relay. - -- s7r PGP Fingerprint:

[tor-relays] optimize performance of a relay running on a VM

this can be improved, but how? The servers have only purpose Tor, there is nothing else running on them and there is no bandwidth cap or throttling. Suggestions? Thanks in advance. - -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11 -BEGIN PGP SIGNATURE- Version

Re: [tor-relays] optimize performance of a relay running on a VM

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 7/1/2014 10:07 PM, Random Tor Node Operator wrote: > On 07/01/2014 08:46 PM, s7r wrote: >> I have multiple relays running on the following systems: - >> vmware vsphere virtualization technology - 100 mbps port - 1GB >> dedi

Re: [tor-relays] Running tor in VPS - keep away snooping eyes

rity and protection against weak password probing. - - do not allow any other users for SSH access. Let me know if you have any other questions. - -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32)

Re: [tor-relays] Running tor in VPS - keep away snooping eyes

lse too and you have some sensitive data there, it is always a good idea to encrypt everything... but in your scenario full disk encryption will not help since you are exposed to physical attacks (e.g. someone caching your files while your virtual machine is RUNNING, making full

Re: [tor-relays] Running tor in VPS - keep away snooping eyes

gt; performance issues? I ask specifically because I run in a VPS where > resources are limited (compared to a proper machine). > > - kali- > > ___ tor-relays mailing > list tor-relays@lists.torproject.org > https://l

Re: [tor-relays] Running tor in VPS - keep away snooping eyes

because I run in a >>> VPS where resources are limited (compared to a proper >>> machine). >>> >>> - kali- > >> >> Depends, what configuration will that virtual machine have? You >> shouldn't notice too big of a difference, full disk

Re: [tor-relays] German company Webtropia: Terminated contract without notice because of abuse

lays > uf I had the same problem with other ISP. Required me to register my own /24 subnet (256 ip addresses) RIPE allocated if i wanted to continue running exits in their network. Currently working on this.Choose a different provider if you wish to continue running exits. need recommendations

Re: [tor-relays] Exit node dropped to near zero weight

xplains it, in a way. Just give some more time to run and it should be OK. I saw your advertised bandwidth is 512KB/s - that is reasonable, but the higher you can give to your relay, the better and the bigger consensus weight it will have. - -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1

Re: [tor-relays] Advertised Bandwidth

RelayBandwidthBurst). It cannot reach the maximum in few days. I have a relay running for 10 days, I haven't set any limit o it (it has a full 100mbps port) and atlas shows it 650KB/s so - waiting is the only thing you need to do. - -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 302

Re: [tor-relays] icetor's loki2 update status (CVE-2014-5117)

rything fine and accurate, just atlas and globe have lag. Someone needs to look into them. - -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJT8qeHAAoJEIN/pSyBJlsRBH0IAL2kdARDPoJ4lyZ8EJ

Re: [tor-relays] Centos 7

irectly if you have questions. Make sure you add repos properly to avoid package name collisions. - -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJT/1

[tor-relays] boost CPU on a Tor relay

processor 1 - processor 7 Any ideas how this could be boosted? OS is Debian wheezy. No aes-ni hardware acceleration, no openssl benchmarking or customization currently. advices? Thank you. - -- s7r PGP Fingerprint: 7C36 9232 5ABD FB0B 3021 03F1 837F A52C 8126 5B11 -BEGIN PGP SIGNATURE

Re: [tor-relays] boost CPU on a Tor relay

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 9/9/2014 2:43 PM, Moritz Bartl wrote: > On 09/09/2014 01:28 PM, s7r wrote: >> A Tor relay currently going 33MB/s could go a lot faster but CPU >> is at 93% usage - this is the bottleneck. Here is the output of >> /proc/cpuinf

Re: [tor-relays] RELAY_EARLY tor network update status (CVE-2014-5117)

.org/#details/B83DC1558F0D34353BB992EF93AFEAFDB226A73E > https://atlas.torproject.org/#details/104A9453FD93BDBEAE9E2024898266AD2051A1BD > > https://atlas.torproject.org/#details/C11650E31F83E149C855D574B3171CC9CF9BEE19 > > _______ tor-relays

Re: [tor-relays] Bandwidth not being used by Tor on Gigabit dedicated server

ess than 15% capacity, 99% of the > time. > > CPU load is always at 0.00. Based in the USA, west coast. > > Ideas? Is there simply less demand for tor traffic in the US? > > Cheers, Jon > > > ___ tor-relays

Re: [tor-relays] Few questions about relaying

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Can you please copy/paste your entire torrc to a pastebin and provide us the link? It is hibernating only if you use accounting. Provide us your entire complete torrc and we will correct it for you if you don't have traffic limits on your server. On

Re: [tor-relays] Few questions about relaying

GMT-04:00 s7r <mailto:s...@sky-ip.org>>: > > Can you please copy/paste your entire torrc to a pastebin and > provide us the link? > > It is hibernating only if you use accounting. Provide us your > entire complete torrc and we will correct it for you if you don&#x

Re: [tor-relays] Few questions about relaying

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 If you don't want to rate-limit, remove RelayBandwidthBurst and RelayBandwidthRate lines. On 10/11/2014 5:24 PM, Blaise Gagnon wrote: > 0.2.5.8-rc yup I'm trying this torrc and will get back to you. > > Thanks s7r ! > > 2

Re: [tor-relays] Tor 0.2.5.10 is released!

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/26/2014 9:06 AM, goll wrote: >> Which package exactly? I'm guessing you're using the deb? Which >> OS? What CPU architecture? > > No, using the rpm, CentOS 6, x86_64. > >> >> The next question would be whether you somehow disabled your >> c

Re: [tor-relays] Call for obfs4 bridges, and a brief discussion of obfs4proxy.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/28/2014 12:24 AM, Steve Snyder wrote: > Does obfs4 support IPv6 addresses? If so, does it work like ORPort > in that it is just a matter of adding another line? > > Yes. > For example, to add an IPv6 address can I just replace > > ServerTr

Re: [tor-relays] Relay's clock settings off no matter what

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Austin, The clock is very important to Tor, you need accurate clock all the time. Do you run NTPDATE or NTPD service inside your VPS? The virutal servers are sometimes problematic, depending on virtualization, when coming to hwclock and dedicat

Re: [tor-relays] Relay's clock settings off no matter what

to set the correct time on a host server... On 11/14/2014 12:49 PM, eric gisse wrote: > If your vps provider is openvz, you are shit out of luck because > you can't set time. > > On Fri, Nov 14, 2014 at 4:37 AM, s7r wrote: Hello > Austin, > > The clock is very important

Re: [tor-relays] wild swings in Advertised Bandwidth

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 That does not necessarily mean your bridge works with max. 8 kB/s. Maybe the bridge is not used much currently (most probably if it's new). The minium BandwidthRate of 20kB/s you read is correct, I think it should be at least 200kB/s minimum. Back to

Re: [tor-relays] Fast Exit Node Operators - ISP in US

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I also share the thought that more US exit power is welcomed in the Tor network. However, the fact that there is more exit power in the EU compared to the US has nothing to do with the legal implications of running a Tor exit, it's as simple as bandwi

Re: [tor-relays] Fast Exit Node Operators - ISP in US

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Just checked them now, that is great if they will allow you to run Tor exit nodes on such cheap virtual machines. 5$ for 1000GB is a good deal for US traffic, and bitcoin accepted is an important pro. But I am concerned if they will sustain Tor exits o

Re: [tor-relays] Fast Exit Node Operators - ISP in US

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 That is, because in almost all cases, providers allow unmetered incoming traffic to your server but keep count and accounting on outgoing traffic from your server, which is why the torrc setting acts the way it does. On 11/23/2014 7:58 PM, Seth wrote

Re: [tor-relays] Fast Exit Node Operators - ISP in US

't have to pay extra) and see what what speed it reaches. On 11/24/2014 5:24 AM, Mirimir wrote: > On 11/23/2014 11:05 AM, s7r wrote: >> That is, because in almost all cases, providers allow unmetered >> incoming traffic to your server but keep count and accounting on >&g

Re: [tor-relays] Fast Exit Node Operators - ISP in US

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 11/24/2014 7:32 PM, Mirimir wrote: > On 11/24/2014 03:06 AM, s7r wrote: >> If the only limit is consumed monthly traffic, and not the >> bandwidth your relays consumes daily (e.g. you use your VPS only >> for Tor) it is no

Re: [tor-relays] Help - My relay consensus has been stripped back to 20

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This was reported yesterday 01.01.2015 in IRC too, for this relay: 3D7E274A87D9A89AF064C13D1EE4CA1F184F2600 The same it was pushing good amounts of traffic and the consensus weight dropped to 20 with no modifications made to the Tor config file or an

Re: [tor-relays] Mozilla-Middles losing guard

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 The speed matters. Some time ago, Guard flag parameters were changed little bit, so now the Guard flag is assigned to 25% of the fastest relays in the network (of course which are also stable and have good uptime and have been around in the network f

Re: [tor-relays] eventdns: Address mismatch on received DNS packet.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 We have a ticket open for this: https://trac.torproject.org/projects/tor/ticket/11600 I think this is a libevent error. It happened to me on FreeBSD 10 with Bind910, FreeBSD 10 with Unbound, Debian Wheezy with Unbound, Debian Wheezy with Bind, Deb

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, Sorry to hear this. I want to setup a big node at Voxility, which is a good provider to host Tor exits, maybe more of us can pool together financial resources and make a big cluster. I have some offers from them if interested. On 2/25/2015 8

Re: [tor-relays] Legal situation of tor in Europe

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 3/9/2015 1:17 PM, Sebastian Urbach wrote: > On March 9, 2015 7:17:20 AM oneoft...@riseup.net wrote: > > Hi John, > >> Can someone point me to an overview of the different legal >> situations for running tor relays in European countries? I'm >>

Re: [tor-relays] relay behind reverse proxy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 If you are using the free nginx, community project, that will only allow you to deploy a http(s) proxy. Only the commercial (paid) nginx allows you to deploy a TCP proxy (handles all TCP traffic), which is what you need for a Tor relay. If you want

Re: [tor-relays] Legal situation of tor in Europe

server is properly secured. If your SSH port is 22, password authentication enabled, and your root password is 12345 . ta-ta. On 3/9/2015 4:40 PM, Markus Hitter wrote: > Am 09.03.2015 um 15:13 schrieb s7r: >> This is a speculation and it's not backed up by anything real. >&

Re: [tor-relays] relay behind reverse proxy

works this way. On 3/9/2015 7:50 PM, efkin wrote: > > > On 03/09/2015 03:35 PM, s7r wrote: >> If you are using the free nginx, community project, that will >> only allow you to deploy a http(s) proxy. Only the commercial >> (paid) nginx allows you to deploy a TCP p

Re: [tor-relays] relay behind reverse proxy

. Publishing server descriptor. > > [notice] Performing bandwidth self-test...done. > > but nothing else on the logs since half an hour... > > does it mean it is working? > > thx for support! > > On 03/09/2015 10:03 PM, s7r wrote: >> Hi again > >> I don&

Re: [tor-relays] Installing obfs4 on Raspberry Pi bridge

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, obfs4 will not run on 0.2.4.x , you need at least 0.2.5.x or 0.2.6.x First, upgrade your Tor. You can use torproject.org repositories. If you are running wheezy: 1. Add the repository: # echo "deb http://deb.torproject.org/torproject.org whee

Re: [tor-relays] Installing obfs4 on Raspberry Pi bridge

t; J. Chase > > > tor-relays-requ...@lists.torproject.org: >> Message: 4 Date: Sun, 29 Mar 2015 00:19:14 +0200 From: s7r >> To: tor-relays@lists.torproject.org Subject: >> Re: [tor-relays] Installing obfs4 on Raspberry Pi bridge >> Message-ID: <551728e2.4030

Re: [tor-relays] amount of unmeasured relays continuously rising since 2 weeks

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi nusenu, Again thanks for keeping an eye on things. At least partially, the balance of measured/unmeasured should be fixed in the new few days. To relay operators, in the mean time, please bare for few more days and sorry for the inconvenience, I

Re: [tor-relays] How to use our own TOR relay as entry node for local network hosts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, On 5/20/2015 12:07 PM, Tor User wrote: > Hello, > > We have been operating a moderately successful public tor relay for > a while now. Having read about how TOR works back a couple of > years ago, I was more or less sold on the idea that i

Re: [tor-relays] amount of unmeasured relays continuously rising since 2 weeks

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Julian Thanks for your contribution to Tor! Please keep them running, as much as you can. We already struggle to (at least partially) solve the issue for the short term, by launching more bandwidth authorities. On the long term, some research

Re: [tor-relays] How to use our own TOR relay as entry node for local network hosts

client and don't use proxy setting, connect directly with StrictNodes and EntryNode. Cheers! On 5/23/2015 3:14 PM, Tor User wrote: > Hi s7r, > > Thank you for your reply. There's a lot of good info in it and > I'll be reconfiguring the clients. > > The fact

Re: [tor-relays] Raspberry Pi - Relay Setup

Just install Tor: sudo apt-get -y install tor and edit the torrc file: nano /etc/tor/torrc make it a relay by adding this content (add your values and data): ORPort Nickname ContactInfo ExitPolicy reject *:* *If you are behind NAT, make sure the ports are properly forwarded to your raspberry

Re: [tor-relays] Problems with second/third relay

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Thanks for adding one more relay. It's ok to have 2 relays on one IP address, both should work. What do you mean you have enabled DMZ and port forwarding? If you enable DMZ, that will forward ALL ports to 1 IP address in the subnet (NAT). Y

Re: [tor-relays] be in time or not to be in time ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I used to receive this message regularly from time to time on a KVM virtual machine running Debian 7 Wheezy (Tor exit relay). NTP process was working fine, no errors. I did manually: # service ntp stop # ntpdate 0.rhel.pool.ntp.org # service ntp sta

Re: [tor-relays] Question about responding to abuse request

Hi, Usually those are automated messages. I get them all the time as well. They are just relaying abuse messages. The text in their message is standard, and includes all cases so to say. If you scroll down the email, you will see the target IP and few logs. Usually this is the result of automated

Re: [tor-relays] pinning relay keys to IPs (or not)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello Yawning, We need to confirm this: is a relay holding TLS connections to the majority of the other relays? On a relay with over 100 days of uptime (middle relay) Stable, HSDir, etc. I have (# netstat -a | wc -l) 1942 connections. Another one,

Re: [tor-relays] relay's count handshake versions, why not TLS handshake types?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, I think that is to maintain a backward compatibility. Tor tries as hard as possible to maintain backward compatibility with older versions, unless something critical which requires deprecation regardless some relays will disappear from the co

Re: [tor-relays] BWauth no-consensus state in effect

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, That is correct Mike Perry - (at least in my case) Tor is much slower (any page takes more time to load) than when bandwidth authorities were assigning weights. This happens on 2 different client computers and one live Tails (obviously each uses

Re: [tor-relays] do not run Tor client and OR relay together!

Hi, Shipping tor-client and tor-relay as separate packages is the worst thing we could do, since it's the same thing with just one config line more or less. It will mess things up terribly. We don't know that just yet, we are getting to fast from one thing to another - wait until proper review ov

[tor-relays] Calling for more Exit Relays

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, In the last 48 hours we went under the 'psychological' threshold of 1000 Exit Relays in the consensus. Right now, Thu Aug 20 23:57:02 UTC 2015, we have: 6234 Running relays 954 Exit relays I think we can improve this balance. Let's do it!

Re: [tor-relays] Google Compute Engine rejected as relay?

Hi Greg, I have forwarded the request to the relevant people. Please stand by to get an update about it as soon as possible. On 8/20/2015 5:17 PM, Greg wrote: > > > On Wed, Aug 19, 2015 at 10:46 PM, Thomas White > wrote: > > I think this is from the Lizard Squa

Re: [tor-relays] Does Setting Up a Bridge Relay Disable the Browser?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Thanks for this. But why do you want to run your bridge instance among the same Tor daemon as the one handling Tor Browser? If you are on Debian, install Tor package separately with apt-get install tor (recommended you add deb.torproject.org to

Re: [tor-relays] Legal status of operating Tor exit in UK?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, I am not from UK so I am also not familiar with the legislation there, but running an exit should be perfectly fine. Your ISP cannot "press" you to do anything! Only a govt. authority or law enforcement authority or judge can legally press y

Re: [tor-relays] excessive bandwidth assigned bandwidth-limited exit relay

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, Don't cap the speed if you have bandwidth limits. The better way to do it is using AccountingMax in torrc. Just let it run at its full speed less of the time and Tor will enter in hibernation once it has no bandwidth left. Example: remove Re

Re: [tor-relays] excessive bandwidth assigned bandwidth-limited exit relay

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Ouch, that's wrong. "BandwidthBurst" and "BandwidthRate" refer to bandwidth consumed by Tor as a client, e.g your localhost SOCKS5. If you are trying to limit RELAYED traffic, as in sent and received by your relay functionality you should use: "Rela

Re: [tor-relays] excessive bandwidth assigned bandwidth-limited exit relay

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 You only mentioned the 100TB plan limit, this is why I suggested AccountingMax. I couldn't have guessed you are talking about some other policy limits. The consensus weight is your bandwidth measured by the bandwidth authorities. This is used by cli

Re: [tor-relays] why are some exit IPs missing from Exit IP DB?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Don't know if we can call it a bug. It appears to be working, real exit IP addresses are discovered. Check for example: PrivacyRepublic0001 178.32.181.96 PrivacyRepublic0002 178.32.181.97 Both exit with IP: 37.187.129.166 It actually works very goo

Re: [tor-relays] why are some exit IPs missing from Exit IP DB?

cking the wrong IP and not reading the post. > > > At 01:45 10/12/2015 +0300, s7r wrote: >> Check for example: PrivacyRepublic0001 178.32.181.96 > > > At 13:29 10/8/2015 -0400, starlight.201...@binnacle.cx wrote: >> Occasionally I run into a relay such as >> &g

Re: [tor-relays] Faravahar messing with my IP address

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, Unfortunately this is not the first time we see this, and it did happen before Faravahar IP address change and before it was experiencing very high latency ( https://trac.torproject.org/projects/tor/ticket/17338 ). See: https://trac.torproje

Re: [tor-relays] too many circuit creation requests

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, Thanks for running a relay. Yes, the raspberry CPU is kind of slow for Tor, especially if you are using the old raspberry-pi with arm-v6 cpu and 512MB of ram. RelayBandwidthRate and RelayBandwidthBurst settings are ok, you might want to incr

Re: [tor-relays] too many circuit creation requests

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, I have checked on atlas and your HSDir flag is gone, so if those additional circuits where HSDir requests, they won't appear any longer. However, keep in mind that this doesn't happen immediately. Some clients might still use the old consensus

Re: [tor-relays] Limiting Bandwidth

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Thanks for running a relay. I recommend adding these lines in your torrc file: AccountingMax 1050 GBytes AccountingStart month 1 00:00 On 11/12/2015 12:59 AM, Billy Humphreys wrote: > > Hi all, does anyone know how to make a tor relay only

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

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, The estimated extra load looks good, it shouldn't be a problem. Are we entirely sure we want to hardcode a static weight for each fallback directory relay? I know we require it to be stable enough but sometimes the weight assigned to a relay is

Re: [tor-relays] Tor not reading medium-term signing key.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, Let's recap (hope I am not missing something): a) you make sure master_id_secret_key is available in /home/[user]/.tor/keys b) you run # tor --keygen and provide the correct passphrase c) you *move* the newly generated ed25519_signing_secret

Re: [tor-relays] Tor not reading medium-term signing key.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 1/5/2016 12:13 AM, 12xBTM wrote: > Now I'm getting permission denied, still out-dated key, and > missing master_id_secret_key errors, which are unsurprisingly > fatal. > > Jan 04 22:41:33.000 [warn] Could not open > "/var/lib/tor/keys/ed25519_s

Re: [tor-relays] Why is Tor trying to check the wrong ORPort/DirPort addresses?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, I have experienced exactly the same problem with similar networking configuration and reported it here: https://trac.torproject.org/projects/tor/ticket/13953 It's being worked on. In your case, however, it appears that the Address argument

Re: [tor-relays] Nameservers fail and come back at the same time?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, This isn't new, and it happens with any DNS resolver (ISP resolver, Google or OpenDNS, custom DNS resolver on localhost running unbound or bind, etc.). I have experienced it on all the exits I ever run, it's the most common warning. There's

Re: [tor-relays] Issues with offline master key functionality

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello - see inline On 2/3/2016 3:49 PM, Riccardo Mori wrote: > Hi everyone, > > Two months ago I decided to try the new ed25519 key introduced in > Tor 2.7 with OfflineMasterKey set so I can keep the master key in > a different place and just uploa

Re: [tor-relays] Tor Process Being Killed on VPS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, More information is needed. Please indicate the type of virtualization used (VMware, Xen, KVM, OpenVZ), your operating system and Tor version as well as the "out of memory" log messages you mentioned - are these from kernel logs or Tor's log

Re: [tor-relays] Bandwidth Fallen Off Drastically

Hello, Your relay seams fine on atlas: http://atlas777hhh7mcs7.onion/#details/A290A9E71ADFC2FB1C80E64EF851A4B905450105 It has an observed bandwidth of 582.23 KB/s Advertised bandwidth of 512 KB/s and burst 716.8 KB/s Which is exactly as per your configuration. The consensus weight is 613, whi

Re: [tor-relays] Who operates the bridge with nickname antirio?

-alpha git 1f679d4ae11cd976+26ab2e0 - I assume your patch isn't merged already? -s7r On 3/27/2016 10:11 AM, Karsten Loesing wrote: > Hi everyone, > > does anybody here know who operates the bridge with nickname antirio? > > https://atlas.torproject.org/#details/16609212922F6F1077A

Re: [tor-relays] TORRC Exit not obeying httproxy

Hi, First, thanks for running a relay. Those settings do not ensure the EXIT traffic generated by your server goes via any proxy. OutboundBindAddress IP - this is the IP address Tor will use for outgoing connections. This is the IP address which will be seen by destinations accessed by Tor clien

Re: [tor-relays] Handling abuse - like to get your help please

Hello, Thanks for running an exit relay. That is just an automated email message. You do not want to reply to every single automated message you receive, firstly because these replies go into a black hole and they are not read by any humans, so your effort may be useless. Generally, you should on

Re: [tor-relays] [warn] eventdns: All nameservers have failed

Hello, This warn is known for some time. It's safe to ignore this warning no matter how many times you see it in your log file, IIRC it's a libevent issue when DNS resolvers are idle. All my exit relays have multiple such lines in the log files constantly. It's highly important to run your own re

Re: [tor-relays] suspicious "Relay127001" relays

On 7/6/2016 4:50 PM, Ivan Markin wrote: > Andreas Krey: >> That will cause issues for everyone that happens to select your >> relay and the 'blocked' relays in a circuit - the connections will >> just fail, and the user will wonder what happened, and why TBB >> doesn't work. > > Sure, I made a not

Re: [tor-relays] Questions about Tor consensus weight & swag

shruub via tor-relays wrote: I also (stupidly) tried to have a cron restarting my tor daemon daily which also resulted in the latter. So I wonder, if there is any way to have a relay run more stable and I suppose with a somewhat higher consensus weight (I can only asssume making some further chan

Re: [tor-relays] Comcast blocks ALL traffic with tor relays

xmrk2 via tor-relays wrote: Any ideas on how to combat this? I was thinking about including some false positives in tor relay list. Imagine including some Google servers' IP addresses - Comcast customers suddenly cannot connect to Google, unless Comcast stops this blocking... or simply whitelis

Re: [tor-relays] Middle relay IP blocking

li...@for-privacy.net wrote: On Samstag, 5. August 2023 08:40:42 CEST Marco Predicatori wrote: secureh...@gmail.com wrote on 8/4/23 01:46: I tried reporting a similar issue a few months ago (post wasn’t approved by moderator). I was running a relay from my home ISP. After a short while certain

Re: [tor-relays] Running an exit relay in Italy

Eldalië via tor-relays wrote: Hello there and thanks everyone for your answers to my message about middle relay blocking. Reading them I feel trying to solve the blacklisting of my IP would be overkilling. Since I have a chance to get a cheap VPS, I will try to migrate the relay on it. And since

[tor-relays] obfs4 bridge current setup is not entirely clear

Hi, I ran into some new IP space and I decided to change a cluster of obfs4 bridges that are more than 4 year old. When I set them up I don't remember spending so much time. So, Debian latest and Tor latest from deb.torproject.org nightly. GoLang from the official website (as it's the latest

  1   2   >