Opened 5 years ago

Closed 3 years ago

Last modified 3 years ago

#11053 closed defect (user disappeared)

Bandwidth not used by Tor on very fast connections

Reported by: mcwerewolf Owned by:
Priority: Very High Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.4.20
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I've installed a tor relay on a KVM system (windows server 2012) that has a very fast connection to the internet (1Gbps), and despite me setting royal bandwidth limits for the relay to use, it advertises as 20 kb/s (the minimum) and is therefore not using any of the available bandwidth.

I assume it's caused by the bandwidth self-check not getting sane results.

A note on the setup: Although the KVM has a virtual NIC by name (as an Intel Pro/1000 MT), the NIC itself never returns any throughput data; the overall network measurement (network layer measurement) in resource monitor works fine, however. I gather this is a KVM oddity, but there's no way to bypass this self-check in tor either in case of problems. I assume it would set to 20KB/s if it gets "0" as a result.

Child Tickets

Change History (4)

comment:1 in reply to:  description Changed 5 years ago by cypherpunks

Replying to mcwerewolf:

I've installed a tor relay on a KVM system (windows server 2012) that has a very fast connection to the internet (1Gbps), and despite me setting royal bandwidth limits for the relay to use, it advertises as 20 kb/s (the minimum) and is therefore not using any of the available bandwidth.

I assume it's caused by the bandwidth self-check not getting sane results.

A note on the setup: Although the KVM has a virtual NIC by name (as an Intel Pro/1000 MT), the NIC itself never returns any throughput data; the overall network measurement (network layer measurement) in resource monitor works fine, however. I gather this is a KVM oddity, but there's no way to bypass this self-check in tor either in case of problems. I assume it would set to 20KB/s if it gets "0" as a result.

Please post your torrc, especially (but not limited to) the RelayBandwidthRate and RelayBandwidthBurst lines.
After this, read this blog post https://blog.torproject.org/blog/lifecycle-of-a-new-relay.

comment:2 Changed 5 years ago by nickm

Milestone: Tor: unspecified

comment:3 Changed 3 years ago by ohheyalan@…

Resolution: user disappeared
Severity: Normal
Status: newclosed

Is it appropriate to close tickets like this with the resolution as "user Disappeared"?

comment:4 Changed 3 years ago by nickm

Mostly, yes. Also it's a good idea to post a rationale when doing so, unless it's obvious.

Note: See TracTickets for help on using tickets.