On Wed, 16 Feb 2011 14:22:28 -0500 Lora Roa <hechicera@xxxxxxxxx> wrote: > Same thing, but with a bridge. Can confirm ports forwarded, hybernate not > messing with it. I though it was just me or some pattern in how my bridge > was handed out. > > Getting < 1 connection a day now, bandwidth meter reports 7:1 ration of > incoming to outgoing. Which made me recheck and retest all my port forward > settings days ago when I saw it start, but I can't figure it out from my > end. Your bridge's lack of usage is probably due to the fact that the bridge authority on Tonga (which receives bridge descriptors from bridges, performs reachability testing, and then sends a list of running bridges to BridgeDB for distribution) crashed on January 31 and no one noticed until yesterday. Oops. We've fixed it now, and we will monitor it more closely in the future, so your bridge should pick up some users soon. > Restart on a reboot yesterday gave this new debug error though: > Feb 15 16:24:11.843 [Notice] Self-testing indicates your ORPort is reachable > from the outside. Excellent. Publishing server descriptor. > Feb 15 16:24:11.845 [Warning] router_orport_found_reachable(): Bug: ORPort > found reachable, but I have no routerinfo yet. Failing to inform controller > of success. > Feb 15 16:40:03.574 [Notice] Guessed our IP address as 98.26.126.162 > (source: 91.208.34.18). > > Which I just noticed. That was not in any of the restart logs before > yesterday though. That's odd. It's probably harmless though -- it looks like the bridge authority just happened to perform a reachability test on your bridge after you rebooted it using the descriptor it had published before you rebooted it, and your router didn't have a 'routerinfo' (one of the terms used for an in-memory representation of a relay or bridge descriptor) for itself because it hadn't guessed its IP address yet. Robert Ransom
Attachment:
signature.asc
Description: PGP signature