- tor-relays - lists.torproject.org

badexit 03F84EA2E09CF427A519C65479DC0BF0D72886A6
by grarpamp 08 Jan '15

08 Jan '15

router Tansam 79.143.87.234 443 0 0 03F84EA2E09CF427A519C65479DC0BF0D72886A6 Appears to be having trouble with, or is doing something with, http versions of https en.wikipedia.org articles. They're either blank or stripped of framework.

1 0

missing pluggable transport
by qq1693129601 08 Jan '15

08 Jan '15

When open tor-browser, it says Tor failed to establish a Tor network connection. Connecting to a relay directory failed (missing pluggable transport). The log is below, could anyone help? ----- 01/06/2015 15:03:35.786 [NOTICE] DisableNetwork is set. Tor will not make or accept non-control network connections. Shutting down all existing connections. 01/06/2015 15:03:35.786 [NOTICE] Opening Socks listener on 127.0.0.1:9150 01/06/2015 15:03:36.711 [WARN] The communication stream of managed proxy './TorBrowser/Tor/PluggableTransports/fteproxy.bin' is 'closed'. Most probably the managed proxy stopped running. This might be a bug of the managed proxy, a bug of Tor, or a misconfiguration. Please enable logging on your managed proxy and check the logs for errors. 01/06/2015 15:03:36.711 [NOTICE] Failed to terminate process with PID '30230' ('Success'). 01/06/2015 15:03:37.711 [NOTICE] Bootstrapped 5%: Connecting to directory server 01/06/2015 15:03:37.711 [WARN] We were supposed to connect to bridge '[2001:49f0:d002:1::2]:80' using pluggable transport 'fte', but we can't find a pluggable transport proxy supporting 'fte'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 01/06/2015 15:03:37.712 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Can't connect to bridge; PT_MISSING; count 1; recommendation warn) 01/06/2015 15:03:39.270 [WARN] We were supposed to connect to bridge '[2001:49f0:d00a:1::c]:80' using pluggable transport 'fte', but we can't find a pluggable transport proxy supporting 'fte'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running. 01/06/2015 15:03:39.270 [WARN] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Can't connect to bridge; PT_MISSING; count 2; recommendation warn)

2 1

Exit Node / iptables / massive attempts on DPT 8118 ?
by rush23＠gmx.net 07 Jan '15

07 Jan '15

5 16

Re: [tor-relays] Help - My relay consensus has been stripped back to 20
by bigbudtor＠Safe-mail.net 06 Jan '15

06 Jan '15

Argh - yes you are right. It was fine again last night and yes it is back down to 20. What the hell is going on? I find it quite troubling that nobody seems to know (or wants to say) why these relays are getting disabled. cheers BB -------- Original Message -------- From: tor-relays-request(a)lists.torproject.org Apparently from: tor-relays-bounces(a)lists.torproject.org To: tor-relays(a)lists.torproject.org Subject: tor-relays Digest, Vol 48, Issue 21 Date: Tue, 06 Jan 2015 12:00:02 +0000 >Yours and mine are back to 20. >On 05.01.2015 03:37 PM, bigbudtor at Safe-mail.net wrote: >> -------- Original Message -------- >> From: tor-relays-request at lists.torproject.org >> Apparently from: tor-relays-bounces at lists.torproject.org >> To: tor-relays at lists.torproject.org >> Subject: tor-relays Digest, Vol 48, Issue 15 >> Date: Mon, 05 Jan 2015 11:05:49 +0000 >> >> >>> Message: 3 >>> Date: Mon, 05 Jan 2015 11:36:59 +0100 >>> From: Network Operations Center <noc at schokomil.ch> >>> To: tor-relays at lists.torproject.org >>> Subject: Re: [tor-relays] Help - My relay consensus has been stripped >>> back to 20 >>> Message-ID: <84a966b4ad0f4d6a230d7b51f1d6b42f at schokomil.ch> >>> Content-Type: text/plain; charset=UTF-8; format=flowed >>> >>> Mine just jumped to 18,000, again I'd like to stress that I have not >>> changed anything in my torrc: >>> >>> https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F2… >> >> Yup, me too. Seems to be back thankfully. >> >> Would love to know why though.... >> >> best >> >> BB >> _______________________________________________ >> tor-relays mailing list >> tor-relays at lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 0

Re: [tor-relays] Help - My relay consensus has been stripped back to 20
by bigbudtor＠Safe-mail.net 06 Jan '15

06 Jan '15

-------- Original Message -------- From: tor-relays-request(a)lists.torproject.org Apparently from: tor-relays-bounces(a)lists.torproject.org To: tor-relays(a)lists.torproject.org Subject: tor-relays Digest, Vol 48, Issue 15 Date: Mon, 05 Jan 2015 11:05:49 +0000 > Message: 3 > Date: Mon, 05 Jan 2015 11:36:59 +0100 > From: Network Operations Center <noc(a)schokomil.ch> > To: tor-relays(a)lists.torproject.org > Subject: Re: [tor-relays] Help - My relay consensus has been stripped > back to 20 > Message-ID: <84a966b4ad0f4d6a230d7b51f1d6b42f(a)schokomil.ch> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Mine just jumped to 18,000, again I'd like to stress that I have not > changed anything in my torrc: > > https://atlas.torproject.org/#details/3D7E274A87D9A89AF064C13D1EE4CA1F184F2… Yup, me too. Seems to be back thankfully. Would love to know why though.... best BB

2 1

Re: [tor-relays] how to monitor traffick through a bridge
by starlight.2015q1＠binnacle.cx 06 Jan '15

06 Jan '15

>Thank you very much for all the precious advice. >I am running tor on linux. I second the suggestion of applying 'iptables' to collecting traffic statistics. Lot of ways to go about it but here's something similar to the approach I'm using. By having separate entries for established and new connections on the input side, one can see both how much traffic is arriving and how many connection requests are arriving. Of if your node is attacked, the second new-connection catcher will show huge volumes of DOS traffic. Also note the separate counters for ssh and OR port traffic, so you can distinguish maintenance and utilization activity. Feel free to change all the port assignments as suits you, even the ssh one. The example uses defaults for illustration. Is recommended that the OR port be assigned randomly in order to make discovery via 'zmap' more difficult. 22 ssh 9001 OR 443 obfs3 80 fte 587 scramblesuit 993 obfs4 The 'iptables' file loses the .txt extension and CR characters (addded for easier MUA clicking) and generally goes in /etc/sysconfig/iptables. Also attaching an example statistics display command and output, and a batch job for collecting the information automatically every day.

1 0

how to monitor traffick through a bridge
by mattia 05 Jan '15

05 Jan '15

Hi, I would like to know how one can monitor traffic that goes through a bridge. I have set one up and would like to know whether it is being used or not, and how much. Thanks!

5 6

Fwd: [tor-talk] please advise on renting a gigabit capable dedicated server
by Libertas 05 Jan '15

05 Jan '15

In case there are people that don't subscribe to both. -------- Forwarded Message -------- Subject: [tor-talk] please advise on renting a gigabit capable dedicated server Date: Fri, 2 Jan 2015 19:31:05 -0600 From: Christopher Yeager <jager(a)farmhouseproject.org> Reply-To: tor-talk(a)lists.torproject.org To: tor-talk(a)lists.torproject.org Hi tor users, my coworkers and I are considering getting together to run a gigabit exit relay and are curious if you all have advice as to the best place to go shopping for a server with 1gbps dedicated bandwidth in a location that is helpful to the network. Someone on irc pointed me to this list, but I'm happy to ask on another if it would be more appropriate. Thanks in advance! -- tor-talk mailing list - tor-talk(a)lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

4 4

new VPS bridge bandwidth under-reported
by starlight.2015q1＠binnacle.cx 05 Jan '15

05 Jan '15

Hello, Just setup a new bridge running 0.2.6.1-alpha and it's working fine. The bridge is running in a Linux container VPS and appears to have an iptables traffic-shaped bandwidth limit of 400KB. Can browse and download files through it with decent performance using obfs4. However self-measurement of bandwidth, after starting at around 200Kbytes has steadily declined until now its showing 8KB and has lost the "fast" flag. At this point the bridge has yet to attract any traffic other then my testing usage--but it works just fine nevertheless. I suspect that latency for small transfers is fairly bad (in the sense of milliseconds, rather than seconds) and that this may be distorting bandwidth metrics. Also the number of bytes transferred is close to zero, which does not seem likely to help the situation. Should I be concerned about it? Anything anyone can recommend to correct it aside from looking another VPS provider? Does the advertised bandwidth have much effect on whether the bridge will be disseminated by the bridge database system? No "stable" flag yet, but not enough time has passed for this to happen. Thanks

3 4

Re: [tor-relays] Help - My relay consensus has been stripped back to 20
by bigbudtor＠Safe-mail.net 05 Jan '15

05 Jan '15

> > Message: 3 > Date: Sat, 03 Jan 2015 02:30:55 +0100 > From: Sebastian Urbach <sebastian(a)urbach.org> > To: <tor-relays(a)lists.torproject.org> > Subject: Re: [tor-relays] Help - My relay consensus has been stripped > back to 20 > Message-ID: > <14aad6973e8.27ae.e04ee758f2dadc1889b5b423dda555f9(a)urbach.org> > Content-Type: text/plain; charset="UTF-8"; format=flowed > > On January 3, 2015 2:03:33 AM bigbudtor(a)Safe-mail.net wrote: > > Hi, > > > As i recall there was a mail from Giovanny a few days ago and he reported > his relay being down. But he had log file entries like: > > [warn] http status 400 ("Authdir is rejecting routers in this range.") > response from dirserver '128.31.0.39:9131'. > > Any of those in your log ? > No I don't see anything resembling that, although I am seeing these events messages in the logs every couple of hours: Dec 30 07:52:28.000 [info] router_pick_dirserver_generic(): No dirservers are reachable. Trying them all again. Dec 30 09:55:29.000 [info] router_pick_dirserver_generic(): No dirservers are reachable. Trying them all again. Dec 30 11:52:24.000 [info] router_pick_dirserver_generic(): No dirservers are reachable. Trying them all again. Dec 30 13:53:23.000 [info] router_pick_dirserver_generic(): No dirservers are reachable. Trying them all again. Dec 30 15:52:20.000 [info] router_pick_dirserver_generic(): No dirservers are reachable. Trying them all again. Dec 30 16:06:34.000 [info] router_upload_dir_desc_to_dirservers(): Uploading relay descriptor to directory authorities Dec 30 16:06:34.000 [info] directory_post_to_dirservers(): Uploading an extrainfo too (length 3891) Dec 30 16:06:34.000 [info] directory_post_to_dirservers(): Uploading an extrainfo too (length 3891) Dec 30 16:06:34.000 [info] directory_post_to_dirservers(): Uploading an extrainfo too (length 3891) Dec 30 16:06:34.000 [info] directory_post_to_dirservers(): Uploading an extrainfo too (length 3891) Dec 30 16:06:34.000 [info] directory_post_to_dirservers(): Uploading an extrainfo too (length 3891) Dec 30 16:06:34.000 [info] directory_post_to_dirservers(): Uploading an extrainfo too (length 3891) Dec 30 16:06:34.000 [info] directory_post_to_dirservers(): Uploading an extrainfo too (length 3891) Dec 30 16:06:34.000 [info] directory_post_to_dirservers(): Uploading an extrainfo too (length 3891) Dec 30 16:06:34.000 [info] directory_post_to_dirservers(): Uploading an extrainfo too (length 3891) Dec 30 17:52:19.000 [info] router_pick_dirserver_generic(): No dirservers are reachable. Trying them all again. Dec 30 19:53:18.000 [info] router_pick_dirserver_generic(): No dirservers are reachable. Trying them all again. Dec 30 21:39:02.000 [info] router_pick_dirserver_generic(): No dirservers are reachable. Trying them all again. Dec 30 23:33:58.000 [info] router_pick_dirserver_generic(): No dirservers are reachable. Trying them all again. Dec 31 01:32:55.000 [info] router_pick_dirserver_generic(): No dirservers are reachable. Trying them all again. Dec 31 02:52:13.000 [info] router_pick_dirserver_generic(): No dirservers are reachable. Trying them all again. Dec 31 05:05:32.000 [info] router_pick_dirserver_generic(): No dirservers are reachable. Trying them all again. I don't appear to have any routing issues, resolution issues or similar but don't have logs old enough to see if this is an unusual log event or not, it may be completely unrelated. As it stands I am afraid that there doesn't seem to be any real alternative other than decommissioning this exit relay. It is costing money and doing nobody any good right now.

2 2