Changes to directory request statistics:

- Rename GEOIP statistics to DIRREQ statistics, because they now include
  more than only GeoIP-based statistics, whereas other statistics are
  GeoIP-dependent, too.
- Rename output file from geoip-stats to dirreq-stats.
- Add new config option DirReqStatistics that is required to measure
  directory request statistics.
- Clean up ChangeLog.

Also ensure that entry guards statistics have access to a local GeoIP
database.

- Use common prefixes DIRREQ_* and dirreq_*.
- Replace enums in structs with bitfields.

Conflicts:
	src/or/geoip.c

it never really worked, and hasn't been used for years.

Add two functions for round_to_next_multiple_of() for uint32_t and
uint64_t.

Avoid division in every step of the loop over all ports.

Introduce a threshold of 0.01% of bytes that must be read and written per
port in order to be included in the statistics. Otherwise we cannot include
these statistics in extra-info documents, because they are too big.

Change the labels "-written" and "-read" so that the meanings are as
intended.

Conflicts:
	ChangeLog
	configure.in
	src/or/config.c
	src/or/or.h

Conflicts:
	ChangeLog
	configure.in
	contrib/tor-mingw.nsi.in
	src/win32/orconfig.h

Patch by Roger; fixes bug 1027.

Karsten Loesing authored 15 years ago and Nick Mathewson committed 15 years ago

[Original patch series from Karsten, revised and squashed by Nick]

[Didn't take Karsten's full bug 1024 workaround, since 0.2.2 doesn't
use v0 rend descs.]

Karsten Loesing authored 15 years ago and Nick Mathewson committed 15 years ago

The internal error "could not find intro key" occurs when we want to send
an INTRODUCE1 cell over a recently finished introduction circuit and think
we built the introduction circuit with a v2 hidden service descriptor, but
cannot find the introduction key in our descriptor.

My first guess how we can end up in this situation is that we are wrong in
thinking that we built the introduction circuit based on a v2 hidden
service descriptor. This patch checks if we have a v0 descriptor, too, and
uses that instead.

Roger Dingledine authored 15 years ago and Nick Mathewson committed 15 years ago

  o Minor features:
    - If we're a relay and we change our IP address, be more verbose
      about the reason that made us change. Should help track down
      further bugs for relays on dynamic IP addresses.

Roger Dingledine authored 15 years ago and Nick Mathewson committed 15 years ago

when we write out our stability info, detect relays that have slipped
through the cracks. log about them and correct the problem.

if we continue to see a lot of these over time, it means there's another
spot where relays fall out of the routerlist without being marked as
unreachable.

Roger Dingledine authored 15 years ago and Nick Mathewson committed 15 years ago

whenever we remove a relay from the main routerlist, tell the
rephist module that it's no longer running.