That's strange. Usually you shouldn't see more traffic than advertised.

Atlas is saying: Bandwidth rate: 300 KiB/s Bandwidth burst: 500 KiB/s Observed bandwidth: 638.69 KiB/s

Strange thing is, that the observed bandwidth is higher than your the one you are advertising. Maybe someone else can say something about this.

The "spikes" can come from the measurments, but usually the aren't that big that you should see such a high spikes.

The only thing i saw is, that you are using RelayBandwidthRate instead of just BandwidthRate in your config file. Don't know if this makes any difference?

-------- Original Message -------- Subject: Re: [tor-relays] New Here Local Time: 11 August 2017 4:10 PM UTC Time: 11 August 2017 2:10 PM From: paul@coffswifi.net To: tor-relays@lists.torproject.org

nickname: coffswifi Provider 1&1

torrc:

RunAsDaemon 1 Address 82.223.27.82 Nickname coffswifi RelayBandwidthRate 300 KBytes RelayBandwidthBurst 500 KBytes ContactInfo Paul <paul AT coffswifi dot net> DirPort 9030 ExitRelay 1 I'm running the default exit policy...

---

From: "Keepyourprivacy" keepyourprivacy@protonmail.ch To: tor-relays@lists.torproject.org Sent: Saturday, August 12, 2017 12:03:20 AM Subject: Re: [tor-relays] New Here

Thanks for running an exit! Mind sharing your torrc configuration? Maybe something is wrong in there...

Which provider are you using? Tor relay nickname would be helpful too

...

-------- Original Message -------- Subject: [tor-relays] New Here Local Time: 11 August 2017 3:50 PM UTC Time: 11 August 2017 1:50 PM From: paul@coffswifi.net To: tor-relays@lists.torproject.org

Hi all,

Have been running a mirror for a couple of years and haven"t had much time to dedicate to and exit node but have finally committed to it. Found a provider that doesn"t seem to have a cap on data and it will cost me about five euros a month.

Question I have is two fold. First I find that atlas.torproject.org sometime says the node is down but its running and connected. Secondly how dose the bandwidth throttling work. I have set it to 300kbits with 500kbit burst but I can see the in/out traffic staying over 1mb for large periods of time and bursting to 7/8mb. Its not a problem just curios.

Regards,

Paul torproject.coffswifi.net _______________________________________________ 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

Was wondering too, there are currently only two exits out there from 1&1. And they are pretty straight forward when they receive abuse messages

-------- Original Message -------- Subject: Re: [tor-relays] New Here Local Time: 11 August 2017 5:14 PM UTC Time: 11 August 2017 3:14 PM From: tor-relays-ml@horus-it.de To: tor-relays@lists.torproject.org

On 11.08.2017 16:10, Paul Templeton wrote:

...

Provider 1&1

I"m guessing their "1&1 Virtual Server Cloud S" package? I found the setup fee of 9,99 EUR quite cheeky, it"s just a virtual server with a preconfigured Linux image after all. Also, I heard 1&1 does not allow Tor exits (I checked about a year ago). Have you contacted them before you set up your virtual server?

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

Duncan dguthrie@posteo.net wrote:

...

Have been running a mirror for a couple of years and haven't had much time to dedicate to and exit node but have finally committed to it. Found a provider that doesn't seem to have a cap on data and it will cost me about five euros a month.

Question I have is two fold. First I find that atlas.torproject.org sometime says the node is down but its running and connected. Secondly how dose the bandwidth throttling work. I have set it to 300kbits with 500kbit burst but I can see the in/out traffic staying over 1mb for large periods of time and bursting to 7/8mb. Its not a problem just curios.

For bandwidth throttling, the option "BandwidthRate" applies to both incoming and outgoing traffic. That is, setting BandwidthRate to 300 Kbytes will limit incoming traffic to 300 kilobytes/s and outgoing traffic to 300 kilobytes/s. It's possible that whatever is measuring the in/out traffic is combining both these values (hence the 1megabit for the 500kbit value). The option "BandwidthBurst" behaves in a similar manner.

From the sequence of postings in this thread so far, I note a couple of things. One is that the OP said he was limiting to 300 kilo*bits*/s, while his torrc (as posted) said 300 kilo*bytes*/s. I've already deleted his message, so I'm making this statement based upon a possibly faulty recollection that he wrote *Relay*Bandwidth, rather than Bandwidth, so any of his own traffic through tor (i.e., his use of tor as a client) is *not* counted or limited by his torrc. Likewise regarding RelayBandwidthBurst vs. BandwidthBurst, which could very well account for the overage observed.

The manual explains each option in the torrc reasonably fully: https://www.torproject.org/docs/tor-manual.html.en (Alternatively, the command 'man tor' should display a virtual manual on the computer.)

I'm not sure why you'd be seeing the latter burst but I suspect the reason is due to an ill-configured torrc. It's probably worth checking the options again after reading the manual and reloading the Tor service.

See possible answer above.

Scott Bennett, Comm. ASMELG, CFIAG ********************************************************************** * Internet: bennett at sdf.org *xor* bennett at freeshell.org * *--------------------------------------------------------------------* * "A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army." * * -- Gov. John Hancock, New York Journal, 28 January 1790 * **********************************************************************