Re: New Tor Relay: Help!!!!!

[slush <slush@xxxxxxxxxx>]

Hello ,

you should consider change of your DNS. Maybe it isn't problem in this
specific issue, but DNS hijacking isn't good at all.

I think there is not problem with your relay. Revvvolution appears on
torstatus.blutmagie.de without any problem so don't panic. In my case
it took many days until clients fully used my line.

Marek

On Mon, Jun 28, 2010 at 6:22 PM,  <torhelp@xxxxxxxxxxxxx> wrote:
> Hello all.
>
> I just upgraded my internet speed and have been running a Tor Relay for around two days or so.
>
> I have set up 2-3 tor relays before so I understand (I think) how to set one up.
>
> Here's the problem:
>
> In the past two days, Vidalia says I've received 200MBs of data and sent around 500MBs of data. My relay has almost NO traffic compared to the other relays I've had.
>
> I'm supposed to have upwards of 3MBS up and .73 MBs down. In Vadalia, I have the "Bandwidth Limits" set to 512 Kbps.
>
> Why is there almost no traffic? Please HELP!!!!
>
> Here's some other info:
>
> Relay Name: Revvvolution
>
> Port Forwarding: 443, 9030
>
> NOT an exit relay.
>
> Here's the log file output:
>
> Jun 25 18:06:53.078 [Notice] Tor v0.2.1.26. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 2 [workstation] {terminal services, single user})
> Jun 25 18:06:53.078 [Notice] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong.
> Jun 25 18:06:53.078 [Notice] Initialized libevent version 1.4.12-stable using method win32. Good.
> Jun 25 18:06:53.078 [Notice] Opening OR listener on 0.0.0.0:443
> Jun 25 18:06:53.187 [Notice] Opening Directory listener on 0.0.0.0:9030
> Jun 25 18:06:53.187 [Notice] Opening Socks listener on 127.0.0.1:9050
> Jun 25 18:06:53.187 [Notice] Opening Control listener on 127.0.0.1:9051
> Jun 25 18:07:20.718 [Notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
> Jun 25 18:07:27.265 [Notice] Performing bandwidth self-test...done.
> Jun 25 18:09:17.828 [Notice] Your DNS provider gave an answer for "wzoe.test", which is not supposed to exist. Apparently they are hijacking DNS failures. Trying to correct for this. We've noticed 2 possibly bad addresses so far.
> Jun 25 18:09:22.734 [Warning] eventdns: All nameservers have failed
> Jun 25 18:09:22.828 [Notice] eventdns: Nameserver 205.171.3.25 is back up
> Jun 25 18:28:32.265 [Notice] Our IP Address has changed from 174.20.99.3 to 97.116.191.145; rebuilding descriptor (source: 216.224.124.114).
> Jun 25 18:29:34.015 [Notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
> Jun 25 18:31:28.281 [Notice] Your DNS provider gave an answer for "p376epb6f37.invalid", which is not supposed to exist. Apparently they are hijacking DNS failures. Trying to correct for this. We've noticed 2 possibly bad addresses so far.
> Jun 25 18:31:32.937 [Warning] eventdns: All nameservers have failed
> Jun 25 18:31:33.046 [Notice] eventdns: Nameserver 205.171.3.25 is back up
> Jun 25 18:34:35.812 [Notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
> Jun 26 07:05:05.781 [Notice] Performing bandwidth self-test...done.
> Jun 26 12:09:23.437 [Notice] Your DNS provider has given "63.146.68.201" as an answer for 8 different invalid addresses. Apparently they are hijacking DNS failures. I'll try to correct for this by treating future occurrences of "63.146.68.201" as 'not found'.
> Jun 26 12:09:28.359 [Warning] eventdns: All nameservers have failed
> Jun 26 12:09:28.484 [Notice] eventdns: Nameserver 205.171.3.25 is back up
> Jun 26 18:31:30.734 [Notice] Performing bandwidth self-test...done.
> Jun 27 04:42:14.546 [Warning] eventdns: All nameservers have failed
> Jun 27 04:42:14.687 [Notice] eventdns: Nameserver 205.171.3.25 is back up
> Jun 27 06:38:43.296 [Notice] Performing bandwidth self-test...done.
> Jun 27 19:10:13.578 [Warning] eventdns: All nameservers have failed
> Jun 27 19:10:13.828 [Notice] eventdns: Nameserver 205.171.3.25 is back up
> Jun 27 20:48:43.406 [Notice] Your ContactInfo config option is not set. Please consider setting it, so we can contact you if your server is misconfigured or something else goes wrong.
> ***********************************************************************
> To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
> unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/
>
***********************************************************************
To unsubscribe, send an e-mail to majordomo@xxxxxxxxxxxxxx with
unsubscribe or-talk    in the body. http://archives.seul.org/or/talk/