- tor-relays - lists.torproject.org

Include Tor Weather Link
by Spencer Rhodes 18 Aug '14

18 Aug '14

If another email goes out to operators of outdated Tor relays, I would suggest including some information and a link to the Tor Weather service, which has an option to notify via email if the software version is outdated. -- Sent from my phone.

2 1

Dynamic IP
by Tim 18 Aug '14

18 Aug '14

Tim Wilson-Brown E: twilsonb(a)mac.com > Date: Mon, 18 Aug 2014 05:04:31 +0200 > From: Sebastian Hahn <mail(a)sebastianhahn.net> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Dynamic IP > Message-ID: <CD0E96E4-2BFA-4FAA-BC19-C3320AC46F08(a)sebastianhahn.net> > Content-Type: text/plain; charset=us-ascii > > Hi Tim, > >> Sebastien, I run a relay on a machine that has an internal private IP, behind a NAT router with a public IP. >> >> In my experience, I need to specify the NAT router's public IP in the torrc, otherwise tor doesn't include it in the router descriptor it submits to the consensus. > > This shouldn't happen typically, Tor tries to learn its IP address by > looking at the traffic it receives. > >> If that process isn't working for me, is this a bug I should report? > > Likely. Can you try again, noting the kind of log messages Tor might > emit? > I apologise, Sebastien, it appears I was not waiting long enough for the router to connect to a directory, then use the headers to find its IP. I had always assumed that the first series of failures to find an IP (before any directories were contacted) was permanent. This is the debug log output from a secondary test router that I configured on the same IP: Aug 18 17:47:20.558 [info] {CONFIG} int resolve_my_address(int, const or_options_t *, uint32_t *, const char **, char **)(): Guessed local hostname 'REDACTED.local' resolves to a private IP address (192.168.REDACTED.REDACTED). Trying something else. Aug 18 17:47:20.558 [info] {CONFIG} int resolve_my_address(int, const or_options_t *, uint32_t *, const char **, char **)(): Interface IP address '192.168.REDACTED.REDACTED' is a private address too. Ignoring. Aug 18 17:47:20.558 [info] {CONFIG} int resolve_my_address(int, const or_options_t *, uint32_t *, const char **, char **)(): Address 'REDACTED.local' resolves to private IP address '192.168.REDACTED.REDACTED'. Tor servers that use the default DirAuthorities must have public IP addresses. Aug 18 17:47:20.558 [info] {CONFIG} int router_pick_published_address(const or_options_t *, uint32_t *)(): Could not determine our address locally. Checking if directory headers provide any hints. Aug 18 17:47:20.558 [info] {CONFIG} int router_pick_published_address(const or_options_t *, uint32_t *)(): Success: chose address '121.REDACTED.REDACTED.REDACTED'. Once the test router appears in the consensus, I'll make similar changes to the primary router (and it will pick them up on the next restart!) Tim

1 0

Close friend
by IceFish ThreeTwo 18 Aug '14

18 Aug '14

Hello. I'm not going to use the term "Framily", Sprint can...nsfw. Anyways, my close friend just set up a Tor node. I'm pretty sure I read somewhere that the Family option in torrc is used so that nodes administrated by the same person never make a circuit with each other, which somehow protects anonymity. Should my friend and I put each other's fingerprints in the Family field? Seems logical since we know each other and if the point of theFamily field is to protect anonymity. Thanks! Ice Fish -- Sent from my iPhone

4 4

Dynamic IP
by Tim 18 Aug '14

18 Aug '14

> On Sun, 17 Aug 2014 00:42:13 +0200, Sebastian Hahn <mail(a)sebastianhahn.net> wrote: > > Date: Sun, 17 Aug 2014 00:42:13 +0200 > From: Sebastian Hahn <mail(a)sebastianhahn.net> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Dynamic IP > Message-ID: <90ABDCE9-CC09-4892-9935-F7B7C78832E9(a)sebastianhahn.net> > Content-Type: text/plain; charset=us-ascii > > Hi Tim, > >> On 16 Aug 2014, at 23:53, Tim <t_ebay(a)icloud.com> wrote: >> I'm running a relay on a similarly "dynamic" IP. >> If the line goes down, I'm reallocated a new one. But otherwise the IP is stable. >> If I don't notice the change, I notice the traffic drop, then I update the torrc, and everything works again. > > I think you're a little confused. It's not necessary to specify your own > IP address in Tor's configuration file. The various "address" options are > purely optional. Or I am confused, and you mean something completely > different? > Sebastien, I run a relay on a machine that has an internal private IP, behind a NAT router with a public IP. In my experience, I need to specify the NAT router's public IP in the torrc, otherwise tor doesn't include it in the router descriptor it submits to the consensus. How does tor autodetect its public IP, when it is running on a separate machine with a private network IP, behind a NAT router with a public IP? If that process isn't working for me, is this a bug I should report? If tor doesn't currently autodetect public IPs on middleboxes (as opposed to the tor relay machine itself), is this a feature that could be implemented? Or do we wish to discourage this use case? (It would involve trusting an external server to report tor's public IP correctly - and making other assumptions like the middlebox having a single public IP.) Tim

2 1

Number of relays by version
by Jesse Victors 17 Aug '14

17 Aug '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA384 Hey guys, Today on Reddit I saw a post on /r/Tor that listed the number of relays by version, which was pretty cool. While OP apparently loaded the information into SQLite and selected the count, there's another way to do it: sudo cat /var/lib/tor/cached-microdesc-consensus | grep '^v ' | awk '{print $3}' | sort | uniq -c Which currently gives: 2 0.2.3.20-rc 5 0.2.3.22-rc 3 0.2.3.24-rc 579 0.2.3.25 1 0.2.4.10-alpha 2 0.2.4.11-alpha 5 0.2.4.15-rc 15 0.2.4.16-rc 23 0.2.4.17-rc 4 0.2.4.18-rc 12 0.2.4.19 271 0.2.4.20 351 0.2.4.21 998 0.2.4.22 3 0.2.4.22-dev 3209 0.2.4.23 7 0.2.4.23-dev 3 0.2.5.1-alpha-dev 9 0.2.5.2-alpha 22 0.2.5.3-alpha 5 0.2.5.3-alpha-dev 28 0.2.5.4-alpha 4 0.2.5.4-alpha-dev 47 0.2.5.5-alpha 232 0.2.5.6-alpha 29 0.2.6.0-alpha-dev I find the distribution interesting. 0.2.3 is dwindling, but for those 589 that remain, please be aware 0.2.4 is available, so be sure to update or change to the official Tor repos. Looks like 0.2.6.0 is the tip of the spear now. - -- Jesse V. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQF8BAEBCQBmBQJT8FBhXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMjgyMjhENjEyODQ1OTU1NzBCMjgwRkFB RDk3MzY0RkMyMEJFQzgwAAoJEK2XNk/CC+yAFCMIAMBzJko9CDSqfEyiPFZzNVy8 ZNlr4ZBekm9aLG2cJEVD2zN2wLc0mWb/ETFrbVNbauWIEvuNjchE0xZRXMUJBrFT L9ErUmNeGWEr77XXYAawoOI4PDPXOF4SIMQUdAel8OVCZ5g0UYARDlfIBgwVeq+o LnvSrDdv/hcwIxsrLxX+J/XqwXOIDnxhjMu6MnHG7YDXGameACbMl4OfOCgXVNT9 VV9YLATJq1nHr5F5I8xmDU5RVUsVRccn8POBHgTfZwDtwMy3N6U/wQqFY0XzslLH wY2veoPcuIoL8x1Sz81vK9Buc9oD/F06HzrZRW2WHg2Tw8yJYFizVyWpOlQ/xKs= =NIsd -----END PGP SIGNATURE-----

2 1

Re: [tor-relays] Dynamic IP
by Tim 16 Aug '14

16 Aug '14

I'm running a relay on a similarly "dynamic" IP. If the line goes down, I'm reallocated a new one. But otherwise the IP is stable. If I don't notice the change, I notice the traffic drop, then I update the torrc, and everything works again. Wouldn't it be great if there was an option for tor to do this automatically? But this would involve trusting google or similar to correctly report the external IP (and not get MITMed). I tried running a bridge, but it made almost no use of the available bandwidth. But if the IP were more dynamic, a bridge would be an excellent choice, as long as I could keep the config synced with the external IP. This would be the core use case for a tor "use dynamic external IP" option. (And the current "guess my IP" option doesn't work for me, as it's the internet-visible external IP I need, not the relay's internal network IP.) > On 17 Aug 2014, at 6:45, IceFish ThreeTwo <threehundredthirtytwofishes(a)gmail.com> wrote: > > Date: Sat, 16 Aug 2014 13:09:08 -0700 > From: IceFish ThreeTwo <threehundredthirtytwofishes(a)gmail.com> > To: "tor-relays(a)lists.torproject.org" > <tor-relays(a)lists.torproject.org> > Subject: Re: [tor-relays] Dynamic IP > > Alright thanks. Yeah it's a "dynamic" IP. I bet they just say that in case > they have to change it for some reason. > >> On Saturday, August 16, 2014, justaguy <justaguy(a)riseup.net> wrote: >> >> That's not a big deal, if it's once every 8 months. >> But every day, that would be a problem. >> If you keep running your relay for 8 months, and then an ip change, i >> think it will be back at normal speeds in like 5 minutes >> On 08/16/2014 10:04 PM, IceFish ThreeTwo wrote: >> >> Unfortunately my ISP only provides static IPs for their business accounts, >> which, even if in my price range, I can't get at my home because of zoning. >> My IP hasn't changed once since I got the service and I think I've kinda >> locked it in with my router. But if it does switch say once every 8 months, >> how big of a deal is that? >> >> On Saturday, August 16, 2014, justaguy <justaguy(a)riseup.net >> <javascript:_e(%7B%7D,'cvml','justaguy(a)riseup.net');>> wrote: >> >>> Yes, other relays don't like your relay changing ip's all the time. >>> You should try to get a static ip somehow, ask your isp :) >>> On 08/16/2014 10:00 PM, IceFish ThreeTwo wrote: >>> >>> I have a dynamic IP from my ISP. Is that going to cause issues with my >>> relay? >>> >>> -- >>> Sent from my iPhone >>> >>> >>> _______________________________________________ >>> tor-relays mailing listtor-relays@lists.torproject.orghttps://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> >> -- >> Sent from my iPhone >> >> >> _______________________________________________ >> tor-relays mailing listtor-relays(a)lists.torproject.org <javascript:_e(%7B%7D,'cvml','tor-relays(a)lists.torproject.org');>https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > -- > Sent from my iPhone >

2 1

Getting things right
by Graeme Briggs-White 16 Aug '14

16 Aug '14

I have a rooted Samsung S3 with CM 11 4.4.4 nightly build and would like to know exactly how to get the best for everyone involved on the network. My problem seems to be ram capacity and have tried every which way to improve that. Nothing seems to work as it has under 1 Gig of ram. How do I configure this for the best and not piss other users off. My binary skills are none too great but I'm willing to learn and am open to harsh comments to get me on my way. I'm quite a newbee at this and open to criticism.....

3 13

Dynamic IP
by IceFish ThreeTwo 16 Aug '14

16 Aug '14

I have a dynamic IP from my ISP. Is that going to cause issues with my relay? -- Sent from my iPhone

3 5

Re: [tor-relays] tor-relays Digest, Vol 43, Issue 15
by Spencer Rhodes 16 Aug '14

16 Aug '14

Hi Matt, Thanks for the quick reply. The servers did not show because I had commented out the Nickname line in /etc/tor/torrc after seeing a notice in arm that it was redundant (presumably because it is identical to the hostname). Apparently, not redundant after all as it is necessary for proper listing on the torstatus servers… So, I browsed to your suggested URL and verified that for my server which does show the Directory flags, it returns a bunch of data: http://99.28.48.185/tor/status-vote/current/consensus, but for the server which is now lacking the flags, nothing is returned: http://80.240.141.246/tor/status-vote/current/consensus. As far as I know, these servers are identically configured apart from the nicknames, fingerprints, and bandwidth. And as I said, initially both servers showed Directory flags. I am running on Debian, and so tried "service for restart” without effect. Hate to have to reinstall to get Directory services up again… Best regards, Spencer On Aug 13, 2014, at 1:28 PM, tor-relays-request(a)lists.torproject.org wrote: > > > From: Matthew Finkel <matthew.finkel(a)gmail.com> > Subject: Re: [tor-relays] Directory Server Issue > Date: August 13, 2014 at 12:08:58 PM EDT > To: tor-relays(a)lists.torproject.org > Reply-To: tor-relays(a)lists.torproject.org > > > On Wed, Aug 13, 2014 at 10:32:45AM -0400, Spencer Rhodes wrote: >> Hi, >> >> I have a server (triratna) which I recently put up, which operates on ports 80 and 443, and which initially showed a Directory Server flag. After several days of operation, however, the directory flag disappeared from both the torstatus listing and from the arm display on the console. >> >> I would like to know if there is a way to verify that directory services are in fact working, and if so, determine why the server is not flagged properly. I found some old postings to the effect that one could browse to server://tor or server://tor/status/all, but this does not seem to be true any more. > > Hi Spencer, > > This should still work. Try using > http://<ip address>:<DirPort>/tor/status-vote/current/consensus > to fetch the current consensus. You can also fetch individual relay > descriptors using a similar URI. > > If you provide your relay fingerprint someone may be able to help > further. I tried looking up the name you gave, but I couldn't find > it in either Globe[0] nor Atlas[1]. > > Thanks for running a relay! > > - Matt > > > [0] https://globe.torproject.org/#/search/query=triratna > [1] https://atlas.torproject.org/#search/triratna > >

1 1

Re: [tor-relays] Advertised Bandwidth
by Mike Patton 16 Aug '14

16 Aug '14

Hey there, The advertised bandwidth will increase gradually. Well mine did. M. On 16/08/2014 10:28 am, IceFish ThreeTwo <threehundredthirtytwofishes(a)gmail.com> wrote: > > Hello! > > I'm unclear as to what the "Advertised Bandwidth" is on Atlas. My node has it's bandwidth set to 700Kb/s, however on Atlas the Advertised Bandwidth is around 7Kb/s. I'm on day three of running this relay and I have read the Early Lifecycle blog post, but I'm still confused as to why the Advertised Bandwidth is a hundredth of what I have it set to. > > Thank you! > Ice Fish > > > -- > Sent from my iPhone

3 2