| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
This seems to be happening to me a lot on a garbage DSL line.
We may need to come up with 2 threshholds: a high short onehop
count and a lower longer count.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Avoid memmoving 0 bytes which might lead to compiler warnings.
- Don't require relays to be entry node AND bridge at the same to time to
record clients.
- Fix a memory leak when writing dirreq-stats.
- Don't say in the stats files that measurement intervals are twice as long
as they really are.
- Reduce minimum observation time for requests to 12 hours, or we might
never record usage.
- Clear exit stats correctly after writing them, or we accumulate old stats
over time.
- Reset interval start for buffer stats, too.
|
|
|
|
|
|
|
|
| |
A) We were considering a circuit had timed out in the special cases
where we close rendezvous circuits because the final rendezvous
circuit couldn't be built in time.
B) We were looking at the wrong timestamp_created when considering
a timeout.
|
|
|
|
| |
Based on irc discussion with arma.
|
|
|
|
|
| |
Mostly by storing the timeout as milliseconds and not seconds
internally.
|
| |
|
| |
|
|
|
|
|
| |
And also the number of recent circuits used to decide
when the network changes.
|
| |
|
| |
|
|
|
|
|
|
|
| |
We want it to be under our control so it doesn't mess
up initialization. This is likely the cause for
the bug the previous assert-adding commit (09a75ad) was
trying to address.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Using CircuitBuildTimeout is prone to issues with SIGHUP, etc.
Also, shuffle the circuit build times array after loading it
in so that newer measurements don't replace chunks of
similarly timed measurements.
|
| |
|
|
|
|
| |
Also switch Xm calculation to mode, not min.
|
|
|
|
|
|
|
| |
It was compiling, but causing segfaults.
Also, adjust when the timer starts for new test circs
and save state every 25 circuits.
|
|
|
|
|
| |
Also add code to keep creating circuits every minute until we
hit our minimum threshhold.
|
| |
|
| |
|
|
|
|
|
| |
The code actually isn't that bad. It's a shame she didn't finish.
Using it as the base for this feature.
|
|
|
|
|
|
| |
Tor now reads the "circwindow" parameter out of the consensus,
and uses that value for its circuit package window rather than the
default of 1000 cells. Begins the implementation of proposal 168.
|
|
|
|
| |
finishes the authority-operator interface side of proposal 167.
|
| |
|
|
|
|
|
|
|
|
| |
This code adds a new field to vote on: "params". It consists of a list of
sorted key=int pairs. The output is computed as the median of all the
integers for any key on which anybody voted.
Improved with input from Roger.
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Resolved conflict in:
src/or/or.h
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Added a sanity check in config.c and a check in directory.c
directory_initiate_command_rend() to catch any direct connection attempts
when a socks proxy is configured.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Note that unlike subversion revision numbers, it isn't meaningful to
compare these for anything but equality. We define a sort-order anyway,
in case one of these accidentally slips into a recommended-versions
list.
|
|\ \ \
| |_|/
|/| | |
|
| | | |
|
| | | |
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Resolved onflicts in:
ChangeLog
src/or/config.c
src/or/or.h
|
| | | |
|
|\| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Relays no longer publish a new server descriptor if they change
their MaxAdvertisedBandwidth config option but it doesn't end up
changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
fixes bug 1026. Patch from Sebastian.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The problem is that clients and hidden services are receiving
relay_early cells, and they tear down the circuit.
Hack #1 is for rendezvous points to rewrite relay_early cells to
relay cells. That way there are never any incoming relay_early cells.
Hack #2 is for clients and hidden services to never send a relay_early
cell on an established rendezvous circuit. That works around rendezvous
points that haven't upgraded yet.
Hack #3 is for clients and hidden services to not tear down the circuit
when they receive an inbound relay_early cell. We already refuse extend
cells at clients.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Conflicts:
ChangeLog
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This new option will allow clients to download the newest fresh consensus
much sooner than they normally would do so, even if they previously set
FetchDirInfoEarly. This includes a proper ChangeLog entry and an updated man
page.
|