[tor-talk] How to update the consensus in client as soon as the configuration of relay nodes changed

[Aiminyoung]

Hi Karsten

I've found some new settings from Chutney torrc template,
TestingServerDownloadSchedule and TestingClientDownloadSchedule.
Then I upgrade my tor to 0.2.5.2 since the new settings are available in
0.2.5.x and gave small values to the settings, but no help.
So I went back to source code and found that in directory.c the directory
request parameter "if_modified_since" came from "valid_after" plus a
constant 180. Though I'm not sure about the reason this number written in
numeric instead of a constant definition, I removed it and now the
consensus file in client can be updated in a period of
TestingClientDownloadSchedule!
Thanks again for the guide.

Best Regards,
Aiminyoung


2014-02-20 10:48 GMT+08:00 Aiminyoung <aiminyoung at gmail.com>:

> Hi Karsten
>
> Thanks for help.
> I did have set TestingTorNetwork which also changed default values of
> V3auth* flags as described in tor manual.
> However they seems to be only about consensus on directory server.
> I will give a try to using Chutney and update results here.
>
> Best regards,
> Aiminyoung
>
>
> 2014-02-19 18:47 GMT+08:00 Karsten Loesing <karsten at torproject.org>:
>
> On 19/02/14 03:24, Aiminyoung wrote:
>>
>>> I have setup a private tor network containing one client, one dirserver,
>>> and three relay nodes.
>>> To make the changes of relay nodes take effect to client, I have to
>>> shorten
>>> the updating period of directory information on dirserver and client.
>>> V3AuthVotingInterval, V3AuthVoteDelay, and V3AuthDistDelay on dirserver
>>> were set to 60 seconds (source code about the minimum limitation were
>>> also
>>> modified),  so that the cached-consensus is updated every 1 minute.
>>> Now I have problem in accelerating the cache updating on client because I
>>> can't find the command to make it.
>>> Is there other ways to shorten the updating interval on client, such as
>>> an
>>> delay constant in source code?
>>>
>>
>> Did you look into the TestingTorNetwork config option?  It should already
>> do what you want.
>>
>> Also look at the FAQ entry for running private networks here:
>>
>> https://www.torproject.org/docs/faq.html.en#PrivateTorNetwork
>>
>> All the best,
>> Karsten
>>
>> --
>> tor-talk mailing list - tor-talk at lists.torproject.org
>> To unsubscribe or change other settings go to
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
>>
>
>