Re: [tor-relays] Problem with authorities?

2019-10-14 Thread teor
Hi,

> On 14 Oct 2019, at 22:23, tscha...@posteo.de wrote:
> 
> On 2019-10-14 11:48, teor wrote:
> 
>>> what's about the autorities maatu., tor26, bastet, gabel., and farav.?
>> 
>> They either:
>> - check IPv6 reachability, or
>> - have a high stable MTBF (mean time before failure):
>> https://consensus-health.torproject.org/#flagthresholds
> 
> Thank you for the reply. What does the 'stable MTBF' mean? Time in
> seconds (18 .. 48 days) before my relay get the stable flag back?

It's a measure of the stability of your relay. A MTBF is an average time
before your relay is next expected to fail, based on its past failures.

For more details, see:
https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n1800

> Downtime was from 2019-09-24 10:00 - 2019-09-26 06:00.
> 
>> Keep your relay up, and its IPv6 address reachable, and you should be fine.
> 
> The ReachableIPv6 flag is set and usage is ~5500 connections.

If your IPv6 address becomes unreachable, that counts as a failure. I don't
have exact data, but it does seem that the IPv6 authorities think your relay
has a lower stability.

T___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] Firewall rules as a "replacement" for MyFamily on a bridge?

2019-10-14 Thread Marco Gruß
Hi,

On Mon, Oct 14, 2019 at 01:02:04AM -0400, Roger Dingledine wrote:
> It does make sense.
> [...]
> I would say that if you're excited to do it, it won't hurt much and
> might help a bit so feel free. But if not you shouldn't. And it would
> be a shame if many people started doing it, because the two "little bit
> against" points get a little bit worse when the behavior is more common.

Thank you, Roger, for the detailed explanation.

I'll leave the ports open for everybody, including my other relays.

Best,
Marco
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] Questions about Fallbacks

2019-10-14 Thread teor

Hi,

> On 8 Oct 2019, at 17:03, Michael Gerstacker 
>  wrote:
> 
> when i setted up my relays i choosed 443 as the ORPort.
> My thought behind it was that 443 is most likely not blocked and less likely 
> observed because the ISP could expect to anyway only see encrypted data so a 
> Tor connection will more likely slip through it.
> 
> I let the DirPort on 9030 because i read that clients anyway only use the 
> ORPort and i thought if a authority will connect to me it makes no difference 
> because none of my ports is blocked.
> 
> Now some of my relays are Fallbacks.
> 
> Would it be a benefit for the network if i change the DirPort to 80 or is the 
> DirPort still not used by clients?

The DirPort is not used by clients.

> Is it necessary to opt-out the relay as a fallback if it was shut down by the 
> provider and already is long gone from metrics?

It won't make much difference.
Relay search deletes missing relays after a week or so.
We rebuild the fallback list and delete missing relays every 6-12 months.

T


___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays


Re: [tor-relays] Some newbie questions

2019-10-14 Thread teor
Hi,

> On 3 Oct 2019, at 11:41, skarz  wrote:
> 
> Also, after I make changes to the torrc file, is pressing ‘x’ in Nyx an 
> acceptable way to enable the changes or is there a preferred method?

Yes, it sends a reload signal:
https://gitweb.torproject.org/nyx.git/tree/nyx/__init__.py#n230

You can also reload tor's config using systemd or "kill -HUP".

> Last, if I’m running a bridge at home do I need to configure iptables / 
> fail2ban or is my firewall sufficient? And specifically which ports need to 
> be forwarded to my bridge? Just the ORPort or others as well?

If you are running obfs4, you also need to forward its port.

T___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays