Hi, I have a Tor relay (https://atlas.torproject.org/#details/342587A287603040A49BB364D72EAC0B6BC3D7...) running from a FreeBSD server at my house on with a 5 megabit upstream connection.
I have seen that lately, Tor's "Consensus Weight" value on this relay has not been going anywhere above (or below) 20. My relay has gotten the "Stable" flag, but yet didn't see it's consensus weight value rise.
I decided to look at https://consensus-health.torproject.org/, and saw that two of the four bandwidth consensus servers, namely tor26 (86.59.21.38) and longclaw (199.254.238.52) don't seem to be calculating any consensus value for Tor relays in the last few days.
Has anyone else been having this problem? And if the Tor consensus operators are reading this, (approximately) when would this problem get resolved?
Thanks, Neel Chauhan
yes
I have experienced the same problem on my exit relay: DDC6C968B3DFD156C97FD71808758D251B66DBB2
My relay lost the stable flag due to a inadvertent shut-down a few days back.
LB
On 5/9/2015 1:38 PM, Neel Chauhan wrote:
Hi, I have a Tor relay (https://atlas.torproject.org/#details/342587A287603040A49BB364D72EAC0B6BC3D7...) running from a FreeBSD server at my house on with a 5 megabit upstream connection.
I have seen that lately, Tor's "Consensus Weight" value on this relay has not been going anywhere above (or below) 20. My relay has gotten the "Stable" flag, but yet didn't see it's consensus weight value rise.
I decided to look at https://consensus-health.torproject.org/, and saw that two of the four bandwidth consensus servers, namely tor26 (86.59.21.38) and longclaw (199.254.238.52) don't seem to be calculating any consensus value for Tor relays in the last few days.
Has anyone else been having this problem? And if the Tor consensus operators are reading this, (approximately) when would this problem get resolved?
Thanks, Neel Chauhan
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
hey,
can you do me a favor and remove the exit status of your relay and turn it into a regular node? I experienced the same problem as you:
https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F26...
but ever since I removed the exit-flag I am generating some consensus rating again. This problem first popped during the last days of 2014 and up until now there hasn't been any reliable fix. Apparently even deleting the ID of your tor-node didn't help according to one user.
On 10.05.2015 07:05 AM, Larry Brandt wrote:
yes
I have experienced the same problem on my exit relay: DDC6C968B3DFD156C97FD71808758D251B66DBB2
My relay lost the stable flag due to a inadvertent shut-down a few days back.
LB
On 5/9/2015 1:38 PM, Neel Chauhan wrote:
Hi, I have a Tor relay (https://atlas.torproject.org/#details/342587A287603040A49BB364D72EAC0B6BC3D7...) running from a FreeBSD server at my house on with a 5 megabit upstream connection.
I have seen that lately, Tor's "Consensus Weight" value on this relay has not been going anywhere above (or below) 20. My relay has gotten the "Stable" flag, but yet didn't see it's consensus weight value rise.
I decided to look at https://consensus-health.torproject.org/, and saw that two of the four bandwidth consensus servers, namely tor26 (86.59.21.38) and longclaw (199.254.238.52) don't seem to be calculating any consensus value for Tor relays in the last few days.
Has anyone else been having this problem? And if the Tor consensus operators are reading this, (approximately) when would this problem get resolved?
Thanks, Neel Chauhan
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hey I have almost the same problem with my relay (https://atlas.torproject.org/#details/DABC2440E9EAAEDB23F150CF95656405917A78...) I stuck to Consensus Weight: 20 since over one week. If I look at the "collected data“ I se the „unmetered = 1“ comment. :(
Any Ideas how to fix this? Is this the normal and wanted behavior?
Best regards, Marcus
Am 10.05.2015 um 13:54 schrieb Network Operations Center noc@schokomil.ch:
hey,
can you do me a favor and remove the exit status of your relay and turn it into a regular node? I experienced the same problem as you:
https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F26...
but ever since I removed the exit-flag I am generating some consensus rating again. This problem first popped during the last days of 2014 and up until now there hasn't been any reliable fix. Apparently even deleting the ID of your tor-node didn't help according to one user.
On 10.05.2015 07:05 AM, Larry Brandt wrote:
yes I have experienced the same problem on my exit relay: DDC6C968B3DFD156C97FD71808758D251B66DBB2 My relay lost the stable flag due to a inadvertent shut-down a few days back. LB On 5/9/2015 1:38 PM, Neel Chauhan wrote:
Hi, I have a Tor relay (https://atlas.torproject.org/#details/342587A287603040A49BB364D72EAC0B6BC3D7...) running from a FreeBSD server at my house on with a 5 megabit upstream connection. I have seen that lately, Tor's "Consensus Weight" value on this relay has not been going anywhere above (or below) 20. My relay has gotten the "Stable" flag, but yet didn't see it's consensus weight value rise. I decided to look at https://consensus-health.torproject.org/, and saw that two of the four bandwidth consensus servers, namely tor26 (86.59.21.38) and longclaw (199.254.238.52) don't seem to be calculating any consensus value for Tor relays in the last few days. Has anyone else been having this problem? And if the Tor consensus operators are reading this, (approximately) when would this problem get resolved? Thanks, Neel Chauhan _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I had a look at https://collector.torproject.org/recent/relay-descriptors/consensuses/2015-0... There you can find 874 relays with the „flag“ "Bandwidth=20 Unmeasured=1“… I don’t think this is normal… Can anybody have a look at this?!
Best regards, Marcus
Am 10.05.2015 um 16:47 schrieb Marcus Wahle marcus.freifunk@gmx.de:
Hey I have almost the same problem with my relay (https://atlas.torproject.org/#details/DABC2440E9EAAEDB23F150CF95656405917A78...) I stuck to Consensus Weight: 20 since over one week. If I look at the "collected data“ I se the „unmetered = 1“ comment. :(
Any Ideas how to fix this? Is this the normal and wanted behavior?
Best regards, Marcus
Am 10.05.2015 um 13:54 schrieb Network Operations Center noc@schokomil.ch:
hey,
can you do me a favor and remove the exit status of your relay and turn it into a regular node? I experienced the same problem as you:
https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F26...
but ever since I removed the exit-flag I am generating some consensus rating again. This problem first popped during the last days of 2014 and up until now there hasn't been any reliable fix. Apparently even deleting the ID of your tor-node didn't help according to one user.
On 10.05.2015 07:05 AM, Larry Brandt wrote:
yes I have experienced the same problem on my exit relay: DDC6C968B3DFD156C97FD71808758D251B66DBB2 My relay lost the stable flag due to a inadvertent shut-down a few days back. LB On 5/9/2015 1:38 PM, Neel Chauhan wrote:
Hi, I have a Tor relay (https://atlas.torproject.org/#details/342587A287603040A49BB364D72EAC0B6BC3D7...) running from a FreeBSD server at my house on with a 5 megabit upstream connection. I have seen that lately, Tor's "Consensus Weight" value on this relay has not been going anywhere above (or below) 20. My relay has gotten the "Stable" flag, but yet didn't see it's consensus weight value rise. I decided to look at https://consensus-health.torproject.org/, and saw that two of the four bandwidth consensus servers, namely tor26 (86.59.21.38) and longclaw (199.254.238.52) don't seem to be calculating any consensus value for Tor relays in the last few days. Has anyone else been having this problem? And if the Tor consensus operators are reading this, (approximately) when would this problem get resolved? Thanks, Neel Chauhan _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi,
This is a known problem; the bandwidth authorities need to be worked on. See for example
https://trac.torproject.org/projects/tor/ticket/13450 https://trac.torproject.org/projects/tor/ticket/4359
There's no timeline set yet on when this will be fixed.
On 05/10/2015 09:48 PM, Marcus Wahle wrote:
I had a look at https://collector.torproject.org/recent/relay-descriptors/consensuses/2015-0... There you can find 874 relays with the „flag“ "Bandwidth=20 Unmeasured=1“… I don’t think this is normal… Can anybody have a look at this?!
Best regards, Marcus
Am 10.05.2015 um 16:47 schrieb Marcus Wahle marcus.freifunk@gmx.de:
Hey I have almost the same problem with my relay (https://atlas.torproject.org/#details/DABC2440E9EAAEDB23F150CF95656405917A78...) I stuck to Consensus Weight: 20 since over one week. If I look at the "collected data“ I se the „unmetered = 1“ comment. :(
Any Ideas how to fix this? Is this the normal and wanted behavior?
Best regards, Marcus
Am 10.05.2015 um 13:54 schrieb Network Operations Center noc@schokomil.ch:
hey,
can you do me a favor and remove the exit status of your relay and turn it into a regular node? I experienced the same problem as you:
https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F26...
but ever since I removed the exit-flag I am generating some consensus rating again. This problem first popped during the last days of 2014 and up until now there hasn't been any reliable fix. Apparently even deleting the ID of your tor-node didn't help according to one user.
On 10.05.2015 07:05 AM, Larry Brandt wrote:
yes I have experienced the same problem on my exit relay: DDC6C968B3DFD156C97FD71808758D251B66DBB2 My relay lost the stable flag due to a inadvertent shut-down a few days back. LB On 5/9/2015 1:38 PM, Neel Chauhan wrote:
Hi, I have a Tor relay (https://atlas.torproject.org/#details/342587A287603040A49BB364D72EAC0B6BC3D7...) running from a FreeBSD server at my house on with a 5 megabit upstream connection. I have seen that lately, Tor's "Consensus Weight" value on this relay has not been going anywhere above (or below) 20. My relay has gotten the "Stable" flag, but yet didn't see it's consensus weight value rise. I decided to look at https://consensus-health.torproject.org/, and saw that two of the four bandwidth consensus servers, namely tor26 (86.59.21.38) and longclaw (199.254.238.52) don't seem to be calculating any consensus value for Tor relays in the last few days. Has anyone else been having this problem? And if the Tor consensus operators are reading this, (approximately) when would this problem get resolved? Thanks, Neel Chauhan _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Thanks for the response Moritz. L Brandt
On 5/10/2015 11:26 PM, Moritz Bartl wrote:
Hi,
This is a known problem; the bandwidth authorities need to be worked on. See for example
https://trac.torproject.org/projects/tor/ticket/13450 https://trac.torproject.org/projects/tor/ticket/4359
There's no timeline set yet on when this will be fixed.
On 05/10/2015 09:48 PM, Marcus Wahle wrote:
I had a look at https://collector.torproject.org/recent/relay-descriptors/consensuses/2015-0... There you can find 874 relays with the „flag“ "Bandwidth=20 Unmeasured=1“… I don’t think this is normal… Can anybody have a look at this?!
Best regards, Marcus
Am 10.05.2015 um 16:47 schrieb Marcus Wahle marcus.freifunk@gmx.de:
Hey I have almost the same problem with my relay (https://atlas.torproject.org/#details/DABC2440E9EAAEDB23F150CF95656405917A78...) I stuck to Consensus Weight: 20 since over one week. If I look at the "collected data“ I se the „unmetered = 1“ comment. :(
Any Ideas how to fix this? Is this the normal and wanted behavior?
Best regards, Marcus
Am 10.05.2015 um 13:54 schrieb Network Operations Center noc@schokomil.ch:
hey,
can you do me a favor and remove the exit status of your relay and turn it into a regular node? I experienced the same problem as you:
https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F26...
but ever since I removed the exit-flag I am generating some consensus rating again. This problem first popped during the last days of 2014 and up until now there hasn't been any reliable fix. Apparently even deleting the ID of your tor-node didn't help according to one user.
On 10.05.2015 07:05 AM, Larry Brandt wrote:
yes I have experienced the same problem on my exit relay: DDC6C968B3DFD156C97FD71808758D251B66DBB2 My relay lost the stable flag due to a inadvertent shut-down a few days back. LB On 5/9/2015 1:38 PM, Neel Chauhan wrote:
Hi, I have a Tor relay (https://atlas.torproject.org/#details/342587A287603040A49BB364D72EAC0B6BC3D7...) running from a FreeBSD server at my house on with a 5 megabit upstream connection. I have seen that lately, Tor's "Consensus Weight" value on this relay has not been going anywhere above (or below) 20. My relay has gotten the "Stable" flag, but yet didn't see it's consensus weight value rise. I decided to look at https://consensus-health.torproject.org/, and saw that two of the four bandwidth consensus servers, namely tor26 (86.59.21.38) and longclaw (199.254.238.52) don't seem to be calculating any consensus value for Tor relays in the last few days. Has anyone else been having this problem? And if the Tor consensus operators are reading this, (approximately) when would this problem get resolved? Thanks, Neel Chauhan _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I'll be shutting down 5 of my unmetered 100mbit relays until they are fixed.
Matt Speak Freely
Same problem with my relay (https://atlas.torproject.org/#details/FE4033D750831C32A957174ADD11E40F558A14...).
If i loof at collected data at collector.torproject i see: Bandwidth=20 Unmeasured=1
Best regards,
-- ML.Tor.Node
Hey I have almost the same problem with my relay (https://atlas.torproject.org/#details/DABC2440E9EAAEDB23F150CF95656405917A78...) I stuck to Consensus Weight: 20 since over one week. If I look at the "collected dataâ I se the âunmetered = 1â comment. :(
Any Ideas how to fix this? Is this the normal and wanted behavior?
Best regards, Marcus
Am 10.05.2015 um 13:54 schrieb Network Operations Center noc@schokomil.ch:
hey,
can you do me a favor and remove the exit status of your relay and turn it into a regular node? I experienced the same problem as you:
https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F26...
but ever since I removed the exit-flag I am generating some consensus rating again. This problem first popped during the last days of 2014 and up until now there hasn't been any reliable fix. Apparently even deleting the ID of your tor-node didn't help according to one user.
On 10.05.2015 07:05 AM, Larry Brandt wrote:
yes I have experienced the same problem on my exit relay: DDC6C968B3DFD156C97FD71808758D251B66DBB2 My relay lost the stable flag due to a inadvertent shut-down a few days back. LB On 5/9/2015 1:38 PM, Neel Chauhan wrote:
Hi, I have a Tor relay (https://atlas.torproject.org/#details/342587A287603040A49BB364D72EAC0B6BC3D7...) running from a FreeBSD server at my house on with a 5 megabit upstream connection. I have seen that lately, Tor's "Consensus Weight" value on this relay has not been going anywhere above (or below) 20. My relay has gotten the "Stable" flag, but yet didn't see it's consensus weight value rise. I decided to look at https://consensus-health.torproject.org/, and saw that two of the four bandwidth consensus servers, namely tor26 (86.59.21.38) and longclaw (199.254.238.52) don't seem to be calculating any consensus value for Tor relays in the last few days. Has anyone else been having this problem? And if the Tor consensus operators are reading this, (approximately) when would this problem get resolved? Thanks, Neel Chauhan _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
In the light of this thread I made an onionoo (-> atlas) feature request to display the Unmeasured=1 flag on atlas (eventually).
https://trac.torproject.org/projects/tor/ticket/16020
It seems like the most pertinent task would be to fix the problem, not display it.
Just saying...
Matt Speak Freely
nusenu:
In the light of this thread I made an onionoo (-> atlas) feature request to display the Unmeasured=1 flag on atlas (eventually).
https://trac.torproject.org/projects/tor/ticket/16020
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Speak Freely:
It seems like the most pertinent task would be to fix the problem, not display it.
Just saying...
I agree. Do we know already which relays are affected and why? teor asked in the trac entry as well.
https://trac.torproject.org/projects/tor/ticket/13450
From my experience, this happens only with exit relays. Changing from
an exit relay to a guard fixes the problem immediately.
I've seen past threads that mentioned deleting your id key would fix the problem, but that never fixed it for me. But that is also counter-intuitive given that going from exit to guard while keeping the same id fixes the problem. If I recall correctly, going back to exit causes the problem to re-appear - I will see if I can confirm that again with one of my guards-that-was-exit.
The common theme I keep seeing is that the bwauths need to fix their systems, but beyond that, or which part of their system, I don't know.
Matt Speak Freely
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Speak Freely:
From my experience, this happens only with exit relays. Changing from
an exit relay to a guard fixes the problem immediately.
I've seen past threads that mentioned deleting your id key would fix the problem, but that never fixed it for me. But that is also counter-intuitive given that going from exit to guard while keeping the same id fixes the problem. If I recall correctly, going back to exit causes the problem to re-appear - I will see if I can confirm that again with one of my guards-that-was-exit.
The common theme I keep seeing is that the bwauths need to fix their systems, but beyond that, or which part of their system, I don't know.
thanks for that post. please add that (or a pointer to it) also in the trac bug entry.
Ok, even my node (https://atlas.torproject.org/#details/FE4033D750831C32A957174ADD11E40F558A14...) after 7 days is not yet measured. But what happens to Tor Network with all these nodes (> 1000) with consensus=20?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Speak Freely:
From my experience, this happens only with exit relays. Changing from
an exit relay to a guard fixes the problem immediately.
I've seen past threads that mentioned deleting your id key would fix the problem, but that never fixed it for me. But that is also counter-intuitive given that going from exit to guard while keeping the same id fixes the problem. If I recall correctly, going back to exit causes the problem to re-appear - I will see if I can confirm that again with one of my guards-that-was-exit.
The common theme I keep seeing is that the bwauths need to fix their systems, but beyond that, or which part of their system, I don't know.
thanks for that post. please add that (or a pointer to it) also in the trac bug entry. -----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJVVNQTAAoJEFv7XvVCELh0whcP/Rvdw95CZXxCFVztnmkgzG/4 I4E+NzcxpSirSnFWXrTpP8IHMUGml9y0h/xo0i+SqFN12JbhrmBVHmwXwG0ymQLR JD1fFh+ogQ602GMEilKpY+jVbdP+nbMPmOzuYCdM6/pruotZ9MxTzeYBaScxOUzg fDaWBJFflDw9jI0o1S/AiGKHPL3gehVNkVsihsAtims9pIdItnTLg25EpLSn7D83 fUO+h+Xc2J/9utmVXdD5nxhE6KR3wjcnUDvLofqmQpKj+FY1qdr3VSaRoWA2iI/f fFQR8ot2rui8DZKAMYM3Ss8vL4R5TZyGHkmCPEs6Vm781qSdVEikpmTsJZns/JpF 7B+OHovTtJtIYcl4/wDmVIm6YrstkSVsu9incjrNaOKvUlV7xn2OQGN3CT3cnr2C aPPcUZFM+MapR9d5KbZbUwLajxmWY2KoU/a0LF6tsURKFt2RiJYo56JrrI60HUnP b0GWq+Cflo+vTmiXmt2yXz47wJcp41Zjcxch7YGI7foL0/OaFMN+RIbbEot47LkY 82NBLuc0M5JDwClobv3S7qjySzBbatNwHQwxeOWtc++vuVxWuUNZIuOPRqP1RRH+ SOiEJJnt5hcmSgIsl1bO9cM5ZBZyhIw2eMCU/9tz9KVr0UdQV0SJnwClYzAnMcqD X+ua7Hq2otDd8w/ntqZW =nK8I -----END PGP SIGNATURE----- _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
A quick update regarding my guard-that-was-exit.
This relay, when it was an exit relay, never got past consensus weight of 20. When I changed it to guard, the consensus weight immediately jumped, and bandwidth was finally starting to be used. As usual, it took a few days for full usage, but it did come.
Instead of measured bandwidth at 20b/s, it now read 45kb/s. Though arm indicated the average speed was 7-11Mb/s.
A few hours ago I switched that relay back to exit, and so far everything looks goodish. The measured bandwidth still says 45Kb/s.
I'm now averaging 10.6Mb/s, and have downloaded 16GB and uploaded 17GB since my last email.
In arm, I lost my HSDir flag, but I have received Exit flag, and have just over 500 exit connections and 1700 in/out connections.
The consensus weight, or anything for that matter, hasn't changed in Atlas yet, but that's not terribly surprising. There were recent changes in how/when Atlas report things now, right?
So... perhaps I just found a fix? Err... Workaround. This isn't a fix.
I'll take a look at doing this to the other relays to see if this fixes the problem for them as well.
Maybe some other people can do the same thing to confirm?
1) Comment out your ExitPolicy accept rules 2) service tor restart 2) Run the relay as a middle/guard until you see in Atlas your consensus weight rises - it should rise within a few hours, but seeing as how your relay isn't working anyway - you can try to wait a day to make sure all those bwauths pick you up. 3) Uncomment your ExitPolicy accept rules 4) service tor restart 5) Report your status back.
How exciting!
Matt Speak Freely
Further update:
I changed two other affected relays to guard last night.
The consensus weight didn't budge at all and bandwidth usage was negligible, so I've deleted all my onion keys for those two relays.
So these relays are starting fresh. We'll see how it goes. I'm going to wait until I get some flags and see a measured speed of anything above 160b/s, as I'll assume this means regardless of actual accuracy, the bwauths have been able to determine *something* about me, then I'll switch the flip back to exit. This should take a while, as they have to go through the different stages again.
My first relay's consensus weight hasn't budged yet, but it was in the thousands before I changed from guard to exit, so I'm not concerned - it hasn't dropped is the point I'm trying to make.
The first relay is now finally being used appropriately, at 13Mb/s in and out each. Since last evening I've done over 250GB in/out.
Arm is still reporting the measured speed as 45Kb/s.
Relay that is now working https://atlas.torproject.org/#details/D60B02A13F5D9CAFD6EC27A5332C5FEF5B7691...
You can see from March to near the end of April, as an exit relay, damn near nothing was going on. Around April 20th I changed it to guard, and activity finally started happening. Yesterday I switch back to exit, and you can clearly see the exit probability jump. :)
For comparison: https://atlas.torproject.org/#details/034A61A65419B5A115A7B6B253CAC4C9D5731E...
Like the other relay, it's consensus never went above 20. However, when I switched the flip to guard, the middle and guard probability increase was technically present, but negligible. 0.0002% and 0.0001%, respectively. Because the first relay's consensus weight responded almost immediately to the change, I arbitrarily decided the problem for the other two relays was not fixed. So I deleted the keys and am starting over to see if that helps any.
And here we are.
Matt Speak Freely
Another update.
Nothing to report.
None of the exits I changed to guard changed their consensus weight. I spun up a brand new guard relay last week, and it also is stuck at 20.
So, my one relay that was an exit but then put to guard which was then reverted back to exit is - dun dun dun - a complete one off.
Curse words and middle fingers.
Matt Speak Freely
tor-relays@lists.torproject.org
-
Larry Brandt -
Marcus Wahle -
MLTorNode -
Moritz Bartl -
Neel Chauhan -
Network Operations Center -
nusenu -
Speak Freely