[tor-relays] Faravahar messing with my IP address
teor2345 at gmail.com
Fri Oct 23 10:55:58 UTC 2015
> On 23 Oct 2015, at 09:30, Green Dream <greendream848 at gmail.com> wrote:
> I see this from time to time as well. Here's another example:
> Oct 17 23:02:44.000 [notice] Our IP Address has changed from 184.108.40.206 to [CORRECT IP]; rebuilding descriptor (source: 220.127.116.11).
> 18.104.22.168 appears to be an instance on Amazon's EC2. I don't run any nodes on EC2. 22.214.171.124 resolves to tor.noreply.org.
> I'm unable to find any occurrences of this happening from Faravahar, however the issue seems to be fairly common. What's going on?
We've had one suggestion so far:
That the iptables forwarding rule from Faravahar's old address might not be preserving the original source address.
Another possibility is that authorities running directory caching proxies are re-using the X-Your-IP-Address-Is header meant for other clients, rather than generating it fresh for every client.
A third possibility is a bug in the tor authority code, which sets X-Your-IP-Address-Is to the wrong IP.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the tor-relays