- tor-relays - lists.torproject.org

Question on running bridge nodes
by Tor externet co uk 11 Oct '14

11 Oct '14

Hi, I've set up a bridge node in the previous few weeks, but have had to put a bandwidth limit on, as I only have 10TB of traffic per month before my ISP will start throttling me to 100k/sec. I wondered whether it was more helpful to the Tor network as a whole to have have a very fast node which hibernated every 12-15 hours, or if I throttled Tor traffic, so that the node was more stable. I'll confess that I'm far more au fait with the politics of Tor than I am of the exact ins and outs of how the technology works. Any help would be gratefully received. Thanks L

2 2

Re: [tor-relays] Slow relay speeds for Australian geographic location(s)
by teor 11 Oct '14

11 Oct '14

On 12 Oct 2014, at 09:32 , tor-relays-request(a)lists.torproject.org wrote: > Date: Sun, 12 Oct 2014 06:19:16 +1100 > From: Mathew <wired.kid(a)gmail.com> > To: tor-relays(a)lists.torproject.org > Subject: [tor-relays] Slow relay speeds for Australian geographic > location(s) > > Hello all, > > I run a non-exit relay in Australia. My relay has been running for almost > 15 days and has seen very little traffic. > I have a 100/40 fibre connection and bandwidth is set at 2MB/s and 2.5MB/s > burst. > > The mean read/write is 3.22kb/s and the advertised bandwidth constantly > varies between 100-800kb/s which is obviously a fraction of my available > bandwidth. > > Do relays located in less tor frequented countries see much less traffic or > something? I have ports set at 443 and dirport 9030, is this an optimal > port setting? > > Anyone with helpful information would be appreciated. My relay is 1337m8 if > anyone wants to look at the traffic. > > Thanks A few hints: 1. The Tor network currently has an oversupply of non-exit relays. Therefore, your relay will never be fully utilised unless it is incredibly fast and stable over the longer term (months). 2. Your relay doesn't have the Guard flag yet. When it gets it, there will be a drop in traffic as your relay changes roles from middle to guard, then an increase overall. [-1] 3. If you look at the graphs for your relay on Atlas [0], there is a gradual increase in bandwidth. This should keep gradually increasing, apart from the guard transition in point #2. 4. It's unlikely your relay is compute-bound (at 100% CPU) or network-bound (saturating any network links). But it might be resource-bound (again, this seems unlikely at the levels you're seeing). Can your NAT box handle ~5000 simultaneous TCP connections/open files/NAT translations? (Mine can't, it reboots occasionally.) Can your Windows server handle ~5000 simultaneous TCP connections? 5. Most of the Tor network is outside Australia. How is TPG's international bandwidth for the NBN? Are the coping? Or are they shaping international transfers? (Please feel free to correct my ISP and network assumptions.) What do you get if you use an online bandwidth test server located in the US or Europe? What are your typical upload speeds on the link? 6. The bandwidth authorities are outside Australia. This appears to produce greater bandwidth measurement variance. To measure bandwidth, the authorities build a circuit between it, your router, and another router with similar bandwidth. More than likely, the authority and other router are a long way away from Australia. My experience has been variance between 50 - 120 KB/s on a 120KB/s set bandwidth. (Which is a little too low for a Tor relay, by the way.) And to answer your questions: A. Tor is country-agnostic, but network-aware by default. Faster, stable relays get priority. B. In my experience, 443 gets more bandwidth than the Tor default port of 9001. You could try setting up another instance on 9001, and see if it experiences the same issues after a few weeks. You could also try paste-binning your torrc, and we'll look for specifics. [-1]: https://blog.torproject.org/blog/lifecycle-of-a-new-relay [0]: https://atlas.torproject.org/ teor pgp 0xABFED1AC hkp://pgp.mit.edu/ https://gist.github.com/teor2345/d033b8ce0a99adbc89c5 http://0bin.net/paste/Mu92kPyphK0bqmbA#Zvt3gzMrSCAwDN6GKsUk7Q8G-eG+Y+BLpe7w…

1 0

Few questions about relaying
by Blaise Gagnon 11 Oct '14

11 Oct '14

Hi and many thanks for developping this project ! I have a dedicated 200Mb (25 MB) fiber optics connection and a dedicated quad-core Linux server (64). What is the best setup to get maximum bandwidth usage ? I'm still stuck at 46.4Kb measured speed and 3,51MB advertised bandwidth. The server has direct connection to the Internet. Fingerprint : 5EF740BB88C75915F8316DFEC8F1C8631FF26F12 Should I run multiple relays on the same machine/IP ? Thanks !

6 17

introduction
by Mirimir 10 Oct '14

10 Oct '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I don't know whether introductions are hopelessly old school on this list, but here's a brief one. Although I've used Tor for many years, it's been just about a year since I decided to understand it better. I've also been catching up on the literature. Now I'm considering the possibility of running some relays. I've read some of the instructions on torservers.net, and have a few questions about security. I'm presuming that this is the best place to ask them. I won't be signing all of my list messages, by the way. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJUNy7oAAoJEGINZVEXwuQ+GPQH/imif4StAJPp6io3zBEkt3iu rNN94iZw+EukXnCbVMTKW686H/6l0NbQ+0iHQ+RkUeX7xUcvV7+rqB9E+nIB7bx/ DOXCDvyqOP2uUeYmxgkTxKz33jD3eMV+MGprB/9oCdMozur4yJmKjf+oYY+6+PT5 WO9Xf7rBbL9KuBqOY7iLCpRtLTvg31vkjz8o3pQFeJYm+aKKRnUjcNcwtroxxdUD c8xe5r8CtFkLL0OX8NuaRX2y3WXeu2GS/8fEEv95J3yqFPTCJ6K9hxmwRfbjG7QT wi/SZ2FEfdAzdvXwT3qd4E5CYMB8RKXVqArlsvmKs7EHbZSVzEqbTbzKBYBvckc= =P0Ua -----END PGP SIGNATURE-----

2 1

questions about attacks involving single-end measurements of available bandwidth
by Mirimir 09 Oct '14

09 Oct '14

In planning how to configure Tor relays, I've been considering various known attacks. Most involve systemic issues about design and implementation, and so aren't relevant to relay configuration. But there is one that seems relevant, and addressable. I've been reading the work of Sambuddho Chakravarty and coworkers, in particular his thesis and a technical report on LinkWidth.[0],[1] What seems relevant here are deanonymization attacks on clients and hidden services that rely on traffic watermarking in conjunction with single-end measurements of available relay bandwidth. I am somewhat dubious about real-world workability. Fast relays simultaneously handle numerous connections, and so it's arguable that no single connection substantially perturbs available bandwidth. But on the other hand, it takes months for traffic through new relays to ramp up, and perhaps they are easier to scope while relatively idle. Regardless, Tor relays are very specialized. And so it should be trivial to craft iptables rules that prevent responses to LinkWidth and other tools for single-end bandwidth measurement, but don't interfere with anything essential. However, I haven't come across anything that seems relevant. Has this threat been addressed? Or am I missing something that complicates the response? Or conversely, is it not something to worry about? [0] Chakravarty (2014) Traffic Analysis Attacks and Defenses in Low Latency Anonymous Communication (PhD thesis) http://www.cs.columbia.edu/~angelos/Papers/theses/sambuddho_thesis.pdf [1] Chakravarty et al. (2008) LinkWidth: A Method to Measure Link Capacity and Available Bandwidth using Single-End Probes http://academiccommons.columbia.edu/download/fedora_content/download/ac:110…

1 0

Need Routing Info on Relays
by Tor Zilla 09 Oct '14

09 Oct '14

Hi Folks, I am trying to figure out how the packet flows over a Tor network.. There is a mix of information.. Some claim that the ISP is not aware of the payload as the complete data is encrypted whereas some say that your ISP is not used at all when using Tor network. AFAIK my packets go to the outer web via my ISP and there is no way to by pass that. I might be wrong. Can someone give me a detailed packet flow? Thanks, Torzilla11

3 8

Re: [tor-relays] . obfsproxy not working on bridge relay
by Jan Nielsen 09 Oct '14

09 Oct '14

I believe that error means obfsproxy was either not installed correctly or your torrc is not pointing to the correct location. Follow the below link's instructions. Also, a quick google search for that error provided resukts from this mailing list. Follow its instructions as well. https://lists.torproject.org/pipermail/tor-relays/2014-February/003892.html On Oct 8, 2014 6:00 AM, <tor-relays-request(a)lists.torproject.org> wrote: > Send tor-relays mailing list submissions to > tor-relays(a)lists.torproject.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > or, via email, send a message with subject or body 'help' to > tor-relays-request(a)lists.torproject.org > > You can reach the person managing the list at > tor-relays-owner(a)lists.torproject.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of tor-relays digest..." > > Today's Topics: > > 1. obfsproxy not working on bridge relay (jchase) > 2. Re: obfsproxy not working on bridge relay (George Kadianakis) > > > ---------- Forwarded message ---------- > From: jchase <jchase(a)riseup.net> > To: tor-relays(a)lists.torproject.org > Cc: > Date: Wed, 08 Oct 2014 10:36:39 +0000 > Subject: [tor-relays] obfsproxy not working on bridge relay > Hi, > Due to m limited bandwidth I've decided to turn my relay into a bridge. > I seem to have everything right except if I restart tor I get a warning > that "managed proxy obfsproxy is 'closed'". I'm sure this has come up in > the past but I can find it in the archives. > In torrc I have: > SocksPort 0 > ORPort 9001 > Exitpolicy reject *:* > Log notice file /var/log/tor/notices.log > Contact info [] > Nickname rasptorholland > BridgeRelay 1 > ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed > ServerTransportListenAddr obfs3 0.0.0.0:9030 > DisableDebuggerAttachment 0 > > Both ports are forwarded, though I can't find proof that tor is actually > using port 9030. > > Any suggestions? > -J. Chase > > > > > ---------- Forwarded message ---------- > From: George Kadianakis <desnacked(a)riseup.net> > To: tor-relays(a)lists.torproject.org > Cc: > Date: Wed, 08 Oct 2014 11:41:22 +0100 > Subject: Re: [tor-relays] obfsproxy not working on bridge relay > jchase <jchase(a)riseup.net> writes: > > > Hi, > > Due to m limited bandwidth I've decided to turn my relay into a bridge. > > I seem to have everything right except if I restart tor I get a warning > > that "managed proxy obfsproxy is 'closed'". I'm sure this has come up in > > the past but I can find it in the archives. > > In torrc I have: > > SocksPort 0 > > ORPort 9001 > > Exitpolicy reject *:* > > Log notice file /var/log/tor/notices.log > > Contact info [] > > Nickname rasptorholland > > BridgeRelay 1 > > ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed > > ServerTransportListenAddr obfs3 0.0.0.0:9030 > > DisableDebuggerAttachment 0 > > > > Hello, > > how did you install obfsproxy? Which installation instructions did you > follow? Seems like you didn't follow: > https://www.torproject.org/projects/obfsproxy-instructions.html.en > > What happens if you run '/usr/bin/obfsproxy managed' in a terminal? > > > _______________________________________________ > tor-relays mailing list > tor-relays(a)lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > >

1 0

Bridges and advertised bandwidth
by Jan Nielsen 09 Oct '14

09 Oct '14

Hi everyone. I am currently operating 4 bridges on VPSs. They all appear to working correctly. However, 2 of the 4 bridges have 0kb/s as their advertised bandwidth while the other two are advertising around 100KB/s. Is there a reason for the 0kb/s? Does this indicate an error in my bridges or simply a gitch? See this for reference. https://globe.torproject.org/#/search/query=acrossthebridge Thank you.

1 0

How many exits can we run?
by Eric Hocking 09 Oct '14

09 Oct '14

Hi everyone, Is there a limit to how many exit nodes we can run?

3 2

Re: [tor-relays] obfsproxy not working on bridge relay - solved?
by jchase 08 Oct '14

08 Oct '14

> From: George Kadianakis <desnacked(a)riseup.net> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] obfsproxy not working on bridge relay > Message-ID: <874mve973h.fsf(a)riseup.net> > Content-Type: text/plain > > jchase <jchase(a)riseup.net> writes: > >> Hi, >> Due to m limited bandwidth I've decided to turn my relay into a bridge. >> I seem to have everything right except if I restart tor I get a warning >> that "managed proxy obfsproxy is 'closed'". I'm sure this has come up in >> the past but I can find it in the archives. >> In torrc I have: >> SocksPort 0 >> ORPort 9001 >> Exitpolicy reject *:* >> Log notice file /var/log/tor/notices.log >> Contact info [] >> Nickname rasptorholland >> BridgeRelay 1 >> ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed >> ServerTransportListenAddr obfs3 0.0.0.0:9030 >> DisableDebuggerAttachment 0 >> > > Hello, > > how did you install obfsproxy? Which installation instructions did you > follow? Seems like you didn't follow: > https://www.torproject.org/projects/obfsproxy-instructions.html.en > > What happens if you run '/usr/bin/obfsproxy managed' in a terminal? Hello, Thanks for your advice! I had installed obfsproxy with apt-get on a Pi. I removed that and tried pip. It took me a while to find out that pip was actually python-pip. (Maybe the Tor website could be more specific about that.) That install went well. You asked me to see what happened after the command '/usr/bin/obfsproxy managed'. It took me a while to find that obfsproxy was installed in /usr/local/ , not in /usr/bin/ . And now, until further notice from tor, things seem to work fine. Thanks, J. Chase

1 0