Just restarted it, and that didn't happen this time. Had not seen it except after that one reboot yesterday.<br><br>Thanks on other bridge info.<br><br>- Lora<br><br><div class="gmail_quote">On Wed, Feb 16, 2011 at 3:26 PM, Robert Ransom <span dir="ltr"><<a href="mailto:rransom.8774@gmail.com">rransom.8774@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div class="im">On Wed, 16 Feb 2011 14:22:28 -0500<br>
Lora Roa <<a href="mailto:hechicera@gmail.com">hechicera@gmail.com</a>> wrote:<br>
> Restart on a reboot yesterday gave this new debug error though:<br>
> Feb 15 16:24:11.843 [Notice] Self-testing indicates your ORPort is reachable<br>
> from the outside. Excellent. Publishing server descriptor.<br>
> Feb 15 16:24:11.845 [Warning] router_orport_found_reachable(): Bug: ORPort<br>
> found reachable, but I have no routerinfo yet. Failing to inform controller<br>
> of success.<br>
> Feb 15 16:40:03.574 [Notice] Guessed our IP address as 98.26.126.162<br>
> (source: 91.208.34.18).<br>
><br>
> Which I just noticed. That was not in any of the restart logs before<br>
> yesterday though.<br>
<br>
</div>That's odd. It's probably harmless though -- it looks like the bridge<br>
authority just happened to perform a reachability test on your bridge<br>
after you rebooted it using the descriptor it had published before you<br>
rebooted it, and your router didn't have a 'routerinfo' (one of the<br>
terms used for an in-memory representation of a relay or bridge<br>
descriptor) for itself because it hadn't guessed its IP address yet.<br>
<font color="#888888"><br>
<br>
Robert Ransom<br>
</font></blockquote></div><br>