[or-cvs] r19771: {torflow} Update README to include total data requirements and also to (torflow/trunk/NetworkScanners/BwAuthority)

mikeperry at seul.org mikeperry at seul.org
Mon Jun 22 00:17:08 UTC 2009


Author: mikeperry
Date: 2009-06-21 20:17:07 -0400 (Sun, 21 Jun 2009)
New Revision: 19771

Modified:
   torflow/trunk/NetworkScanners/BwAuthority/README.BwAuthorities
Log:

Update README to include total data requirements and also to
include a snippet on setting up the HTTPS scan file server.



Modified: torflow/trunk/NetworkScanners/BwAuthority/README.BwAuthorities
===================================================================
--- torflow/trunk/NetworkScanners/BwAuthority/README.BwAuthorities	2009-06-21 18:53:31 UTC (rev 19770)
+++ torflow/trunk/NetworkScanners/BwAuthority/README.BwAuthorities	2009-06-22 00:17:07 UTC (rev 19771)
@@ -26,6 +26,7 @@
 continuously, but it should be available on demand, as some of the
 faster nodes actually do have this much slack capacity.
 
+The machine will require around 4-5Gbytes/day.
 
 
 2. Get a checkout of Tor with the new network status control fixes:
@@ -103,6 +104,9 @@
 not possible, you can configure your scanner to sleep during a different
 time by editing the bwauthority.cfg files in ./data/scanner.*.
 
+For more fine grained tuning, note that the scanner using ./data/scanner.1
+will require the most bandwidth, and ./data/scanner.4 will require the 
+least.
 
 
 8. PROFIT!
@@ -110,3 +114,25 @@
 That's all there is to it. No '????' step needed!
 
 
+
+Appendix A: Creating the HTTPS scanning server
+
+The scanner server will need approx 30-40Mbit of upstream available, and will
+need to serve https via a fixed IP. SSL is needed to avoid HTTP content
+caches at the various exit nodes. Self-signed certs are OK.
+
+The server will consume around 12-15Gbytes/day.
+
+Here are two shell script snippets to generate the files we will need 
+for scanning and testing:
+
+for i in 64 32 16 8 4 2 1; do
+  dd if=/dev/urandom of=./${i}M bs=1k count=`expr $i \* 1024`
+done
+
+for i in 512 256 128 64 32 16; do
+  dd if=/dev/urandom of=./${i}k bs=1k count=$i
+done
+
+
+



More information about the tor-commits mailing list