[tor-relays] Question about Bridges Bandwidth Authority

[s7r]

Hello,

I'd like to know more details about how exactly the bridge bandwidth
authority works, and if we use the "weight" of each bridge for anything.

For example, I have setup 5 obfs4 bridges, with the exact very same
hardware resources and all on the same network speed of course.

One of them gets used by clients (say 20-50 unique clients every 6 hours
or so) while the rest of 4 are not used at all. This usage is not a
concern for me, as its known bridges take time until they get used,
depending on which bucket they have been assigned and etc. So I assume
it's OK at this particular point in their lifetime to be unused by any
client.

But what I am curious about is, when I search them on RelaySearch, the
used one has a measured bandwidth of over 2 MiB/s (and has the fast
flag) while other 3 unused ones have bandwidths of between 50 and 60
KiB/s (these also have the fast flag) and there is one last one which is
also not used and has a bandwidth of less than 10 KiB/s that does not
have the fast flag. (Fast flag missing is also not my problem, I am just
mentioning it as a side detail).

Now I know for sure those values are not at all in according to the real
environment. Each bridge should be at least capable of 3 MiB/s even if
all 5 are used at the same time at their full speeds. Actually I have
simulated this, it's not just theoretical.

Is there anything related to usage, so that the bridge bandwidth
authority only measures the used bridges? What could have cause such big
discrepancy in my particular case, any ideas?

Also, do we use the weight of each bridge in order to determine how much
% probability it has to be served to a request in the bucket that is
part of, or we don't use bridge weights for anything at all?

Thanks!



signature.asc
Description: OpenPGP digital signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Windows Relay Setup

[TorGate]

Its realy simple, learn linux and start with a small relay (nonexit). You can 
try a debian 10 or Ubuntu. Windoze is not a god solution. Sorry.

> Am 23.07.2019 um 22:43 schrieb Dave Warren :
> 
> One other possibility if you can't work through any issues, Windows 10 has 
> fairly decent Linux support, and/or consider running a lightweight Linux in a 
> Hyper-V VM (Windows 10 Pro, most flavours of Windows Server).
> 
> Neither of these are as clean as running natively in Windows, but when a 
> project doesn't actively maintain a particular platform it is sometimes an 
> overall better result.
> 
> 
>> On 2019-07-14 17:33, William Pate wrote:
>> Hi!
>> Well, I certainly expected far more snarky responses. :)
>> Thank you for the links. I'll check them out and, if I get it to work, maybe 
>> write up a guide for others.
>> Thank you!
>> William
>> ‐‐‐ Original Message ‐‐‐
>>> On Sunday, July 14, 2019 1:44 AM, Barton Bruce  
>>> wrote:
>>> 
>>> 
>>> William,
>>> 
 On 7/11/2019 6:58 PM, William Pate wrote:
 
 I'm interested in hosting a Windows-based relay, if anyone can point me to 
 a good tutorial. I've tried the most common ones.
 
 tor-relays mailing list
 tor-relays@lists.torproject.org
 https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>> 
>>> There used to be a VIDALIA (sp?) kit that could simply be downloaded and
>>> run on a windows machine. I then worked for an ISP/CLEC and had lots of
>>> bandwidth so ran Vidaalia on a 64 bit Windows 7 Ultimate machine on my
>>> desk at work.
>>> 
>>> I never did hear why something had changed at the tor project so that
>>> stopped working, but do remember a rude snippy condescending reply from
>>> someone on the mailing list so I lost interest.
>>> 
>>> I did get the head Tor guy from the Central Square Cambridge office of
>>> TOR to come speak at a local networking group's monthly meeting we held
>>> at a MicroSlush faclity in Burlington, MA and it was well received by a
>>> packed audience. I think he now has left TOR and works for some ISP.
>>> 
>>> 
>>> 
>>> This email has been checked for viruses by Avast antivirus software.
>>> https://www.avast.com/antivirus
>> ___
>> tor-relays mailing list
>> tor-relays@lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays