- tor-relays - lists.torproject.org

Do bridges care about DNS?
by Steve Snyder 24 Jan '12

24 Jan '12

Do bridges have a need for name resolution, or it it just a matter of passing a packet from one IP address to another (i.e. from user to Tor node)? Thanks.

1 0

Re: [tor-relays] How can I tell if my bridge is working?
by Scott Bennett 22 Jan '12

22 Jan '12

On Sun, 22 Jan 2012 05:58:45 -0500 Roger Dingledine <arma(a)mit.edu> wrote: >On Thu, Jan 19, 2012 at 08:35:30PM -0500, Steve Snyder wrote: >> New operator of a Tor bridge here. How can I tell that it is being used? >> >> With a regular relay I can look up the stats on TorStatus, or I can see >> that there are n current connections. But a bridge won't be published, >> and the lower volume of traffic means that there may not be many active >> connections at any given time. >> >> So how do I know if it is working? I mean beyond the absence of any >> errors logged? > >Answer 1: absence of any errors logged. Then just trust. :) > >Answer 2: Use a Tor controller. Vidalia has a "who has used my bridge >lately?" button you can push to learn by-country statistics. Or try >'arm' if you prefer command-line controllers. > >Answer 3: We publish sanitized bridge descriptors on the metrics site: >https://metrics.torproject.org/data.html#bridgedesc >We're working on usable interfaces to let you look up the descriptor >for your bridge (including the usage statistics that it publishes). Stay >tuned. > Answer 4: this isn't exactly what you want, yet it still provides relevant information. Use the HeartbeatPeriod command in your torrc file to provide usage information on a periodic basis with your choice of period. The message logged gives the uptime in days and hours and a rounded figure for bytes sent and bytes received since initialization, so if your node is *only* used as a bridge, these messages will give you rough idea of your bridge's usage. Note, of course, that some of the traffic will be stuff that your node needs for its operation, e.g., a consensus file. Be advised that each period incurs about 1 s of delay in logging the information, so if you want information every hour exactly, for example, you need to specify a period of 3599 s, not 3600 s. Note, too, that the default period is 21,600 s, or 6 hr. Again, "HearbeatPeriod 21599 seconds" should yield a message logged every six hours exactly. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at cs.niu.edu * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************

2 1

Tor Status graphs
by Geoff Down 22 Jan '12

22 Jan '12

Hi, the read/write graphs in my relay's TorStatus.blutmagie.de page have been broken for some time (flat-lined) but I assumed that was down to my old software. However, I see that all the relays' pages are the same. Is this data no longer available? I had a quick look in the archives for an answer. GD -- http://www.fastmail.fm - IMAP accessible web-mail

3 2

How can I tell if my bridge is working?
by Steve Snyder 22 Jan '12

22 Jan '12

New operator of a Tor bridge here. How can I tell that it is being used? With a regular relay I can look up the stats on TorStatus, or I can see that there are n current connections. But a bridge won't be published, and the lower volume of traffic means that there may not be many active connections at any given time. So how do I know if it is working? I mean beyond the absence of any errors logged? Thanks.

4 3

Re: [tor-relays] How can I tell if my bridge is working?
by robbie macg 21 Jan '12

21 Jan '12

Hi, I may have misunderstood the question. I think the simplest way to determine if your bridge is up and running correctly is to check the contents of /var/log/tor/log. Alternatively, try using Vidalia to connect to your own bridge. and log an error. These methods often work well for newer users. You may have something more sophisticated in mind or be trying to accomplish some thing else. If hat's the case, I apologize. Cheers, Robbie > Message: 1 > Date: Fri, 20 Jan 2012 09:17:16 -0500 > From: "cmeclax-sazri" <cmeclax-sazri(a)ixazon.dynip.com> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] How can I tell if my bridge is working? > Message-ID: <201201200917.16804.cmeclax-sazri(a)ixazon.dynip.com> > Content-Type: Text/Plain; charset="iso-8859-1" > > On Thursday, January 19, 2012 20:35:30 Steve Snyder wrote: >> New operator of a Tor bridge here. How can I tell that it is being used? > > Telnet to port 9051 and type ?authenticate "blurdyboop"?. Then type > ?setevents > bw? and it'll tell you how many bytes go in and out. I'm not sure how to > tell > that there are client connections, but it's probably another setevents > command. > > cmeclax > > > ------------------------------ > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > > > End of tor-relays Digest, Vol 12, Issue 19 > ****************************************** >

1 0

Tor Deprecation Notice
by Damian Johnson 20 Jan '12

20 Jan '12

Hi all. As per ticket 4788 [1] we'll soon be removing relays that are out of date and no longer safe to run, which includes anything older than version 0.2.1.30. When I last checked this included 257 relays [2] and I've already notified the 107 of those that had contact information available. If you're running one of those relays then you'll need to upgrade to keep operating. Sorry about the inconvenience and thanks for running a relay! -Damian [1] https://trac.torproject.org/projects/tor/ticket/4788 [2] https://trac.torproject.org/projects/tor/attachment/ticket/4788/old_relays.…

3 2

[warn] Request too large from address '[scrubbed]' to DirPort. Closing.
by Klaus Layer 19 Jan '12

19 Jan '12

Hi, last night the log of one of my nodes showed within 2 minutes about 160 of these messages. Traffic stats show that the incoming bandwidth increased from the average of 300 Mbit/s to more than 400 Mbit/s, where at the same time outgoing traffic dropped. From the peak I see, the requests must have been really big. Does anyone noticed this on other tor servers too? Regards, Klaus

3 2

Re: [tor-relays] logging failure in 0.2.3.10-alpha
by Scott Bennett 19 Jan '12

19 Jan '12

On Thu, 19 Jan 2012 09:39:55 -0800 (PST) CyberRax <cyberrax(a)yahoo.com> wrote: >----- Original Message ----- > >> From: Scott Bennett <bennett(a)cs.niu.edu> >> =A0 =A0 I delayed moving from 0.2.3.7-alpha to 0.2.3.10-alpha until now = >[...] >>=A0=A0=A0=A0 ...no log files were created > >2 thoughts: >a) does the user have access to the logging folder? (_tor rather than root) >b) if you're building through FreeBSD's ports system then the installed /us= >r/local/etc/rc.d/tor gives the log filename from commandline which, >=A0=A0 if I understand correctly, overrides the settings given in torrc (th= >at change was made in 0.2.3.9 or so) *Very* good clue! Thank you very much! Several years ago, I did install a version of tor via the ports tree, but soon switched to building it myself due to delays in new versions being incorporated into the ports and a concern over potentially losing key files, torrc, etc. if I needed to remove it temporarily or during updates. However, I left the infrastructure stuff (e.g., the /usr/local/etc/rc.d/tor script and the /var/db/tor and /var/log/tor directories) in place. The version information line in it still says, # $FreeBSD: ports/security/tor/files/tor.in,v 1.2 2006/08/06 12:26:25 arved Exp $ :-) Anyway, I deleted the --log option from the line that starts/stops tor, and it created both log files this time when I started it. The original script specified /var/log/tor as a log file, so I must have long ago changed it to a directory to hold more than one log file and then forgotten I had done that. /var/log is a directory only writeable by root anyway, and /var/log/tor is a directory only writeable by _tor, so tor would not have been able to create a file called /var/log/tor. Thanks again for the pointer! Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at cs.niu.edu * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************

1 0

https://metrics.torproject.org/networkstatus.html
by Sebastian Urbach 19 Jan '12

19 Jan '12

Hi, Im receiving the following error since a few days: Proxy Error The proxy server received an invalid response from an upstream server. The proxy server could not handle the request GET /networkstatus.html. Reason: Error reading from remote server Apache Server at metrics.torproject.org Port 443 Url: https://metrics.torproject.org/networkstatus.html Anyone out there to fix it ;-) ? -- Mit freundlichen Grüßen / Yours sincerely Sebastian Urbach -------------------------------------------------------- Religion is something left over from the infancy of our intelligence, it will fade away as we adopt reason and science as our guidelines. -------------------------------------------------------- Bertrand Arthur William Russell (1872-1970), British philosopher, logician, mathematician, historian, and social critic.

2 1

logging failure in 0.2.3.10-alpha
by Scott Bennett 19 Jan '12

19 Jan '12

I delayed moving from 0.2.3.7-alpha to 0.2.3.10-alpha until now because the latter failed to build from source under FreeBSD 7.4-STABLE. Oddly enough, now that I've upgraded to 8.2-STABLE, it appears to build just fine. So I ran a tor --verify-config on my existing torrc file, which was confirmed to be okay by 0.2.3.10-alpha. Next, I fired it up, and...no log files were created, :-( so I had no idea whether it was working, had encountered any difficulties during initialization, etc. It should have created two log files in /var/log/tor/, one for "notice" and above, and one for "info" and above. I tried a SIGHUP to get it to reread torrc, which made no observable change, as expected. After pondering the situation for a few minutes, I decided to shut it down. If tor can't communicate to its operator, then it can't be safely run. If anyone can feed me a clue about what to try in hopes of fixing this, I'd greatly appreciate it. If there are no helpful ideas forthcoming by this evening, I'll likely go back to 0.2.3.7-alpha in order to have a working node. Thanks much. Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at cs.niu.edu * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************

2 1