Custom Query (24815 matches)
Results (28 - 30 of 24815)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#962 | fixed | bandwidth change makes relay publish but authorities discard | ||
Description |
Apr 01 09:45:39.145 [info] dirserv_add_descriptor(): Added descriptor from 'fluxe3' (source: 78.47.18.110): Valid server updated. Apr 01 18:52:28.976 [info] dirserv_add_descriptor(): Not replacing descriptor from 'fluxe3' (source: 78.47.18.110); differences are cosmetic. shahn> I also reloaded it at 22:52 on April 1st
shahn> RelayBandwidthRate 150 KBytes (was at 10000 or something insanely high) shahn> and RelayBandwidthBurst 200 KBytes (was at 15000)
what the relay should do is make a new descriptor, and then call router-differences-are-cosmetic on it, and revert if cosmetic. that way we're using the same function, rather than trying to keep the checks the same in both cases. [Automatically added by flyspray2trac: Operating System: All] |
|||
#965 | fixed | Redo DNS tests when exit policy changes from reject *; avoid when policy changes to reject * | ||
Description |
traffic, and still do DNS tests. Isn't that supposed to be different? <armadev> i've had a todo item for nick to not do dns tests if reject *:*. he didn't want to put it in, though. <armadev> i think that you would need to remember whether you did them, and if not launch them, if exit policy changes from reject * to something else
<armadev> fine by me. open a flyspray, due 0.2.2.x?
Laptop user in a new environment) [Automatically added by flyspray2trac: Operating System: All] |
|||
#968 | fixed | Directory authority in private Tor network doesn't publish consensus | ||
Description |
Under certain circumstances a single directory authority in a private Tor network does not manage to publish a consensus. For some reason the directory adds itself to the list of trusted directory authorities *twice*. The result is that it thinks there are 2 directories and that a single vote is not enough to publish a consensus. The directory triggers the following warning: Index: src/or/routerlist.c =================================================================== --- src/or/routerlist.c (revision 19258) +++ src/or/routerlist.c (working copy) @@ -3706,6 +3706,18 @@
+ SMARTLIST_FOREACH(trusted_dir_servers, trusted_dir_server_t *, ent, { + if (ent->v3_identity_digest && + !memcmp(v3_auth_digest, ent->v3_identity_digest, DIGEST_LEN)) + log_warn(LD_CONFIG, "We already have a directory with the same " + "v3 identity digest %s, address %s, OR port %d, and Dir port %d. " + "Now we try to add one with address %s, OR port %d, and Dir port %d. " + "Something is wrong here!", + hex_str(ent->v3_identity_digest, DIGEST_LEN), + ent->address, ent->or_port, ent->dir_port, + hostname, or_port, dir_port); + }); +
A workaround is to add a return statement to that loop. But it would be better to find out why the directory adds itself to the list twice. [Automatically added by flyspray2trac: Operating System: All] |