Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server

[Tor Bug Tracker & Wiki]

#33824: relay measures low / high on same network and same server
---+
 Reporter:  niftybunny |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #33775 | Points:
 Reviewer: |Sponsor:
---+

Comment (by arma):

 Ok, the consensus weight for niftyguard33 is now 4000ish. maatuska is now
 voting 17 (up from 16), and longclaw is now voting 3700 (up from 13). I
 assume after a while maatuska will get enough new opinions that it will
 also raise its weight.

 I'm tempted to suggest closing this ticket as a duplicate of #33871, as
 juga says above.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server

[Tor Bug Tracker & Wiki]

#33824: relay measures low / high on same network and same server
---+
 Reporter:  niftybunny |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #33775 | Points:
 Reviewer: |Sponsor:
---+

Comment (by juga):

 Replying to [comment:5 arma]:
 >
 > My current intuition is that sbws is somehow not giving relays higher
 weights than they currently have in the consensus -- that is, if a relay
 has a tiny number in the consensus, then with sbws it is doomed to stay
 tiny, whereas with torflow it will get a much bigger number if it performs
 well compared to its other tiny peers. This intuition is not based on
 investigating the code or the design though. :)

 This intuition is correct, see #33871

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server

[Tor Bug Tracker & Wiki]

#33824: relay measures low / high on same network and same server
---+
 Reporter:  niftybunny |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #33775 | Points:
 Reviewer: |Sponsor:
---+

Comment (by arma):

 Replying to [comment:5 arma]:
 > > | 2020-03-26 14:00:00 |186 | 185.220.101.242 |
 niftyguard33| abuse-cont...@to-surf-and-protect.net  | 0 |
 0 |   16 |
 >
 > Spot-checking this one, it looks promising too.

 For a historical snapshot, here are the current weights at this moment:

 [torflow]
 moria1: 2760
 gabelmoo: 4490
 Faravahar: 1680
 bastet: 2440

 [sbws]
 maatuska: 16
 longclaw: 13

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server

[Tor Bug Tracker & Wiki]

#33824: relay measures low / high on same network and same server
---+
 Reporter:  niftybunny |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #33775 | Points:
 Reviewer: |Sponsor:
---+

Comment (by arma):

 Replying to [ticket:33824 niftybunny]:
 >  185.220.101.245 | niftyguard36  | abuse-contact@to-surf-and-
 protect.net  | 0 |0 |   27 |

 Ok, with the new torflow instances running, it looks like this relay is
 recovering:
 https://metrics.torproject.org/rs.html#search/niftyguard36

 > | 2020-03-26 14:00:00 |186 | 185.220.101.242 | niftyguard33
 | abuse-cont...@to-surf-and-protect.net  | 0 |0 |   16
 |

 Spot-checking this one, it looks promising too.

 My current intuition is that sbws is somehow not giving relays higher
 weights than they currently have in the consensus -- that is, if a relay
 has a tiny number in the consensus, then with sbws it is doomed to stay
 tiny, whereas with torflow it will get a much bigger number if it performs
 well compared to its other tiny peers. This intuition is not based on
 investigating the code or the design though. :)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server

[Tor Bug Tracker & Wiki]

#33824: relay measures low / high on same network and same server
---+
 Reporter:  niftybunny |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #33775 | Points:
 Reviewer: |Sponsor:
---+

Comment (by juga):

 Thanks for the info.

 i'm adding mostly the same info but in csv and ordered by name, then ip,
 since i wanted to check whether some ips change ip, which would make them
 more likely to get excluded or bw not updated so often.

 Something that would be even more useful if it's easy for you, is to get
 that data directly from the bandwidth files, including info about which is
 the bwauth that publish it, the date/time it was published and all the
 bandwidth values.

 But i could also calculate it myself or might not be really needed.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server

[Tor Bug Tracker & Wiki]

#33824: relay measures low / high on same network and same server
---+
 Reporter:  niftybunny |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #33775 | Points:
 Reviewer: |Sponsor:
---+
Changes (by juga):

 * Attachment "nifty_ordered.csv" added.


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server

[Tor Bug Tracker & Wiki]

#33824: relay measures low / high on same network and same server
---+
 Reporter:  niftybunny |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #33775 | Points:
 Reviewer: |Sponsor:
---+

Comment (by arma):

 Thanks nifty! It's clear there is something weird going on with sbws, and
 I am excited for the sbws folks to investigate.

 In the shorter term, I am exploring getting a third torflow back into the
 consensus, by just duplicating moria1's weight votes:
 https://lists.torproject.org/pipermail/tor-relays/2020-April/018337.html

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server

[Tor Bug Tracker & Wiki]

#33824: relay measures low / high on same network and same server
---+
 Reporter:  niftybunny |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #33775 | Points:
 Reviewer: |Sponsor:
---+
Changes (by arma):

 * cc: arma (added)


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server

[Tor Bug Tracker & Wiki]

#33824: relay measures low / high on same network and same server
---+
 Reporter:  niftybunny |  Owner:  (none)
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Core Tor/sbws  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID:  #33775 | Points:
 Reviewer: |Sponsor:
---+
Changes (by teor):

 * parent:   => #33775


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #33824 [Core Tor/sbws]: relay measures low / high on same network and same server

[Tor Bug Tracker & Wiki]

#33824: relay measures low / high on same network and same server
+---
 Reporter:  niftybunny  |  Owner:  (none)
 Type:  defect  | Status:  new
 Priority:  Medium  |  Component:  Core Tor/sbws
  Version:  |   Severity:  Normal
 Keywords:  |  Actual Points:
Parent ID:  | Points:
 Reviewer:  |Sponsor:
+---
 Teor told me it would be helpfuI:

 "If you have a relay that measures low, and a relay that measures high,
 on the same network, that would be really helpful."

  185.220.101.199 | niftywabbit | abuse-contact@to-surf-and-
 protect.net  | 1 |1 |56000 |
  185.220.101.245 | niftyguard36  | abuse-contact@to-surf-and-
 protect.net  | 0 |0 |   27 |

 Same server, same routing, same config  ...

 Here a list I got from nusenu. There are three servers, all in the same
 datacenter, same rack, same 20 gbit connection to the same router, same
 routing, same configuration, same hardware (40 cores, 128 gb ram and 2 ssd
 per server.

 
+-++-+-++---+--+--+
 | first_seen  | family members | IP  | nickname
 | contact| guard | exit | consensus_weight
 |
 
+-++-+-++---+--+--+
 | 2016-09-22 16:00:00 |  1 | 185.220.101.3   | niftyhutia
 | abuse-cont...@to-surf-and-protect.net  | 0 |1 | 7300
 |
 | 2020-03-26 14:00:00 |186 | 185.220.101.242 | niftyguard33
 | abuse-cont...@to-surf-and-protect.net  | 0 |0 |   16
 |
 | 2020-03-26 14:00:00 |186 | 185.220.101.224 | niftyguard15
 | abuse-cont...@to-surf-and-protect.net  | 1 |1 |   61
 |
 | 2019-01-05 08:00:00 |186 | 137.74.19.201   |
 niftyflorescaverat  | ab...@to-surf-and-protect.net  | 1 |
 0 |35000 |
 | 2020-03-26 14:00:00 |186 | 185.220.101.214 | niftyguard05
 | abuse-cont...@to-surf-and-protect.net  | 0 |1 |  220
 |
 | 2020-03-26 14:00:00 |186 | 185.220.101.228 | niftyguard19
 | abuse-cont...@to-surf-and-protect.net  | 0 |1 |  150
 |
 | 2019-01-25 21:00:00 |186 | 185.220.101.133 | niftyboglemming
 | abuse-cont...@to-surf-and-protect.net  | 1 |1 |34000
 |
 | 2019-01-31 03:00:00 |186 | 185.220.101.146 | niftyhazelmouse
 | abuse-cont...@to-surf-and-protect.net  | 1 |1 |38500
 |
 | 2020-02-02 15:00:00 |186 | 185.220.101.199 | niftywabbit
 | abuse-cont...@to-surf-and-protect.net  | 1 |1 |56000
 |
 | 2016-08-23 17:00:00 |186 | 185.220.101.1   | niftyhedgehog
 | abuse-cont...@to-surf-and-protect.net  | 1 |1 |26600
 |
 | 2016-09-18 20:00:00 |186 | 185.220.101.31  | niftywoodmouse
 | abuse-cont...@to-surf-and-protect.net  | 1 |1 |43900
 |
 | 2020-03-26 20:00:00 |186 | 185.220.101.244 | niftyguard35
 | abuse-cont...@to-surf-and-protect.net  | 1 |0 |   53
 |
 | 2020-03-26 15:00:00 |186 | 185.220.101.243 | niftywabbit13
 | abuse-cont...@to-surf-and-protect.net  | 1 |1 |   75
 |
 | 2020-03-26 14:00:00 |186 | 185.220.101.245 | niftyguard36
 | abuse-cont...@to-surf-and-protect.net  | 0 |0 |   27
 |
 | 2019-01-26 02:00:00 |186 | 185.220.101.7   | niftylagurus
 | abuse-cont...@to-surf-and-protect.net  | 1 |1 |19900
 |
 | 2020-03-19 21:00:00 |186 | 185.220.101.36  | niftyexit
 | abuse-cont...@to-surf-and-protect.net  | 0 |1 |   30
 |
 | 2020-03-26 17:00:00 |186 | 185.220.101.154 | niftywabbit14
 | abuse-cont...@to-surf-and-protect.net  | 1 |1 |   26
 |
 | 2019-01-31 20:00:00 |186 | 54.38.73.16 | niftymastomys
 | abuse-cont...@to-surf-and-protect.net  | 1 |0 |63000
 |
 | 2016-07-27 13:00:00 |186 | 185.220.101.10  | niftymouse
 | abuse-cont...@to-surf-and-protect.net  | 1 |1 |16000
 |
 | 2018-01-12 21:00:00 |186 | 185.220.101.19  | niftyrabbitrat
 | abuse-cont...@to-surf-and-protect.net  | 1 |1 |58700
 |
 | 2019-06-24 14:00:00 |186 | 51.38.22.252| wabbitseason4
 | abuse-cont...@to-surf-and-protect.net  | 1 |0 |23800
 |
 | 2016-10-23 21:00:00 |186 | 185.220.101.137 |
 niftycottonmouse| abuse-cont...@to-surf-and-protect.net  | 1 |
 1 |