From f9ea242acabcaec0ab0fbd0de5e9999dfcdb0193 Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Thu, 30 Sep 2010 18:25:25 -0400 Subject: Implement node-based router family code Also, make the NodeFamily option into a list of routersets. This lets us git rid of router_in_nickname_list (or whatever it was called) without porting it to work with nodes, and also lets people specify country codes and IP ranges in NodeFamily --- doc/tor.1.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'doc/tor.1.txt') diff --git a/doc/tor.1.txt b/doc/tor.1.txt index 42eed6e3dd..90a52fe1ef 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -571,7 +571,8 @@ The following options are useful only for clients (that is, if constitute a "family" of similar or co-administered servers, so never use any two of them in the same circuit. Defining a NodeFamily is only needed when a server doesn't list the family itself (with MyFamily). This option - can be used multiple times. + can be used multiple times. In addition to nodes, you can also list + IP address and ranges and country codes in {curly braces}. **EnforceDistinctSubnets** **0**|**1**:: If 1, Tor will not put two servers whose IP addresses are "too close" on -- cgit v1.2.3-54-g00ecf