Turns out this is a known bug in tor.
s7r reported [1] it several years ago (2014-12-13).
In [1] a log warning has been added, [2] is
about the actual fix.
[1] https://trac.torproject.org/projects/tor/ticket/13953
[2] https://trac.torproject.org/projects/tor/ticket/19919
--
https://mastodon
It seems that each function in a network app that
- listens to the net, should have an independantly
configurable inbound ip and port.
- talks out to the net, should have an independantly
configurable source ip and port.
And when there are multiple interfaces / NAT,
address metadata and metainfo a
Hi,
I got an interesting bugreport for ansible-relayor [1],
that leads me to the following question:
Is OutboundBindAddress used during ORPort IP auto detection?
Imagine the following setup:
Relay with two public IPs:
1.1.1.1
2.2.2.2
Two tor instances (one per IP):
1.1.1.1:9000
2.2.2.2:9000
> On Mar 23, 2018, at 8:21 PM, Roger Dingledine wrote:
>
> I believe there are no scanners that supply answers to multiple directory
> authorities.
>
Great! IIRC, at one point in the distant past this was not the case.
> You could in theory check whether this is true in practice by seeing if
