Opened 9 years ago

Closed 9 years ago

Last modified 7 years ago

#1952 closed defect (fixed)

Bw Weights error 1 for case Case 3b

Reported by: arma Owned by: mikeperry
Priority: Medium Milestone: Tor: 0.2.2.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: tor-relay
Cc: nickm, arma Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Sep 18 07:55:01.861 [notice] Time to compute a consensus.
Sep 18 07:55:02.002 [warn] Bw Weights error 1 for case Case 3b (E scarce, Wme*E

Wmd*D). G=1361647 M=846716 E=161928 D=1625005 T=3995296

Sep 18 07:55:02.002 [warn] Bw Case 3b (E scarce, Wme*E == Wmd*D): Wme=14054! G=1
361647 M=846716 E=161928 D=1625005 T=3995296
Sep 18 07:55:02.002 [warn] Bw Case 3b (E scarce, Wme*E == Wmd*D): Wee=-4054! G=1
361647 M=846716 E=161928 D=1625005 T=3995296
Sep 18 07:55:02.002 [notice] Computed bandwidth weights for Case 3b (E scarce, W
me*E == Wmd*D): G=1361647 M=846716 E=161928 D=1625005 T=3995296
Sep 18 07:55:02.056 [warn] Bw Weight Failure for Case 3b: Etotal 1397504.300000 != Mtotal 1266100.934000. G=1361647 M=846716 E=161928 D=1625005 T=3995296. Wgg=0.978000 Wgd=0.000000 Wmg=0.022000 Wme=1.000000 Wmd=0.140000 Wee=0.000000 Wed=0.860000
Sep 18 07:55:02.078 [warn] Bw Weight Failure for Case 3b: Etotal 1397504.300000 != Gtotal 1331690.766000. G=1361647 M=846716 E=161928 D=1625005 T=3995296. Wgg=0.978000 Wgd=0.000000 Wmg=0.022000 Wme=1.000000 Wmd=0.140000 Wee=0.000000 Wed=0.860000
Sep 18 07:55:02.078 [warn] Bw Weight Failure for Case 3b: Mtotal 1266100.934000 != Gtotal 1331690.766000. G=1361647 M=846716 E=161928 D=1625005 T=3995296. Wgg=0.978000 Wgd=0.000000 Wmg=0.022000 Wme=1.000000 Wmd=0.140000 Wee=0.000000 Wed=0.860000
Sep 18 07:55:02.244 [warn] Bw Weights error 1 for case Case 3b (E scarce, Wme*E == Wmd*D). G=1361647 M=846716 E=161928 D=1625005 T=3995296
Sep 18 07:55:02.244 [warn] Bw Case 3b (E scarce, Wme*E == Wmd*D): Wme=14054! G=1361647 M=846716 E=161928 D=1625005 T=3995296
Sep 18 07:55:02.244 [warn] Bw Case 3b (E scarce, Wme*E == Wmd*D): Wee=-4054! G=1361647 M=846716 E=161928 D=1625005 T=3995296
Sep 18 07:55:02.244 [notice] Computed bandwidth weights for Case 3b (E scarce, Wme*E == Wmd*D): G=1361647 M=846716 E=161928 D=1625005 T=3995296
Sep 18 07:55:02.298 [warn] Bw Weight Failure for Case 3b: Etotal 1397504.300000 != Mtotal 1266100.934000. G=1361647 M=846716 E=161928 D=1625005 T=3995296. Wgg=0.978000 Wgd=0.000000 Wmg=0.022000 Wme=1.000000 Wmd=0.140000 Wee=0.000000 Wed=0.860000
Sep 18 07:55:02.298 [warn] Bw Weight Failure for Case 3b: Etotal 1397504.300000 != Gtotal 1331690.766000. G=1361647 M=846716 E=161928 D=1625005 T=3995296. Wgg=0.978000 Wgd=0.000000 Wmg=0.022000 Wme=1.000000 Wmd=0.140000 Wee=0.000000 Wed=0.860000
Sep 18 07:55:02.298 [warn] Bw Weight Failure for Case 3b: Mtotal 1266100.934000 != Gtotal 1331690.766000. G=1361647 M=846716 E=161928 D=1625005 T=3995296. Wgg=0.978000 Wgd=0.000000 Wmg=0.022000 Wme=1.000000 Wmd=0.140000 Wee=0.000000 Wed=0.860000
[...]
Sep 18 08:20:56.174 [warn] Weighted bandwidth is 0.000000 in node selection for rule weight as exit
Sep 18 08:21:57.322 [warn] Weighted bandwidth is 0.000000 in node selection for rule weight as exit
Sep 18 08:22:58.443 [warn] Weighted bandwidth is 0.000000 in node selection for rule weight as exit
Sep 18 08:23:59.597 [warn] Weighted bandwidth is 0.000000 in node selection for rule weight as exit
[...]
Sep 18 08:55:01.605 [notice] Time to compute a consensus.
Sep 18 08:55:01.742 [warn] Bw Weights error 1 for case Case 3b (E scarce, Wme*E == Wmd*D). G=1399808 M=853058 E=164944 D=1628516 T=4046326
Sep 18 08:55:01.743 [warn] Bw Case 3b (E scarce, Wme*E == Wmd*D): Wme=13479! G=1399808 M=853058 E=164944 D=1628516 T=4046326
Sep 18 08:55:01.743 [warn] Bw Case 3b (E scarce, Wme*E == Wmd*D): Wee=-3479! G=1399808 M=853058 E=164944 D=1628516 T=4046326
Sep 18 08:55:01.743 [notice] Computed bandwidth weights for Case 3b (E scarce, Wme*E == Wmd*D): G=1399808 M=853058 E=164944 D=1628516 T=4046326
Sep 18 08:55:01.794 [warn] Bw Weight Failure for Case 3b: Etotal 1406223.566000 != Mtotal 1291387.426000. G=1399808 M=853058 E=164944 D=1628516 T=4046326. Wgg=0.963500 Wgd=0.000000 Wmg=0.036500 Wme=1.000000 Wmd=0.136500 Wee=0.000000 Wed=0.863500
Sep 18 08:55:01.794 [warn] Bw Weight Failure for Case 3b: Etotal 1406223.566000 != Gtotal 1348715.008000. G=1399808 M=853058 E=164944 D=1628516 T=4046326. Wgg=0.963500 Wgd=0.000000 Wmg=0.036500 Wme=1.000000 Wmd=0.136500 Wee=0.000000 Wed=0.863500
Sep 18 08:55:01.794 [warn] Bw Weight Failure for Case 3b: Mtotal 1291387.426000 != Gtotal 1348715.008000. G=1399808 M=853058 E=164944 D=1628516 T=4046326. Wgg=0.963500 Wgd=0.000000 Wmg=0.036500 Wme=1.000000 Wmd=0.136500 Wee=0.000000 Wed=0.863500
Sep 18 08:55:01.959 [warn] Bw Weights error 1 for case Case 3b (E scarce, Wme*E == Wmd*D). G=1399808 M=853058 E=164944 D=1628516 T=4046326
Sep 18 08:55:01.959 [warn] Bw Case 3b (E scarce, Wme*E == Wmd*D): Wme=13479! G=1399808 M=853058 E=164944 D=1628516 T=4046326
Sep 18 08:55:01.959 [warn] Bw Case 3b (E scarce, Wme*E == Wmd*D): Wee=-3479! G=1399808 M=853058 E=164944 D=1628516 T=4046326
Sep 18 08:55:01.959 [notice] Computed bandwidth weights for Case 3b (E scarce, Wme*E == Wmd*D): G=1399808 M=853058 E=164944 D=1628516 T=4046326
Sep 18 08:55:02.011 [warn] Bw Weight Failure for Case 3b: Etotal 1406223.566000 != Mtotal 1291387.426000. G=1399808 M=853058 E=164944 D=1628516 T=4046326. Wgg=0.963500 Wgd=0.000000 Wmg=0.036500 Wme=1.000000 Wmd=0.136500 Wee=0.000000 Wed=0.863500
Sep 18 08:55:02.011 [warn] Bw Weight Failure for Case 3b: Etotal 1406223.566000 != Gtotal 1348715.008000. G=1399808 M=853058 E=164944 D=1628516 T=4046326. Wgg=0.963500 Wgd=0.000000 Wmg=0.036500 Wme=1.000000 Wmd=0.136500 Wee=0.000000 Wed=0.863500
Sep 18 08:55:02.011 [warn] Bw Weight Failure for Case 3b: Mtotal 1291387.426000 != Gtotal 1348715.008000. G=1399808 M=853058 E=164944 D=1628516 T=4046326. Wgg=0.963500 Wgd=0.000000 Wmg=0.036500 Wme=1.000000 Wmd=0.136500 Wee=0.000000 Wed=0.863500
Sep 18 08:55:02.048 [notice] Consensus computed; uploading signature(s)
Sep 18 08:55:02.049 [notice] Signature(s) posted.
Sep 18 08:55:02.052 [notice] Got a signature from 216.224.124.114. Adding it to the pending consensus.
Sep 18 08:55:02.053 [warn] Unable to store signatures posted by 216.224.124.114: Mismatched digest.
Sep 18 08:55:02.083 [notice] Got a signature from 194.109.206.212. Adding it to the pending consensus.
Sep 18 08:55:02.166 [notice] Got a signature from 86.59.21.38. Adding it to the pending consensus.
Sep 18 08:55:02.249 [notice] Got a signature from 128.31.0.39. Adding it to the pending consensus.
Sep 18 08:55:02.336 [notice] Uploaded signature(s) to dirserver 128.31.0.34:9131
Sep 18 08:55:02.344 [warn] http status 400 ("Mismatched digest.") response after uploading signatures to dirserver '216.224.124.114:9030'. Please correct.
Sep 18 08:55:02.360 [notice] Uploaded signature(s) to dirserver 80.190.246.100:8180
Sep 18 08:55:02.458 [notice] Uploaded signature(s) to dirserver 213.115.239.118:443
Sep 18 08:55:02.508 [notice] Uploaded signature(s) to dirserver 86.59.21.38:80
Sep 18 08:55:03.011 [notice] Uploaded signature(s) to dirserver 194.109.206.212:80
Sep 18 08:55:03.060 [warn] http status 400 ("Mismatched digest.") response after uploading signatures to dirserver '208.83.223.34:443'. Please correct.
Sep 18 08:55:03.115 [notice] Got a signature from 208.83.223.34. Adding it to the pending consensus.
Sep 18 08:55:03.115 [warn] Unable to store signatures posted by 208.83.223.34: Mismatched digest.
Sep 18 08:55:05.319 [notice] Got a signature from 193.23.244.244. Adding it to the pending consensus.
Sep 18 08:55:05.319 [warn] Unable to store signatures posted by 193.23.244.244: Mismatched digest.
Sep 18 08:55:05.894 [warn] http status 400 ("Mismatched digest.") response after uploading signatures to dirserver '193.23.244.244:80'. Please correct.
Sep 18 08:55:55.181 [notice] Got a signature from 80.190.246.100. Adding it to the pending consensus.
Sep 18 08:57:06.089 [warn] Weighted bandwidth is 0.000000 in node selection for rule weight as exit
Sep 18 08:57:31.117 [notice] Time to fetch any signatures that we're missing.
Sep 18 08:57:31.307 [notice] Got a signature from 208.83.223.34. Adding it to the pending consensus.
Sep 18 08:57:31.307 [warn] Problem adding detached signatures from 208.83.223.34:443: Mismatched digest.
Sep 18 08:57:31.311 [notice] Got a signature from 216.224.124.114. Adding it to the pending consensus.
Sep 18 08:57:31.312 [warn] Problem adding detached signatures from 216.224.124.114:9030: Mismatched digest.
Sep 18 08:57:31.343 [notice] Got a signature from 80.190.246.100. Adding it to the pending consensus.
Sep 18 08:57:31.363 [notice] Got a signature from 86.59.21.38. Adding it to the pending consensus.
Sep 18 08:57:31.381 [warn] Received http status code 404 ("Not found") from server '213.115.239.118:443' while fetching "/tor/status-vote/next/consensus-signatures.z".
Sep 18 08:57:31.429 [notice] Got a signature from 193.23.244.244. Adding it to the pending consensus.
Sep 18 08:57:31.429 [warn] Problem adding detached signatures from 193.23.244.244:80: Mismatched digest.
Sep 18 08:57:31.453 [notice] Got a signature from 194.109.206.212. Adding it to the pending consensus.
Sep 18 08:58:07.215 [warn] Weighted bandwidth is 0.000000 in node selection for rule weight as exit
Sep 18 08:59:06.245 [notice] Strange value for circuit build time: 552299msec. Assuming clock jump.
Sep 18 09:00:01.427 [notice] Time to publish the consensus and discard old votes
Sep 18 09:00:01.470 [warn] Consensus includes unrecognized authority 'gabelmoo-legacy' at 80.190.246.100:8180 (contact n/a; identity 81349FC1F2DBA2C2C11B45CB9706637D480AB913)
Sep 18 09:00:01.470 [warn] Consensus includes unrecognized authority 'moria1-legacy' at 128.31.0.34:9131 (contact n/a; identity E2A2AF570166665D738736D0DD58169CC61D8A8B)
Sep 18 09:00:01.470 [warn] A consensus needs 5 good signatures from recognized authorities for us to accept it. This one has 4. 6 of the authorities we know didn't sign it. It has 2 signatures from authorities we don't recognize.
Sep 18 09:00:01.470 [warn] Not enough good signatures on networkstatus consensus
Sep 18 09:00:01.470 [warn] Error publishing ns consensus
Sep 18 09:00:01.509 [warn] Consensus includes unrecognized authority 'gabelmoo-legacy' at 80.190.246.100:8180 (contact n/a; identity 81349FC1F2DBA2C2C11B45CB9706637D480AB913)
Sep 18 09:00:01.509 [warn] Consensus includes unrecognized authority 'moria1-legacy' at 128.31.0.34:9131 (contact n/a; identity E2A2AF570166665D738736D0DD58169CC61D8A8B)
Sep 18 09:00:01.509 [warn] A consensus needs 5 good signatures from recognized authorities for us to accept it. This one has 4. 6 of the authorities we know didn't sign it. It has 2 signatures from authorities we don't recognize.
Sep 18 09:00:01.509 [warn] Not enough good signatures on networkstatus consensus
Sep 18 09:00:01.509 [warn] Error publishing microdesc consensus
[...]

The various failure cases keep occurring on future hours.

Child Tickets

Attachments (10)

weighttests.py (5.2 KB) - added by mikeperry 9 years ago.
Numerical solution to try to find the avg point of all the endpoints. Takes a tor dirauth server log as first argument. Incomplete solution…
weighttests-try2.py (2.4 KB) - added by mikeperry 9 years ago.
Try using mathematica to get a simplified set of equations for the plane, and use the remaining unknowns as endpoints. Works, but gives 0.5 for the two unspecified values..
Midpoint-Failures.log (22.9 KB) - added by mikeperry 9 years ago.
All points that failed for the numeric plane midmoint algorithm.. Most of these succeeded on the authority (ides).
ides-bw-all.log.bz2 (41.8 KB) - added by mikeperry 9 years ago.
All bw weight log lines from ides, with adjacent log lines+warns.
weighttests-try3.py (3.3 KB) - added by mikeperry 9 years ago.
Revisit cases and come up with new constraints. Works for all points in my log. Will output all errors to stderr (v3)
tor-bw.log.bz2 (117.0 KB) - added by linus 9 years ago.
Logs starting 2010-06-08.
weighttests-try4.py (5.8 KB) - added by mikeperry 9 years ago.
New set of constraints that allow exits to still be used as middle nodes, and are also provably complete.
weighttests-weasel.py (3.4 KB) - added by mikeperry 9 years ago.
Weasels changes to the numerical solution. Uses numpy, gets better results (possibly due to precision).
all.log.bz2 (251.1 KB) - added by mikeperry 9 years ago.
Combination log of dizum and Linus's logs. Contains dups and is not in order, but this shouldn't matter.
weighttests-try5.py (6.6 KB) - added by mikeperry 9 years ago.
Constraints used in my branch, as per arma's point in his comment.

Download all attachments as: .zip

Change History (22)

comment:1 Changed 9 years ago by arma

Mostly failure case 3b, but here's a 2b also:

Sep 18 11:55:01.924 [notice] Time to compute a consensus.
Sep 18 11:55:02.065 [notice] Computed bandwidth weights for Case 2b (E=G): G=1384464 M=927793 E=156002 D=1718346 T=4186605
Sep 18 11:55:02.122 [warn] Bw Weight Failure for Case 2b (balanced): Etotal 1629483.695000 != Mtotal 927793.000000. G=1384464 M=927793 E=156002 D=1718346 T=4186605. Wgg=1.000000 Wgd=0.142500 Wmg=0.000000 Wme=0.000000 Wmd=0.000000 Wee=1.000000 Wed=0.857500
Sep 18 11:55:02.122 [warn] Bw Weight Failure for Case 2b (balanced): Mtotal 927793.000000 != Gtotal 1629328.305000. G=1384464 M=927793 E=156002 D=1718346 T=4186605. Wgg=1.000000 Wgd=0.142500 Wmg=0.000000 Wme=0.000000 Wmd=0.000000 Wee=1.000000 Wed=0.857500
Sep 18 11:55:02.292 [notice] Computed bandwidth weights for Case 2b (E=G): G=1384464 M=927793 E=156002 D=1718346 T=4186605
Sep 18 11:55:02.347 [warn] Bw Weight Failure for Case 2b (balanced): Etotal 1629483.695000 != Mtotal 927793.000000. G=1384464 M=927793 E=156002 D=1718346 T=4186605. Wgg=1.000000 Wgd=0.142500 Wmg=0.000000 Wme=0.000000 Wmd=0.000000 Wee=1.000000 Wed=0.857500
Sep 18 11:55:02.347 [warn] Bw Weight Failure for Case 2b (balanced): Mtotal 927793.000000 != Gtotal 1629328.305000. G=1384464 M=927793 E=156002 D=1718346 T=4186605. Wgg=1.000000 Wgd=0.142500 Wmg=0.000000 Wme=0.000000 Wmd=0.000000 Wee=1.000000 Wed=0.857500

comment:2 Changed 9 years ago by arma

Note that for the 9am EDT case, we failed to make a consensus -- related to bug #1890. But I think this time we can't blame it on clock skew. Here are the logs from the voting phase:

Sep 18 08:50:01.965 [notice] Time to vote.
Sep 18 08:50:02.472 [notice] Choosing valid-after time in vote as 2010-09-18 13:
00:00: consensus_set=1, last_interval=3600
Sep 18 08:50:02.994 [notice] Vote posted.
Sep 18 08:50:03.131 [notice] Uploaded a vote to dirserver 128.31.0.34:9131
Sep 18 08:50:04.777 [notice] Uploaded a vote to dirserver 208.83.223.34:443
Sep 18 08:50:05.004 [notice] Uploaded a vote to dirserver 216.224.124.114:9030
Sep 18 08:50:05.005 [notice] Uploaded a vote to dirserver 86.59.21.38:80
Sep 18 08:50:05.466 [notice] Uploaded a vote to dirserver 194.109.206.212:80
Sep 18 08:50:07.339 [notice] Uploaded a vote to dirserver 193.23.244.244:80
Sep 18 08:50:20.763 [notice] Uploaded a vote to dirserver 80.190.246.100:8180
Sep 18 08:50:54.126 [warn] Weighted bandwidth is 0.000000 in node selection for
rule weight as exit
Sep 18 08:51:55.218 [warn] Weighted bandwidth is 0.000000 in node selection for
rule weight as exit
Sep 18 08:52:31.293 [notice] Time to fetch any votes that we're missing.
Sep 18 08:52:31.293 [notice] We're missing votes from 1 authorities. Asking every other authority for a copy.
Sep 18 08:52:31.479 [warn] Received http status code 404 ("Not found") from server '216.224.124.114:9030' while fetching "/tor/status-vote/next/49015F787433103580E3B66A1707A00E60F2D15B.z".
Sep 18 08:52:31.482 [warn] Received http status code 404 ("Not found") from server '208.83.223.34:443' while fetching "/tor/status-vote/next/49015F787433103580E3B66A1707A00E60F2D15B.z".
Sep 18 08:52:31.519 [warn] Received http status code 404 ("Not found") from server '80.190.246.100:8180' while fetching "/tor/status-vote/next/49015F787433103580E3B66A1707A00E60F2D15B.z".
Sep 18 08:52:31.549 [warn] Received http status code 404 ("Not found") from server '86.59.21.38:80' while fetching "/tor/status-vote/next/49015F787433103580E3B66A1707A00E60F2D15B.z".
Sep 18 08:52:31.651 [warn] Received http status code 404 ("Not found") from server '193.23.244.244:80' while fetching "/tor/status-vote/next/49015F787433103580E3B66A1707A00E60F2D15B.z".
Sep 18 08:52:31.991 [warn] Received http status code 404 ("Not found") from server '194.109.206.212:80' while fetching "/tor/status-vote/next/49015F787433103580E3B66A1707A00E60F2D15B.z".
Sep 18 08:52:56.360 [warn] Weighted bandwidth is 0.000000 in node selection for rule weight as exit
Sep 18 08:53:57.496 [warn] Weighted bandwidth is 0.000000 in node selection for rule weight as exit
Sep 18 08:54:58.619 [warn] Weighted bandwidth is 0.000000 in node selection for rule weight as exit
Sep 18 08:55:01.605 [notice] Time to compute a consensus.

Changed 9 years ago by mikeperry

Attachment: weighttests.py added

Numerical solution to try to find the avg point of all the endpoints. Takes a tor dirauth server log as first argument. Incomplete solution...

Changed 9 years ago by mikeperry

Attachment: weighttests-try2.py added

Try using mathematica to get a simplified set of equations for the plane, and use the remaining unknowns as endpoints. Works, but gives 0.5 for the two unspecified values..

Changed 9 years ago by mikeperry

Attachment: Midpoint-Failures.log added

All points that failed for the numeric plane midmoint algorithm.. Most of these succeeded on the authority (ides).

Changed 9 years ago by mikeperry

Attachment: ides-bw-all.log.bz2 added

All bw weight log lines from ides, with adjacent log lines+warns.

Changed 9 years ago by mikeperry

Attachment: weighttests-try3.py added

Revisit cases and come up with new constraints. Works for all points in my log. Will output all errors to stderr (v3)

Changed 9 years ago by linus

Attachment: tor-bw.log.bz2 added

Logs starting 2010-06-08.

Changed 9 years ago by mikeperry

Attachment: weighttests-try4.py added

New set of constraints that allow exits to still be used as middle nodes, and are also provably complete.

Changed 9 years ago by mikeperry

Attachment: weighttests-weasel.py added

Weasels changes to the numerical solution. Uses numpy, gets better results (possibly due to precision).

comment:3 Changed 9 years ago by mikeperry

Ok. I think I've got this bug solved. However, I have two equally valid solutions for case 3b, when Exits are scarce but Guards are plentiful.

One solution causes nodes flagged with Exit+Guard to never be used as guard nodes, but still allows both Exit and Exit+Guard nodes to be chosen as middle nodes.

The other solution causes Exit flagged nodes to never be chosen as middle nodes.

The first solution has the advantage that Exit+Guard flagged nodes will experience less socket pressure, since they won't have to deal with both incoming and outgoing connections. However, this isn't really true, because sometimes the network moves to case 2B, which would allow Exit+Guard to be guards... The number of clients should still be lower, though.

This solution also allows us to change bridge users to use Guards and Exits+Guards as their middle hop, without that hop instantly realizing that it is being connected to by a bridge. However, the second solution would still allow this, but we would have to code the bridge clients to only use Exit+Guard flagged nodes as their exits while this case 3b was in effect.

So which one do we pick, first or second?

comment:4 Changed 9 years ago by arma

I would say we should pick the situation where exit+guards can be used in the first hop. One of the main security goals of Tor is unlinkability, and the degree of unlinkability that Tor can provide is related to the number of possible entry points in the network.

In the future I hope to make Guard flags even more common, with the goal of improving this unlinkability thing. It would be a shame if you can't help out on both sides just because you're an Exit.

comment:5 Changed 9 years ago by nickm

I concur with arma.

comment:6 in reply to:  4 Changed 9 years ago by rransom

Replying to arma:

I would say we should pick the situation where exit+guards can be used in the first hop. One of the main security goals of Tor is unlinkability, and the degree of unlinkability that Tor can provide is related to the number of possible entry points in the network.

To improve unlinkability, you would need to increase the number of entry nodes that each client might use (currently fixed at 3, for good reason), not increase the total number of entry nodes in the network. The way to improve anonymity here is to reduce the number of possible entry nodes in the network, thereby increasing the number of clients per entry node (and therefore providing more cover traffic for each client's circuits).

comment:7 Changed 9 years ago by mikeperry

Status: newneeds_review

I have a patch for this in mikeperry/bug1952 that should fix this bug with a new consensus method 10, and should also cause the authorities to omit the bandwidth-weights line if it ever has incorrect weights.

I'll also write up a proof that this won't happen again (modulo precision issues) that I'll be posting to or-dev.

Changed 9 years ago by mikeperry

Attachment: all.log.bz2 added

Combination log of dizum and Linus's logs. Contains dups and is not in order, but this shouldn't matter.

comment:8 Changed 9 years ago by mikeperry

Cc: nickm arma added

Changed 9 years ago by mikeperry

Attachment: weighttests-try5.py added

Constraints used in my branch, as per arma's point in his comment.

comment:10 Changed 9 years ago by mikeperry

Resolution: fixed
Status: needs_reviewclosed

comment:11 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:12 Changed 7 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.