<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br></div><div>On 23 Oct 2015, at 09:30, Green Dream <<a href="mailto:greendream848@gmail.com">greendream848@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">I see this from time to time as well. Here's another example:<div><br></div><div><div> Oct 17 23:02:44.000 [notice] Our IP Address has changed from 52.64.142.121 to [CORRECT IP]; rebuilding descriptor (source: 86.59.21.38).</div><div><br></div><div>52.64.142.121 appears to be an instance on Amazon's EC2. I don't run any nodes on EC2. 86.59.21.38 resolves to <a href="http://tor.noreply.org">tor.noreply.org</a>.</div></div><div><br></div><div>I'm unable to find any occurrences of this happening from Faravahar, however the issue seems to be fairly common. What's going on?</div></div></div></blockquote><br><div>We've had one suggestion so far:</div><div>That the iptables forwarding rule from Faravahar's old address might not be preserving the original source address.</div><div><br></div><div>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.</div><div><br></div><div>A third possibility is a bug in the tor authority code, which sets <span style="background-color: rgba(255, 255, 255, 0);">X-Your-IP-Address-Is to the wrong IP.</span></div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Tim</span></div></body></html>