On Sat, May 06, 2017 at 09:25:11AM -0700, David Fifield wrote:
> > You're right that this is a fragile situation. Maybe we should recommend
> > that if you firewall your ORPort, you also set "AssumeReachable 1"
> > in your torrc?
>
> I've just set "AssumeReachable 1"; let's see if that helps
Dear chutney users,
Do you use DNS with chutney?
(Chutney uses IP addresses by default.)
Chutney has never worked offline, because Tor Exits check DNS before
publishing their exit policy. And if DNS fails while a test is being
run, chutney fails. (See Tor bug #21900.)
We can make chutney work
On Sat, May 06, 2017 at 03:41:28AM -0400, Roger Dingledine wrote:
> On Fri, May 05, 2017 at 04:30:52PM -0700, David Fifield wrote:
> > But if it's the case that an unreachable ORPort causes descriptors not
> > to be uploaded, then why do the default obfs4 bridges appear in Atlas?
>
> Tor relays
On Fri, May 05, 2017 at 04:30:52PM -0700, David Fifield wrote:
> But if it's the case that an unreachable ORPort causes descriptors not
> to be uploaded, then why do the default obfs4 bridges appear in Atlas?
Tor relays (and bridges) test their reachability by making circuits
that loop back to
