Re: [tor-relays] Help the Tor Project by running a fast unpublished bridge
ON Saturday, August 11. 2012, 18:25:03 Roger Dingledine wrote: > The constraints are: > * 100mbit+ connectivity, though in practice I expect they will spend > most of their time doing far less than that. > * No more than 2 bridges per /24. If you're running fast (100mbit+) > exits (which is more important), exits on that /24 count toward this 2. > * No more than 7 bridges total per data center. > > If you could set up 1 (or 2, or 20) and send me the address(es) privately, > that would be grand. If I ask my ISP for additional IPs, how do I check these constraints, given that I don't know other bridges/exits running at my ISP/DC. Regards, Torland ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Help the Tor Project by running a fast unpublished bridge
>> Sorry for exposing the internals of running >> a non-profit. But I think transparency is especially important here. :) > > I don't know why you feel sorry. Transparency is important for > non-profit, at least for most I guess. Non-profit is just a tax and legal designation. After any necessary compliance with that, the degree of transparency, salaries paid, competitiveness, degree of being closely held, and indeed all other things... is completely variable. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Help the Tor Project by running a fast unpublished bridge
Roger Dingledine: Hi Roger, > We're in an interesting situation here, where we can use their bridge > funding for other more important things if we don't spent it all on > bridges. So maybe the subject should have been the more counterintuitive > "Help fund Tor bundle usability by running a fast unpublished bridge". > > Another option would be to give it to Moritz et al at torservers.net > so they can run more fast exits -- at which point Moritz might end up > sending a similar mail saying "Help us run more exit relays by running > a fast unpublished bridge". > > Now that I think about it, maybe the best way to phrase it would be as > a matching donation: "Run a fast unpublished bridge with 2 IP addresses, > and we have a funder who will match your donation by giving $200-300/mo > to Tor." That's the reasoning that led me to say it's a great way to > contribute to Tor if you can't run a fast relay yourself. Sounds all plausible to me. > Another model I've been pondering is to offer people some funding to > run a fast *non*-exit relay along with a pair of extra IP addresses for > these unpublished bridges. But on the theory that exits are more scarce > than non-exits (and I don't want to muddy the current exit experiment > with even more money), I figured it would be better to separate the roles. Understandable. > This discussion really goes back to a simple question: is it better to > use our funding for more design and development, or for strengthening > the network? For exit relays, I think choosing "strengthen the network" > is a great and worthwhile experiment. I agree on the exits. Better design and more development could be beneficial to Tor. > But for bridges, since the current > Tor transport and current bridge distribution strategies are not great, In the long run you are right. New fast bridges *might* improve the situation for censored users, but that won't last very long. > I think it's better to use funding for better designs and better code. Yes, that's much better over time. > I should note that I actually encouraged VoA to want unpublished bridges: > if we set up fast bridges and published them via bridges.torproject.org > today, they'd get blocked quickly in China. They have fixed IP addresses which would result in permanently blocked bridges. I wonder how good the manual bridge distribution is. When VoA is fine with spending their money for other stuff as long as their goal is achieved it's reasonable. > I'm especially hoping to hear from volunteers for whom setting up a few > extra bridges is basically free -- for example, those already running > fast non-exit relays who have a few more IP addresses nearby. This is > also a nice way for students at universities to get involved if they're > not ready to run a fast public relay quite yet. That would be beneficial to Tor. > I hope that helps to explain. For me it was helpful. I understood the goal in the first place, but was a little concerned. After all I guess spending money for design and code is more helpful than bridges for anyone. > Sorry for exposing the internals of running > a non-profit. But I think transparency is especially important here. :) I don't know why you feel sorry. Transparency is important for non-profit, at least for most I guess. Sebastian ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Help the Tor Project by running a fast unpublished bridge
On 13.08.2012 12:56, Andrew Beveridge wrote: > I guess I fit into that category - the exit I run (mentioned previously > in the exit funding thread) is on a server which has about 3 free IP > addresses which I'm not using right now - I could easily use them as > fast unpublished bridges if somebody explained briefly how. Thank you! First, as you want to run both exit and bridge on one server, it will be useful to switch to a modified init script that makes it easier to handle multiple Tors: cd /etc/init.d wget -O tor https://www.torservers.net/misc/config/initd-tor chmod +x tor Example usage: # ls /etc/tor tor0.cfg tor1.cfg tor2.cfg tor3.cfg # /etc/init.d/tor start# starts tor 0-3 # /etc/init.d/tor stop # stops tor 0-3 # /etc/init.d tor reload tor2 tor3 # /etc/init.d/tor stop tor1 Next, in /etc/tor, rename your current torrc to tor0.cfg and create a new file called tor1.cfg: - snip - ## separate directories per tor process DataDirectory /var/lib/tor/bridge PidFile /var/run/tor/tor-bridge.pid Log notice file /var/log/tor/notices-bridge.log Address 109.163.233.200 # your second external IP OutboundBindAddress 109.163.233.200 ORListenAddress 109.163.233.200:443 ## default bridge port 443 ORPort 443 ## private bridge PublishServerDescriptor 0 SocksPort 0 BridgeRelay 1 Exitpolicy reject *:* - snip - -- Moritz Bartl https://www.torservers.net/ ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] Help the Tor Project by running a fast unpublished bridge
On Mon, Aug 13, 2012 at 5:55 AM, Roger Dingledine wrote: > > I'm especially hoping to hear from volunteers for whom setting up a few > extra bridges is basically free -- for example, those already running > fast non-exit relays who have a few more IP addresses nearby. This is > also a nice way for students at universities to get involved if they're > not ready to run a fast public relay quite yet. > > --Roger > > ___ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > I guess I fit into that category - the exit I run (mentioned previously in the exit funding thread) is on a server which has about 3 free IP addresses which I'm not using right now - I could easily use them as fast unpublished bridges if somebody explained briefly how. -- * Andrew Beveridge, **Tor lurker / sympathizer / advocate, exit node maintainer.* Director / Computer Repair Technician @ TechFix LTD [ http://www.techfixuk.com] Freelance Web Developer @ [http://www.andrewbeveridge.co.uk] Tel/Fax: +44 (0) 1383269735 | * Email: t...@techfixuk.com * * 5 Drum Road, Kelty, KY4 0DQ, Scotland * ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
