Maybe the network of your provider is going down sometimes. So even IF the server is not restarted, it is "offline", because other nodes can't connect to you. Maybe you should run uptimerobot.com and let it ping your server every three minutes to see, if its unreachable sometimes. Atlas has usually correct stats.
-------- Original Message --------
Subject: Re: [tor-relays] New Here
Local Time: 11 August 2017 4:28 PM
UTC Time: 11 August 2017 2:28 PM
From: paul@xxxxxxxxxxxxx
To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Another odd thin is atlas will say its down for say three hours but there are up to 1900 connections thumping away from other relays. The node has been running longer but I restarted thinking something was wrong. LOL
But like I said its not a problem - I"m wait to see if the VM provider has an issue and at 5 euros per month I"ll run others in other country"s for that money. Shame its to expensive to run one here in OZ. *SIGH*
----- Original Message -----
From: "Keepyourprivacy" <keepyourprivacy@xxxxxxxxxxxxx>
To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Sent: Saturday, August 12, 2017 12:18:03 AM
Subject: Re: [tor-relays] New Here
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@xxxxxxxxxxxxx
To: tor-relays@xxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxx>
To: tor-relays@xxxxxxxxxxxxxxxxxxxx
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
<blockquote>
-------- 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@xxxxxxxxxxxxx
To: tor-relays@xxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
</blockquote>
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays