![]() More work before we can enable it by default. The congestion control feature, detailed in proposal 324, still needs To the middle position for various network health reasons. The MiddleOnly flag (prop335) voted by the authorities to pin relays ![]() This second alpha release of the 0.4.7.x series adds two majorįeatures: congestion control (prop324) for network performance, and If you haven’t migrated just yet from v2 to v3, please see this blog post: This is the last step in the long deprecation process of onion service version 2. Version 2 onion service are now disabled at the client, service and relay level meaning that any tor nodes running this version and onward won’t support version 2 as in won’t establish connections, publish a service or relay cells. It is desirable to put the said relays in a less powerful position until an assessment can be made. not all relays in MyFamily), or needs validation that requires contacting the relay operator. The primary use case for this new flag is for the Tor network health team that often deals with a large number of relays with an incorrect configuration (e.g. And the BadExit flag is also set in this process. The new MiddleOnly flag, detailed in proposal 335, is used to pin relays in the middle position that is they can’t become HSDir, Exit, Guard or V2Dir. And so, at this release, it can not be used without a custom patch. It is currently in its testing and tuning phase which means that you should expect more 0.4.7.x alphas as congestion control stabilizes and gets tuned for optimal performance. ![]() At this stage, it still needs more work before we can enabled it by default. Alpha Congestion ControlĬongestion control, detailed in proposal 324, aim at improving Tor network performance, throughput and bandwidth utilization. Below are the major changes of the released versions and links to more detailed release notes. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |