In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany. It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of.
That was exactly my point, thank you Anemoi. This is the case all over the world, not just in Germany. Unfortunately there seems to be a culture of shooting the messenger here, or accusing him of being “aggressive”, “accusatory”, “claiming entitlement” or (my favorite) “lacking programming skills”, in addition to politely phrased suggestions to ditch my relay and pay for a VPS with a fixed IP.
The idea of running a volunteer based network for public good is to use every possible resource offered by volunteers, and if DirAuth algorithms need to be adapted for this, such proposal should be taken seriously. I for one am positive that a huge amount of bandwidth that could have been be donated, is lost this way.
If this does not make technical sense (which I doubt but I may be wrong), rephrasing the guidelines and officially saying on the Tor page that operators behind dynamic IP are only welcome if they run bridges would be fine – but this isn’t not the case as of now. I hope Tor developers or whoever runs the Tor project are reading this.
From: tor-relays [mailto:tor-relays-bounces@lists.torproject.org] On Behalf Of anemoi@tutanota.de Sent: Sunday, December 04, 2016 9:24 PM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany. It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of.
On Sun, Dec 04, 2016 at 09:42:34PM +0200, Rana wrote:
I hope Tor developers or whoever runs the Tor project are reading this.
Only barely. :/ I bet most of them are unable to keep up with the madness that this thread has become.
Please, I beg all of you, consider that there are 1700 busy people on this mailing list. Imagine people reading your post and thinking about it and sending a reasoned useful response if they have one, and waiting for other people to do so if they don't. Heuristics like "one useful post per topic per day" might be helpful.
And if the topic has totally changed, please change the Subject line to what the new topic is (like I've done here) -- otherwise people see a wall of 80 mails and it looks like a flamewar or something and they skip it.
Thanks for your help in keeping this a manageable list, --Roger
Am 04.12.2016 um 20:24 schrieb anemoi@tutanota.de:
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany. It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of.
In Soviet Russia, it's quite usual that you have a only IP over Avian Carriers (RFC 2549) and unusual that you have fibre to your home. Not that much relays are located in Soviet Russia. It's not just a question of frustration of owners connected via avian carriers but also a matter of bandwith waste and diversity. If Tor cannot handle avian carriers properly a lot of bandwith is not used. And bandwith and diversity is something that the Tor network can not get enough of.
SCNR
In the UK it depends what ISP your on. Virgin Media gives out static ip's as far as i know. BT (what i'm using) is dynamic, the ip changes every time the router reboots. It reboots when it detects a fault which is normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on home ip (raspberry pi)) https://atlas.torproject.org/#details/38B330302F1FB79ED11A468FC9DEA8960B842B...
MilkyWay (running on Digital Ocean) https://atlas.torproject.org/#details/E856ABA2020AA9C483CC2D9B4C878D8D948B08...
Does anyone know what the 'Family Members' does and should my relays have this set?
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany. It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of. _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi Alan,
Family indicates they're all operated by the same person. as you run both TheCosmos and MilkyWay, they are in the same family.
Please declare so in the .torrc.
Thanks!
On 4 Dec 2016 8:07 PM, "Alan" tor-relay@clutterbuck.uk wrote:
In the UK it depends what ISP your on. Virgin Media gives out static ip's as far as i know. BT (what i'm using) is dynamic, the ip changes every time the router reboots. It reboots when it detects a fault which is normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on home ip (raspberry pi)) https://atlas.torproject.org/#details/38B330302F1FB79ED11A468FC9DEA8 960B842B57
MilkyWay (running on Digital Ocean) https://atlas.torproject.org/#details/E856ABA2020AA9C483CC2D9B4C878D 8D948B0887
Does anyone know what the 'Family Members' does and should my relays have this set?
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany. It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of. _______________________________________________ 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 that, I've made changes to both torrc files. I've added MyFamily with each others finger print like so: MyFamily E856ABA2020AA9C483CC2D9B4C878D8D948B0887
Then sighup'd both relays through arm.
Do you know how long it takes Atlas to show the changes?
Alan
Hi Alan,
Family indicates they're all operated by the same person. as you run both TheCosmos and MilkyWay, they are in the same family.
Please declare so in the .torrc.
Thanks!
On 4 Dec 2016 8:07 PM, "Alan" tor-relay@clutterbuck.uk wrote:
In the UK it depends what ISP your on. Virgin Media gives out static ip's as far as i know. BT (what i'm using) is dynamic, the ip changes every time the router reboots. It reboots when it detects a fault which is normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on home ip (raspberry pi)) https://atlas.torproject.org/#details/38B330302F1FB79ED11A468FC9DEA8 960B842B57
MilkyWay (running on Digital Ocean) https://atlas.torproject.org/#details/E856ABA2020AA9C483CC2D9B4C878D 8D948B0887
Does anyone know what the 'Family Members' does and should my relays have this set?
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany.Ã It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of. _______________________________________________ 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
Good question some of mine are not but then I thought the fingerprint had to be prefixed with a $ sign? I dont see any errors in the log when I use $<fingerprint> or without a $ sign?
Looking at Atlas the myfamily fingerprints seem to have a $ in front of them? But in man pages it just says 'fingerprint' with no syntax
Anyway Atlas can take awhile to update - hours rather than days
On 4 Dec 2016, at 20:47, Alan tor-relay@clutterbuck.uk wrote:
Thanks for that, I've made changes to both torrc files. I've added MyFamily with each others finger print like so: MyFamily E856ABA2020AA9C483CC2D9B4C878D8D948B0887
Then sighup'd both relays through arm.
Do you know how long it takes Atlas to show the changes?
Alan
Hi Alan,
Family indicates they're all operated by the same person. as you run both TheCosmos and MilkyWay, they are in the same family.
Please declare so in the .torrc.
Thanks!
On 4 Dec 2016 8:07 PM, "Alan" tor-relay@clutterbuck.uk wrote:
In the UK it depends what ISP your on. Virgin Media gives out static ip's as far as i know. BT (what i'm using) is dynamic, the ip changes every time the router reboots. It reboots when it detects a fault which is normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on home ip (raspberry pi)) https://atlas.torproject.org/#details/38B330302F1FB79ED11A468FC9DEA8 960B842B57
MilkyWay (running on Digital Ocean) https://atlas.torproject.org/#details/E856ABA2020AA9C483CC2D9B4C878D 8D948B0887
Does anyone know what the 'Family Members' does and should my relays have this set?
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany.Ã It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of. _______________________________________________ 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've been trying to find the answer to $ prefix or not. I've just this second added it to both. Maybe without it assumes it's a nickname.
Good question some of mine are not but then I thought the fingerprint had to be prefixed with a $ sign? I dont see any errors in the log when I use $<fingerprint> or without a $ sign?
Looking at Atlas the myfamily fingerprints seem to have a $ in front of them? But in man pages it just says 'fingerprint' with no syntax
Anyway Atlas can take awhile to update - hours rather than days
On 4 Dec 2016, at 20:47, Alan tor-relay@clutterbuck.uk wrote:
Thanks for that, I've made changes to both torrc files. I've added MyFamily with each others finger print like so: MyFamily E856ABA2020AA9C483CC2D9B4C878D8D948B0887
Then sighup'd both relays through arm.
Do you know how long it takes Atlas to show the changes?
Alan
Hi Alan,
Family indicates they're all operated by the same person. as you run both TheCosmos and MilkyWay, they are in the same family.
Please declare so in the .torrc.
Thanks!
On 4 Dec 2016 8:07 PM, "Alan" tor-relay@clutterbuck.uk wrote:
In the UK it depends what ISP your on. Virgin Media gives out static ip's as far as i know. BT (what i'm using) is dynamic, the ip changes every time the router reboots. It reboots when it detects a fault which is normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on home ip (raspberry pi)) https://atlas.torproject.org/#details/38B330302F1FB79ED11A468FC9DEA8 960B842B57
MilkyWay (running on Digital Ocean) https://atlas.torproject.org/#details/E856ABA2020AA9C483CC2D9B4C878D 8D948B0887
Does anyone know what the 'Family Members' does and should my relays have this set?
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany.ÃÂ It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of. _______________________________________________ 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
The dollar sign is optional.
Find ExcludeNodes option description at: https://www.torproject.org/docs/tor-manual.html.en
A list of identity fingerprints, country codes, and address patterns
of nodes to avoid when building a circuit. Country codes are 2-letter ISO3166 codes, and must be wrapped in braces; fingerprints may be preceded by a dollar sign.
In my experience, this holds true all over a torrc.
Matt
On 12/04/2016 04:10 PM, Alan wrote:
I've been trying to find the answer to $ prefix or not. I've just this second added it to both. Maybe without it assumes it's a nickname.
Good question some of mine are not but then I thought the fingerprint had to be prefixed with a $ sign? I dont see any errors in the log when I use $<fingerprint> or without a $ sign?
Looking at Atlas the myfamily fingerprints seem to have a $ in front of them? But in man pages it just says 'fingerprint' with no syntax
Anyway Atlas can take awhile to update - hours rather than days
On 4 Dec 2016, at 20:47, Alan tor-relay@clutterbuck.uk wrote:
Thanks for that, I've made changes to both torrc files. I've added MyFamily with each others finger print like so: MyFamily E856ABA2020AA9C483CC2D9B4C878D8D948B0887
Then sighup'd both relays through arm.
Do you know how long it takes Atlas to show the changes?
Alan
Hi Alan,
Family indicates they're all operated by the same person. as you run both TheCosmos and MilkyWay, they are in the same family.
Please declare so in the .torrc.
Thanks!
On 4 Dec 2016 8:07 PM, "Alan" tor-relay@clutterbuck.uk wrote:
In the UK it depends what ISP your on. Virgin Media gives out static ip's as far as i know. BT (what i'm using) is dynamic, the ip changes every time the router reboots. It reboots when it detects a fault which is normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on home ip (raspberry pi)) https://atlas.torproject.org/#details/38B330302F1FB79ED11A468FC9DEA8 960B842B57
MilkyWay (running on Digital Ocean) https://atlas.torproject.org/#details/E856ABA2020AA9C483CC2D9B4C878D 8D948B0887
Does anyone know what the 'Family Members' does and should my relays have this set?
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany.ÃÂ It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of. _______________________________________________ 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
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
For efficiency upon yourself and others... Don't add the '$'. Use lower case for fingerprints with no spaces (ticketed). Use the same myfamily line including all your relays for all your relays, no point in trying to leave announcing relay out of list.
On 5 Dec. 2016, at 07:47, Alan tor-relay@clutterbuck.uk wrote:
Thanks for that, I've made changes to both torrc files. I've added MyFamily with each others finger print like so: MyFamily E856ABA2020AA9C483CC2D9B4C878D8D948B0887
Then sighup'd both relays through arm.
Do you know how long it takes Atlas to show the changes?
25 - 85 minutes, as long as OnionOO is running.
Tim
Alan
Hi Alan,
Family indicates they're all operated by the same person. as you run both TheCosmos and MilkyWay, they are in the same family.
Please declare so in the .torrc.
Thanks!
On 4 Dec 2016 8:07 PM, "Alan" tor-relay@clutterbuck.uk wrote:
In the UK it depends what ISP your on. Virgin Media gives out static ip's as far as i know. BT (what i'm using) is dynamic, the ip changes every time the router reboots. It reboots when it detects a fault which is normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on home ip (raspberry pi)) https://atlas.torproject.org/#details/38B330302F1FB79ED11A468FC9DEA8 960B842B57
MilkyWay (running on Digital Ocean) https://atlas.torproject.org/#details/E856ABA2020AA9C483CC2D9B4C878D 8D948B0887
Does anyone know what the 'Family Members' does and should my relays have this set?
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany.Ã It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of. _______________________________________________ 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
T
No all good just add them as you are tor adds a $ if you dont its not an issue
Cheers Mark B
On 4 Dec 2016, at 20:47, Alan tor-relay@clutterbuck.uk wrote:
Thanks for that, I've made changes to both torrc files. I've added MyFamily with each others finger print like so: MyFamily E856ABA2020AA9C483CC2D9B4C878D8D948B0887
Then sighup'd both relays through arm.
Do you know how long it takes Atlas to show the changes?
Alan
Hi Alan,
Family indicates they're all operated by the same person. as you run both TheCosmos and MilkyWay, they are in the same family.
Please declare so in the .torrc.
Thanks!
On 4 Dec 2016 8:07 PM, "Alan" tor-relay@clutterbuck.uk wrote:
In the UK it depends what ISP your on. Virgin Media gives out static ip's as far as i know. BT (what i'm using) is dynamic, the ip changes every time the router reboots. It reboots when it detects a fault which is normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on home ip (raspberry pi)) https://atlas.torproject.org/#details/38B330302F1FB79ED11A468FC9DEA8 960B842B57
MilkyWay (running on Digital Ocean) https://atlas.torproject.org/#details/E856ABA2020AA9C483CC2D9B4C878D 8D948B0887
Does anyone know what the 'Family Members' does and should my relays have this set?
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany.Ã It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of. _______________________________________________ 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
On Sun, 4 Dec 2016 20:47:17 -0000 "Alan" tor-relay@clutterbuck.uk wrote:
Thanks for that, I've made changes to both torrc files. I've added MyFamily with each others finger print like so: MyFamily E856ABA2020AA9C483CC2D9B4C878D8D948B0887
You don't need to only list the other one(s) in each MyFamily, you could simply list all your relays in it. This tends to simplify management of this, and since now the MyFamily line is identical on all hosts, you have a simpler task if you want to automate adding it to the configs.
Hi Alan
If you have more than one relay you add the fingerprint of any other relay you run to your torrc file - if say I ran 10 relays and exits there may be a chance that you would route through just my servers thus you would not be anonymous as I could follow you through from entry to exit.
In short if you have more than one relay or exit add the fingerprint of the other relays exits to your torrc file
Cheers Snap
On 4 Dec 2016, at 19:58, Alan tor-relay@clutterbuck.uk wrote:
In the UK it depends what ISP your on. Virgin Media gives out static ip's as far as i know. BT (what i'm using) is dynamic, the ip changes every time the router reboots. It reboots when it detects a fault which is normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on home ip (raspberry pi)) https://atlas.torproject.org/#details/38B330302F1FB79ED11A468FC9DEA8960B842B...
MilkyWay (running on Digital Ocean) https://atlas.torproject.org/#details/E856ABA2020AA9C483CC2D9B4C878D8D948B08...
Does anyone know what the 'Family Members' does and should my relays have this set?
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany. It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of. _______________________________________________ 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,
Im not sure if I'm entitled to post here, but i think my contribution might be useful. I am running two relays on dynamic IPs which change about very 24hours, my advertised bandwidth is around 700KB/s, Actually used are around 150KB/s which gives about 20% of the advertised bandwidth. This ratio is of course little bit lower than the static IP relays but by no means as severe as Rana’s. Maybe Rana’s configuration might have a problem and we should make a step back and look closer on Rana’s configuration to figure out what’s going on.
Kind regards
2016-12-04 20:23 GMT, Sec INT sec.int9@gmail.com:
Hi Alan
If you have more than one relay you add the fingerprint of any other relay you run to your torrc file - if say I ran 10 relays and exits there may be a chance that you would route through just my servers thus you would not be anonymous as I could follow you through from entry to exit.
In short if you have more than one relay or exit add the fingerprint of the other relays exits to your torrc file
Cheers Snap
On 4 Dec 2016, at 19:58, Alan tor-relay@clutterbuck.uk wrote:
In the UK it depends what ISP your on. Virgin Media gives out static ip's as far as i know. BT (what i'm using) is dynamic, the ip changes every time the router reboots. It reboots when it detects a fault which is normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on home ip (raspberry pi)) https://atlas.torproject.org/#details/38B330302F1FB79ED11A468FC9DEA8960B842B...
MilkyWay (running on Digital Ocean) https://atlas.torproject.org/#details/E856ABA2020AA9C483CC2D9B4C878D8D948B08...
Does anyone know what the 'Family Members' does and should my relays have this set?
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany. It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of. _______________________________________________ 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
On 5 Dec. 2016, at 07:44, Netgear Ready rndduo@gmail.com wrote:
Hey,
Im not sure if I'm entitled to post here, but i think my contribution might be useful. I am running two relays on dynamic IPs which change about very 24hours, my advertised bandwidth is around 700KB/s, Actually used are around 150KB/s which gives about 20% of the advertised bandwidth. This ratio is of course little bit lower than the static IP relays but by no means as severe as Rana’s. Maybe Rana’s configuration might have a problem and we should make a step back and look closer on Rana’s configuration to figure out what’s going on.
Yes, that's an important point. If other operators with dynamic IPs aren't seeing this issue, perhaps the dynamic IP is not the problem?
Maybe Rana's Raspberry Pi (or router) can't handle the number of connections required to run a relay?
Maybe their ISP has poor international connectivity?
Maybe their connection can't sustain traffic speeds reliably?
There are plenty of answers other than a dynamic IP address.
In fact, the bandwidth measurement code doesn't even store IP addresses, so the issue can't be there.
But the reachability code does reset the time when it last reached the relay every time the address changes, in node_addrs_changed().
So there is that factor as well, which would reset the flags. But it still shouldn't affect the bandwidth measurements. They should be much higher.
Tim
Kind regards
2016-12-04 20:23 GMT, Sec INT sec.int9@gmail.com:
Hi Alan
If you have more than one relay you add the fingerprint of any other relay you run to your torrc file - if say I ran 10 relays and exits there may be a chance that you would route through just my servers thus you would not be anonymous as I could follow you through from entry to exit.
In short if you have more than one relay or exit add the fingerprint of the other relays exits to your torrc file
Cheers Snap
On 4 Dec 2016, at 19:58, Alan tor-relay@clutterbuck.uk wrote:
In the UK it depends what ISP your on. Virgin Media gives out static ip's as far as i know. BT (what i'm using) is dynamic, the ip changes every time the router reboots. It reboots when it detects a fault which is normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on home ip (raspberry pi)) https://atlas.torproject.org/#details/38B330302F1FB79ED11A468FC9DEA8960B842B...
MilkyWay (running on Digital Ocean) https://atlas.torproject.org/#details/E856ABA2020AA9C483CC2D9B4C878D8D948B08...
Does anyone know what the 'Family Members' does and should my relays have this set?
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany. It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of.
T
My international connectivity is just fine, connection speed is stable at 1.5 mbps and I have a Stable flag. Three authorities voted to give me HSDir and Fast. I have provided my Torrc. My consensus weight is stable for several days now, at 14.
-----Original Message----- From: tor-relays [mailto:tor-relays-bounces@lists.torproject.org] On Behalf Of teor Sent: Sunday, December 04, 2016 11:07 PM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP
On 5 Dec. 2016, at 07:44, Netgear Ready rndduo@gmail.com wrote:
Hey,
Im not sure if I'm entitled to post here, but i think my contribution might be useful. I am running two relays on dynamic IPs which change about very 24hours, my advertised bandwidth is around 700KB/s, Actually used are around 150KB/s which gives about 20% of the advertised bandwidth. This ratio is of course little bit lower than the static IP relays but by no means as severe as Rana’s. Maybe Rana’s configuration might have a problem and we should make a step back and look closer on Rana’s configuration to figure out what’s going on.
Yes, that's an important point. If other operators with dynamic IPs aren't seeing this issue, perhaps the dynamic IP is not the problem?
Maybe Rana's Raspberry Pi (or router) can't handle the number of connections required to run a relay?
Maybe their ISP has poor international connectivity?
Maybe their connection can't sustain traffic speeds reliably?
There are plenty of answers other than a dynamic IP address.
In fact, the bandwidth measurement code doesn't even store IP addresses, so the issue can't be there.
But the reachability code does reset the time when it last reached the relay every time the address changes, in node_addrs_changed().
So there is that factor as well, which would reset the flags. But it still shouldn't affect the bandwidth measurements. They should be much higher.
Tim
Kind regards
2016-12-04 20:23 GMT, Sec INT sec.int9@gmail.com:
Hi Alan
If you have more than one relay you add the fingerprint of any other relay you run to your torrc file - if say I ran 10 relays and exits there may be a chance that you would route through just my servers thus you would not be anonymous as I could follow you through from entry to exit.
In short if you have more than one relay or exit add the fingerprint of the other relays exits to your torrc file
Cheers Snap
On 4 Dec 2016, at 19:58, Alan tor-relay@clutterbuck.uk wrote:
In the UK it depends what ISP your on. Virgin Media gives out static ip's as far as i know. BT (what i'm using) is dynamic, the ip changes every time the router reboots. It reboots when it detects a fault which is normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on home ip (raspberry pi)) https://atlas.torproject.org/#details/38B330302F1FB79ED11A468FC9DEA8 960B842B57
MilkyWay (running on Digital Ocean) https://atlas.torproject.org/#details/E856ABA2020AA9C483CC2D9B4C878D 8D948B0887
Does anyone know what the 'Family Members' does and should my relays have this set?
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany. It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 5 Dec. 2016, at 08:15, Rana ranaventures@gmail.com wrote:
My international connectivity is just fine, connection speed is stable at 1.5 mbps and I have a Stable flag. Three authorities voted to give me HSDir and Fast. I have provided my Torrc. My consensus weight is stable for several days now, at 14.
Speed tests don't test the things tor needs.
The 5 tor bandwidth authorities say your relay can't handle much bandwidth. They say it can sustain around 14KB/s when they check.
This might mean your Pi or your broadband router is overwhelmed with too many connections. Do you know what the maximum connection capacity is on your router and your relay? Can you increase it to at least 8000?
Or it could be that your latency to Europe and North America is high. (Relays in Asia, Australia, and New Zealand have similar issues.)
Tim
-----Original Message----- From: tor-relays [mailto:tor-relays-bounces@lists.torproject.org] On Behalf Of teor Sent: Sunday, December 04, 2016 11:07 PM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP
On 5 Dec. 2016, at 07:44, Netgear Ready rndduo@gmail.com wrote:
Hey,
Im not sure if I'm entitled to post here, but i think my contribution might be useful. I am running two relays on dynamic IPs which change about very 24hours, my advertised bandwidth is around 700KB/s, Actually used are around 150KB/s which gives about 20% of the advertised bandwidth. This ratio is of course little bit lower than the static IP relays but by no means as severe as Rana’s. Maybe Rana’s configuration might have a problem and we should make a step back and look closer on Rana’s configuration to figure out what’s going on.
Yes, that's an important point. If other operators with dynamic IPs aren't seeing this issue, perhaps the dynamic IP is not the problem?
Maybe Rana's Raspberry Pi (or router) can't handle the number of connections required to run a relay?
Maybe their ISP has poor international connectivity?
Maybe their connection can't sustain traffic speeds reliably?
There are plenty of answers other than a dynamic IP address.
In fact, the bandwidth measurement code doesn't even store IP addresses, so the issue can't be there.
But the reachability code does reset the time when it last reached the relay every time the address changes, in node_addrs_changed().
So there is that factor as well, which would reset the flags. But it still shouldn't affect the bandwidth measurements. They should be much higher.
Tim
Kind regards
2016-12-04 20:23 GMT, Sec INT sec.int9@gmail.com:
Hi Alan
If you have more than one relay you add the fingerprint of any other relay you run to your torrc file - if say I ran 10 relays and exits there may be a chance that you would route through just my servers thus you would not be anonymous as I could follow you through from entry to exit.
In short if you have more than one relay or exit add the fingerprint of the other relays exits to your torrc file
Cheers Snap
On 4 Dec 2016, at 19:58, Alan tor-relay@clutterbuck.uk wrote:
In the UK it depends what ISP your on. Virgin Media gives out static ip's as far as i know. BT (what i'm using) is dynamic, the ip changes every time the router reboots. It reboots when it detects a fault which is normally between 2-4 weeks on average.
These are my relays:
TheCosmos (running on home ip (raspberry pi)) https://atlas.torproject.org/#details/38B330302F1FB79ED11A468FC9DEA8 960B842B57
MilkyWay (running on Digital Ocean) https://atlas.torproject.org/#details/E856ABA2020AA9C483CC2D9B4C878D 8D948B0887
Does anyone know what the 'Family Members' does and should my relays have this set?
In Germany, it's quite usual that you have a dynamic IP and unusual that you have static IP. Not just a few relays are located in Germany. It's not just a question of frustration of owners of dynamic IP relay, but also a matter of bandwith waste. If Tor cannot handle dynamic IPs properly a lot of bandwith is not used. And bandwith is something that the Tor network can not get enough of.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
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
T
Wow, I cannot think of a way to check the max number of connections on my router. I do not believe that Pi has such limitation...
-----Original Message----- From: tor-relays [mailto:tor-relays-bounces@lists.torproject.org] On Behalf Of teor Sent: Sunday, December 04, 2016 11:42 PM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP
On 5 Dec. 2016, at 08:15, Rana ranaventures@gmail.com wrote:
My international connectivity is just fine, connection speed is stable at 1.5 mbps and I have a Stable flag. Three authorities voted to give me HSDir and Fast. I have provided my Torrc. My consensus weight is stable for several days now, at 14.
Speed tests don't test the things tor needs.
The 5 tor bandwidth authorities say your relay can't handle much bandwidth. They say it can sustain around 14KB/s when they check.
This might mean your Pi or your broadband router is overwhelmed with too many connections. Do you know what the maximum connection capacity is on your router and your relay? Can you increase it to at least 8000?
Or it could be that your latency to Europe and North America is high. (Relays in Asia, Australia, and New Zealand have similar issues.)
Tim
On 5 Dec. 2016, at 08:51, Rana ranaventures@gmail.com wrote:
Wow, I cannot think of a way to check the max number of connections on my router. I do not believe that Pi has such limitation…
Every unix-based machine has such a limitation on each user. It is normally called the maximum number of file descriptors.
So yes, it likely affects your router (which you can't change), and your relay (which you can).
Check the tor logs for messages about connection limits or file descriptor limits.
Look up instructions online for increasing the number of file descriptors per user on your OS and distribution.
Tim
-----Original Message----- From: tor-relays [mailto:tor-relays-bounces@lists.torproject.org] On Behalf Of teor Sent: Sunday, December 04, 2016 11:42 PM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP
On 5 Dec. 2016, at 08:15, Rana ranaventures@gmail.com wrote:
My international connectivity is just fine, connection speed is stable at 1.5 mbps and I have a Stable flag. Three authorities voted to give me HSDir and Fast. I have provided my Torrc. My consensus weight is stable for several days now, at 14.
Speed tests don't test the things tor needs.
The 5 tor bandwidth authorities say your relay can't handle much bandwidth. They say it can sustain around 14KB/s when they check.
This might mean your Pi or your broadband router is overwhelmed with too many connections. Do you know what the maximum connection capacity is on your router and your relay? Can you increase it to at least 8000?
Or it could be that your latency to Europe and North America is high. (Relays in Asia, Australia, and New Zealand have similar issues.)
Tim
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
T
Thanks Netgear Ready for the constructive approach. Here is my torrc (nickname redacted). There is no hidden service running on the Pi and no connections to the transparent proxy (its respective wifi interface is down). The Pi is doing nothing except the Tor relay, memory utilization 13%, CPU close to nil.
My uplink is consistent at 1.5 mbps measured using speedtest-cli from the Pi, downlink is much higher. Consensus weight is 14 (!), Atlas "advertised" bandwidth currently 85 KB/s but sometimes reaches as high as 170 KB/s. Actual traffic is practically negligible (14 MB in 6 hours). I have a Stable flag and am running for a month, the last 9 days with the same IP. Help will be much appreciated.
Rana
------------------------------------------------- Log notice file /var/log/tor/notices.log VirtualAddrNetworkIPv4 10.192.0.0/10 AutomapHostsSuffixes .onion,.exit AutomapHostsOnResolve 1 TransPort 9040 TransListenAddress 172.24.1.1 DNSPort 53 DNSListenAddress 172.24.1.1 DisableDebuggerAttachment 0 RunAsDaemon 1 HiddenServiceDir /var/lib/tor/hidden_service/ HiddenServicePort 80 127.0.0.1:80 HiddenServiceDir /var/lib/tor/other_hidden_service/ HiddenServicePort 80 127.0.0.1:80 HiddenServicePort 22 127.0.0.1:22 ORPort 9001 Nickname xxxxxxxx RelayBandwidthRate 250 KB # Throttle traffic to 250KB/s (2.0 Mbit/sec) RelayBandwidthBurst 350 KB # But allow bursts up to 350KB/s (2.8 Mbit/sec) DirPort 9030 # what port to advertise for directory connections ExitPolicy reject *:* # no exits allowed
-----Original Message----- From: tor-relays [mailto:tor-relays-bounces@lists.torproject.org] On Behalf Of Netgear Ready Sent: Sunday, December 04, 2016 10:44 PM To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] Unwarranted discrimination of relays with dynamic IP
Hey,
Im not sure if I'm entitled to post here, but i think my contribution might be useful. I am running two relays on dynamic IPs which change about very 24hours, my advertised bandwidth is around 700KB/s, Actually used are around 150KB/s which gives about 20% of the advertised bandwidth. This ratio is of course little bit lower than the static IP relays but by no means as severe as Rana’s. Maybe Rana’s configuration might have a problem and we should make a step back and look closer on Rana’s configuration to figure out what’s going on.
Kind regards
tor-relays@lists.torproject.org
-
Alan -
anemoi＠tutanota.de -
Diarmaid McManus -
grarpamp -
Matt Traudt -
Netgear Ready -
Rana -
Roger Dingledine -
Roman Mamedov -
Sebastian Niehaus -
Sec INT -
teor