stdout should be clean for control messages.

Make it port-purpose-agnostic; that is it should treat each port as
equal, and not expect to get a DirPort and an ORPort.

in-progress due to various bugs i uncovered in the ipv6 config option
meanings.

In case the struct grows in the future. Shouldn't be too expensive.

Linus Nordberg authored 12 years ago and Nick Mathewson committed 12 years ago

Can it ever help? I can only see harm. What am I missing?

Linus Nordberg authored 12 years ago and Nick Mathewson committed 12 years ago

Also, make node_get_prim_orport() indicate in its return value whether
a valid OR port was copied or not.

Maybe we should make it legal to pass ap_out==NULL?

Linus Nordberg authored 12 years ago and Nick Mathewson committed 12 years ago

Also, do this only for clients, explicitly.

Also, give the flag a value every time we set consensus. We used to
touch it only when ClientPreferIPv6ORPort was set, which was wrong.

Linus Nordberg authored 12 years ago and Nick Mathewson committed 12 years ago

extend_info_from_node() used to use the primary OR port (i.e. IPv4)
unless the node had routerinfo. Now that we have IPv6 addresses in
microdescs we may want to use them.

Note that this patch changes using r->cache_info.identity_digest into
using node->identity. I count on these being well synchronised, or
things would break in other ways. Right?

Linus Nordberg authored 12 years ago and Nick Mathewson committed 12 years ago

Add ClientUseIPv6 and ClientPreferIPv6ORPort configuration options.

Use "preferred OR port" for all entry nodes, not only for bridges.

Mark bridges with "prefer IPv6 OR port" if an IPv6 address is
configured in Bridge line and ClientPreferIPv6ORPort is set.

Mark relays with "prefer IPv6 OR port" if an IPv6 address is found in
descriptor and ClientPreferIPv6ORPort is set.

Filter "preferred OR port" through the ClientUseIPv6 config option. We
might want to move this test to where actual connection is being set
up once we have a fall back mechanism in place.

Have only non-servers pick an IPv6 address for the first hop: We
don't want relays to connect over IPv6 yet. (IPv6 has never been used
for second or third hops.)

Implements ticket 5535.

Linus Nordberg authored 12 years ago and Nick Mathewson committed 12 years ago

I'm not entirely sure that this is meningful but I'm pretty sure it's
not harmful. Seems like the logical thing to do.

Linus Nordberg authored 12 years ago and Nick Mathewson committed 12 years ago

Generate and store all supported microdescriptor formats. Generate
votes with one "m" line for each format. Only "m" lines with version
info matching chosen consensus method will be voted upon.

An optimisation would be to combine "m" lines with identical hashes,
i.e. instead of "m 1,2,3 H1" and "m 4,5 H1", say "m 1,2,3,4,5 H1".

Linus Nordberg authored 12 years ago and Nick Mathewson committed 12 years ago

Define new new consensus method 14 adding "a" lines to vote and
consensus documents.

From proposal 186:

  As with other data in the vote derived from the descriptor, the
  consensus will include whichever set of "a" lines are given by the
  most authorities who voted for the descriptor digest that will be
  used for the router.

This patch implements this.

This is the preferred filename to use with Autoconf 2.50 and later.

specifically, specify what sort of routers we're fetching.

Reserve it for when new directory information arrives in response to
a fetch.

Resolves ticket 6760.

Addresses bug 6759.

Allow one-hop directory fetching circuits the full "circuit build timeout"
period, rather than just half of it, before failing them and marking
the relay down. This fix should help reduce cases where clients declare
relays (or worse, bridges) unreachable because the TLS handshake takes
a few seconds to complete.

Fixes bug 6743 (one piece of bug 3443); bugfix on 0.2.2.2-alpha, where
we changed the timeout from a static 30 seconds.