tor-relays

tor-relays@lists.torproject.org

38 participants
4819 discussions

Fwd: Problems with isp's onestrike policy
by majacobs 19 Aug '16

19 Aug '16

>> >> Cut off three times because of worm spread alert. I ran an exit node for just a couple of weeks. First came in while i was away on holiday . Could not connect to my vpn but noticed that one of my consumer routers send a reboot message around the first day of my vacation and didn't think about it again , that is till I got home and really started to run the node . Node 0d0a was running fine and well when the net was cut of for a second time just a few days before the third and last time. I contacted support , sought advice I was told to better run a relay. >> No way! I thought! >> To cut a story short, I know run in bridged mode (obsfs4proxy) but I am looking for solutions as to how Tor can help not seeing exit-nodes coming and going because of worm spreading? >> >> >> >> the white rider >> (Het leuke van ... is

3 4

Re: [tor-relays] Tiny computers (RPi-like) for exit nodes?
by Pi3 18 Aug '16

18 Aug '16

Im running 5 Mbits mid node on Pi3. Cpu load is 25-30% on 1 core with full steady traffic - no aes-ni here. Things should improve greatly when this ticket will go live in 0.2.9.x https://trac.torproject.org/projects/tor/ticket/7572

2 1

Abuse reports for non-exits
by Johan Nilsson 18 Aug '16

18 Aug '16

Hi, a directory authority IP-address on the DFRI network was recently reported for hosting malware and abuse reports was sent out to several mail addresses. Not only to abuse(a)dfri.tld as one would hope. The reason seems to have been malware using Tor connecting to the IP while analyzed in a sandbox. With the introduction of fallback directories abuse reports may become an issue for non-exit nodes. Just a heads up. Regards, Johan https://www.dfri.se

1 0

Local DNS on Exit logs failed user queries
by teor 18 Aug '16

18 Aug '16

Hi, When I set up a Tor Exit, I set up a local resolver (BIND) as a cache. Today, I was monitoring the syslog, and I noticed that BIND logs DNS names when resolution fails. (I have since removed these entries from the logs.) One way to prevent this is to disable logging on BIND entirely: logging { category default { null; }; }; Another is to isolate the categories that log DNS names, and disable them individually: logging { // these categories log DNS names category dnssec { null; }; category edns-disabled { null; }; category lame-servers { null; }; category resolver { null; }; category security { null; }; // also ignore uncategorised log messages category unmatched { null; }; }; I've updated the Tor wiki page on BIND with this configuration: https://trac.torproject.org/projects/tor/wiki/doc/BIND Does anyone know how to work out all the BIND categories that log DNS names? (All of the documentation I found online was helping people log *every* DNS query.) Or is it safer just to log a few essential categories? (Can anyone recommend any?) Has anyone checked if the logs on other resolvers (like unbound) have the same issue? Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org

4 4

Web server and TOR bridge at same IP:port
by Alen Hiew 17 Aug '16

17 Aug '16

Hello, listers! Is it possible to configure on own physical server a https Web server (for ex., Apache) at port 443 and obfs4 or meek bridge at same static global IP address and same port 443? It's something like SNI, not for two TLS web sites with different domain names at same IP but for web site on web server and TOR bridge. If this is possible it will be good masking for bridge because on others' requests this server will reply as simple https web server. As i understand, it will be difficult for observer without keys to distinguish encrypted bridge traffic from TLS-encrypted web traffic. If this is possible, can anyone tell about configuration manual/hits for this? WBR, Alan Hiew.

5 4

[WARN] Remote server sent bogus reason code 65021
by pa011 16 Aug '16

16 Aug '16

Just established a new Exit with two instances on (Linux 3.16.0-4-amd64) ,Tor 0.2.8.6 On the second instance I get these warnings: [WARN] Remote server sent bogus reason code 65021 [21 duplicates hidden] [WARN] Remote server sent bogus reason code 65023 [95 duplicates hidden] [NOTICE] Have tried resolving or connecting to address '[scrubbed]' at 3 different places. Giving up. [40 duplicates hidden] The code65023 is ticking up by one in about 10 seconds? The default instance is free of that. Anything to worry about? Thanks Paul

1 1

A question about transfer - any advice?
by Charon 16 Aug '16

16 Aug '16

I'm running a Tor relay and everything is going great so far, but since I'm hosting on a commercial VPS, I have limited transfer (1 TB per month, overage: $0.02/GB). As such, I've set accounting to 10 GB per day so I'll at most use 620 GB in any given month and don't have to pay any overage costs. Q1: can I increase this limit without paying extra? I'm seeing that this 10 GB is hit very quickly, today within 9 hours. Q2: how can I adjust the bandwidth limit (80 Mb/s, burst 160 Mb/s) so that this 10 GB is more spread out over the day? Would it help to make this, say, 20 or 40 Mb/s? Thanks! Ps: if I haven't supplied sufficient details, please feel free to ask

2 1

Re: [tor-relays] Pi3 mid relay dropping lil bit of packets
by Pi3 16 Aug '16

16 Aug '16

Hmm I just noticed that systemd HUPs tor exactly every 24h and now I have 16 packets lost with 30gb relayed. Can this be the cause? Is there a way to log these drops without putting too much load on ram/cpu? Just to have a timestamp?

1 0

Re: [tor-relays] Pi3 mid relay dropping lil bit of packets
by Pi3 16 Aug '16

16 Aug '16

Ok thank you for replies, will keep an eye on this. On Tue, Aug 16, 2016 at 6:11 AM, Green Dream <greendream848(a)gmail.com> wrote: Counter-point... transmission errors are not a certainty: RX packets:323526978271 errors:0 dropped:0 overruns:0 frame:0 TX packets:249565709357 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:285274358053849 (285.2 TB) TX bytes:287754558279252 (287.7 TB) Ideally there should be no errors. :) 11 dropped packets isn't a big deal, but I wouldn't be quick to dismiss these errors by default. In certain cases things might be improved with driver updates, or sysctl tweaks, or a new ethernet cable, etc. _______________________________________________ tor-relays mailing list tor-relays(a)lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

1 0

spelling mistake
by I 16 Aug '16

16 Aug '16

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-relays