Routers count as down when they change ORPort, too
commit9b64227ffd38e9406c5c88ace137a0eae010771d
authorSebastian Hahn <sebastian@torproject.org>
Mon, 7 Feb 2011 15:31:20 +0000 (7 16:31 +0100)
committerSebastian Hahn <sebastian@torproject.org>
Mon, 7 Feb 2011 23:38:48 +0000 (8 00:38 +0100)
treeb533ef2a0ef94cbc9329a0261ea516dac6f9f9d3
parenta68e2043aba4d33e39a8cb47be5dc3082f27ad07
Routers count as down when they change ORPort, too

rransom noticed that a change of ORPort is just as bad as a change of IP
address from a client's perspective, because both mean that the relay is
not available to them while the new information hasn't propagated.
Change the bug1035 fix accordingly.

Also make sure we don't log a bridge's IP address (which might happen
when we are the bridge authority).
changes/bug1035
src/or/dirserv.c
src/or/rephist.c
src/or/rephist.h