[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-relays] Q: Is my bridge up?
I put up a new bridge and thought things were okay; I could see outbound, sometimes inbound connections in nyx, and seemed to have some throughput in the first nyx screen. The start up log lines seem okay:
"Jun 10 11:05:07.000 [notice] Bootstrapped 100% (done): Done
Jun 10 11:05:07.000 [notice] Now checking whether ORPort 108.52.155.127:11340 is reachable... (this may take up to 20 minutes -- look for log messages indicating success)
Jun 10 11:05:09.000 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Jun 10 11:06:09.000 [notice] Performing bandwidth self-test...done.
Jun 10 14:13:20.000 [notice] New control connection opened.
Jun 10 15:33:16.000 [notice] No circuits are opened. Relaxed timeout for circuit 133 (a General-purpose client 1-hop circuit in state doing handshakes with channel state open) to 60000ms. However, it appears the circuit has timed out anyway.
Jun 10 16:25:18.000 [notice] New control connection opened."
And the 6hr heartbeat seems to show stuff is happening"
"Jun 10 17:05:06.000 [notice] Heartbeat: Tor's uptime is 6:00 hours, with 0 circuits open. I've sent 1.91 MB and received 5.84 MB."
But when I use the bridge reach-ability test at
It fails to find my obfs4 port.
I have the two ports port-forwarded in my local router, but when I turn on ping to the router, nmap from outside sees them as filtered.
Am I sending people down a black hole? Because tor does seem to be making tor connections.
TIA,
--Torix
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays