Custom Query (23030 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (16 - 18 of 23030)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Ticket Resolution Summary Owner Reporter
#30522 implemented Update to May GeoIP2 database karsten
Description

My geoip-2019-05-13 branch contains the updated geoip and geoip6 files with IPv4 and IPv6 ranges and is supposed to be merged into maint-0.2.9 and other branches that are still maintained.

#30521 implemented add gaba and pili to speaking@ tpa arma
Description

We need some fresh blood on the speaking@ alias, which is our internal alias to coordinate speaking requests (see #23162).

I'm going to add Gaba and Pili, on the theory that they know external people, they know internal people, they know capacities. And they are more organized than the average Tor person. :)

#30520 not a bug Onion Service (v2) hosting Tor instance reporting under high load: Failed to find node for hop #1 of our path. Discarding this circuit. s7r
Description

An onion hosting Tor instance is reporting strange stuff for the last 3 days. The server was attacked (DOS / SYN Flood last days), so maybe this could have triggered some network connection changes but the connection remained active / online. The torrc is very simple:

SocksPort 127.0.0.1:9050
ControlPort 0
HiddenServiceDir /var/lib/tor/tor_hs
HiddenServiceVersion 2
HiddenServicePort <port> 127.0.0.1:<port>

1)

May 12 11:16:08.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 362 buildtimes.
May 12 22:20:32.000 [notice] No circuits are opened. Relaxed timeout for circuit 398807 (a Hidden service: Connecting to rendezvous point 4-hop circuit in state doing handshakes with channel state open) to 106324ms. However, it appears the circuit has timed out anyway. [16 similar message(s) suppressed in last 3600 seconds]

2)

May 13 11:05:36.000 [notice] No circuits are opened. Relaxed timeout for circuit 399137 (a General-purpose client 3-hop circuit in state waiting to see how other guards perform with channel state open) to 106324ms. However, it appears the circuit has timed out anyway. [27 similar message(s) suppressed in last 3600 seconds]

3)

May 14 21:27:36.000 [warn] Failed to find node for hop #1 of our path. Discarding this circuit.
May 14 21:27:36.000 [notice] Our circuit 0 (id: 400112) died due to an invalid selected path, purpose General-purpose client. This may be a torrc configuration issue, or a bug. [8 similar message(s) suppressed in last 3600 seconds]

I wish I could reproduce the last one. Could this be a bug that occurs when our primary #1 Guard is in consensus but not reachable just for a certain machine / IP?

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Note: See TracQuery for help on using queries.