Re: [tor-relays] Local DNS on Exit logs failed user queries

On 8/16/16, teor wrote: > Or is it safer just to log a few essential categories? > (Can anyone recommend any?) Once properly set up and tested, DNS just works, only maintenance being updating root zone or keys whenever. You might be interested in aggregated stats logs it emits, memory, queries pe

[tor-relays] Local DNS on Exit logs failed user queries

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: loggin

Re: [tor-relays] [WARN] Remote server sent bogus reason code 65021

Looks like this is solved and belonged to not open ports Sorry for the hassle Paul Am 16.08.2016 um 18:34 schrieb pa011: > 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

Re: [tor-relays] A question about transfer - any advice?

Well, to spread out 1TB over a month, 1,000,000÷30 days÷24 hours÷60 minutes÷60 seconds÷2 for in/out x 8 to convert to bits equals... 1.54 Mbps, give or take. It's not exact math since a byte is 1024 instead of 1000. Either way, 1TB gets used pretty quickly. My exit transfers 1TB in just a few hour

Re: [tor-relays] Web server and TOR bridge at same IP:port

If a pluggable transport is HTTP(S)-ish, I would expect nginx to be able to use SNI or a Host header (or the lack) to decide whether to serve web content or proxy to tor or the transport. I'm not sure if nginx can decide to proxy tcp based on SNI, but it would be worth reading the docs. If this is

[tor-relays] A question about transfer - any advice?

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 cost

Re: [tor-relays] Web server and TOR bridge at same IP:port

Something like this exists: sslh[1], a "protocol demultiplexer". However, it doesn't explicitly support Tor, and I'm not sure if it's possible to distinguish between Tor packets and other TLS traffic using the options it offers[2]. [1]: http://www.rutschle.net/tech/sslh.shtml [2]: https://github.c

Re: [tor-relays] Web server and TOR bridge at same IP:port

I don't think you will be able to bind two daemons to the same TCP port (443). Maybe you could have something else listening on TCP port 443 and passing the requests onto both places? You might be able to put a single reverse proxy in front on that port, and have that proxy send the requests to t

[tor-relays] [WARN] Remote server sent bogus reason code 65021

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 tr

Re: [tor-relays] Pi3 mid relay dropping lil bit of packets

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?___ tor-relays maili

Re: [tor-relays] Pi3 mid relay dropping lil bit of packets

Ok thank you for replies, will keep an eye on this. On Tue, Aug 16, 2016 at 6:11 AM, Green Dream wrote: Counter-point... transmission errors are not a certainty:           RX packets:323526978271 errors:0 dropped:0 overruns:0 frame:0          TX packets:249565709357 err

[tor-relays] Web server and TOR bridge at same IP:port

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 si

Re: [tor-relays] spelling mistake

On Sun, 14 Aug 2016, I wrote: >https://www.torproject.org/docs/pluggable-transports.html.en > >voluntters Thanks. Committed a fix. -- | .''`. ** Debian ** Peter Palfrader | : :' : The universal https://www.palfrader.org/ | `. `'