Simple relay setup


2 years ago
Hello,

I followed the instructions to setup a non exit relay on my home windows 8 machine but some of the steps in the tutorial present in torproject.org don't match the events that I encounter.

In the end, I am "connected to the tor network", the port forwarding test returns "failed to retrieve a port mapping" eventhough my router config page says is has automatically opened ports 9030 and another one for Tor through upnp.

The program has run for one night and on my 50 mb/s upload connection I now have 28 MB upload total.

I am correctly listed on this page : http://torstatus.blutmagie.de/index.php
although it says I have only 4 kB/s upload

So my question is just : given that such a limited amount of my bandwidth has been used so far, and given the "failed to retrieve a port mapping" message, do I have a configuration problem of is my relay working ?

Below is my full log.

janv. 03 22:28:30.351 [Notice] I learned some more directory information, but not enough to build a circuit: We need more descriptors: we have 3642/5036, and can only build 37% of likely paths. (We have 71% of guards bw, 73% of midpoint bw, and 71% of exit bw.)
janv. 03 22:28:30.406 [Notice] I learned some more directory information, but not enough to build a circuit: We need more descriptors: we have 3738/5036, and can only build 39% of likely paths. (We have 72% of guards bw, 74% of midpoint bw, and 74% of exit bw.)
janv. 03 22:28:30.464 [Notice] I learned some more directory information, but not enough to build a circuit: We need more descriptors: we have 3834/5036, and can only build 43% of likely paths. (We have 75% of guards bw, 76% of midpoint bw, and 74% of exit bw.)
janv. 03 22:28:30.529 [Notice] I learned some more directory information, but not enough to build a circuit: We need more descriptors: we have 3930/5036, and can only build 45% of likely paths. (We have 77% of guards bw, 78% of midpoint bw, and 76% of exit bw.)
janv. 03 22:28:30.534 [Notice] I learned some more directory information, but not enough to build a circuit: We need more descriptors: we have 3937/5036, and can only build 46% of likely paths. (We have 77% of guards bw, 78% of midpoint bw, and 76% of exit bw.)
janv. 03 22:28:30.589 [Notice] I learned some more directory information, but not enough to build a circuit: We need more descriptors: we have 4033/5036, and can only build 48% of likely paths. (We have 78% of guards bw, 79% of midpoint bw, and 76% of exit bw.)
janv. 03 22:28:30.594 [Notice] I learned some more directory information, but not enough to build a circuit: We need more descriptors: we have 4040/5036, and can only build 48% of likely paths. (We have 78% of guards bw, 79% of midpoint bw, and 76% of exit bw.)
janv. 03 22:28:30.654 [Notice] I learned some more directory information, but not enough to build a circuit: We need more descriptors: we have 4136/5036, and can only build 53% of likely paths. (We have 81% of guards bw, 81% of midpoint bw, and 80% of exit bw.)
janv. 03 22:28:30.726 [Notice] I learned some more directory information, but not enough to build a circuit: We need more descriptors: we have 4232/5036, and can only build 58% of likely paths. (We have 83% of guards bw, 83% of midpoint bw, and 84% of exit bw.)
janv. 03 22:28:30.793 [Notice] We now have enough directory information to build circuits.
janv. 03 22:28:30.793 [Notice] Bootstrapped 80%: Connecting to the Tor network.
janv. 03 22:28:30.930 [Notice] Bootstrapped 85%: Finishing handshake with first hop.
janv. 03 22:28:30.981 [Notice] Bootstrapped 90%: Establishing a Tor circuit.
janv. 03 22:28:30.990 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
janv. 03 22:28:30.990 [Notice] Bootstrapped 100%: Done.
janv. 03 22:28:30.999 [Notice] Now checking whether ORPort 81.249.104.245:443 and DirPort 81.249.104.245:9030 are reachable... (this may take up to 20 minutes -- look for log messages indicating success)
janv. 03 22:28:30.999 [Notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.
janv. 03 22:28:31.001 [Notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
janv. 03 22:29:16.400 [Notice] Performing bandwidth self-test...done.
janv. 03 22:29:57.793 [Notice] Your DNS provider gave an answer for "7wfbmf7e3mmvwz.com", which is not supposed to exist. Apparently they are hijacking DNS failures. Trying to correct for this. We've noticed 1 possibly bad address so far.
janv. 03 22:30:02.761 [Warning] eventdns: All nameservers have failed
janv. 03 22:30:02.791 [Notice] eventdns: Nameserver 208.67.222.222:53 is back up
janv. 03 22:30:02.911 [Notice] Your DNS provider has given "67.215.65.132" as an answer for 6 different invalid addresses. Apparently they are hijacking DNS failures. I'll try to correct for this by treating future occurrences of "67.215.65.132" as 'not found'.
janv. 03 22:33:08.592 [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.
janv. 03 22:33:08.592 [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.
janv. 03 22:33:08.592 [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.
janv. 03 22:35:15.788 [Notice] Your DNS provider gave an answer for "jsl2txrwjk.com", which is not supposed to exist. Apparently they are hijacking DNS failures. Trying to correct for this. We've noticed 1 possibly bad address so far.
janv. 03 22:35:20.772 [Warning] eventdns: All nameservers have failed
janv. 03 22:35:20.788 [Notice] eventdns: Nameserver 208.67.222.222:53 is back up
janv. 03 22:35:20.804 [Notice] Your DNS provider has given "67.215.65.132" as an answer for 6 different invalid addresses. Apparently they are hijacking DNS failures. I'll try to correct for this by treating future occurrences of "67.215.65.132" as 'not found'.
janv. 03 23:28:16.871 [Notice] Circuit handshake stats since last time: 0/0 TAP, 4/4 NTor.
janv. 04 00:28:14.911 [Notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
janv. 04 01:28:14.870 [Notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
janv. 04 02:28:14.232 [Notice] Circuit handshake stats since last time: 1/1 TAP, 0/0 NTor.
janv. 04 03:28:14.610 [Notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
janv. 04 04:28:13.012 [Notice] Heartbeat: Tor's uptime is 6:00 hours, with 1 circuits open. I've sent 7.21 MB and received 14.31 MB.
janv. 04 04:28:13.012 [Notice] Average packaged cell fullness: 97.735%
janv. 04 04:28:13.012 [Notice] TLS write overhead: 11%
janv. 04 04:28:14.012 [Notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
janv. 04 05:28:14.381 [Notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
janv. 04 06:28:14.790 [Notice] Circuit handshake stats since last time: 1/1 TAP, 0/0 NTor.
janv. 04 07:28:14.218 [Notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
janv. 04 08:28:14.673 [Notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
janv. 04 09:28:14.162 [Notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
janv. 04 10:28:13.646 [Notice] Heartbeat: Tor's uptime is 12:00 hours, with 1 circuits open. I've sent 21.06 MB and received 23.65 MB.
janv. 04 10:28:13.646 [Notice] Average packaged cell fullness: 98.712%
janv. 04 10:28:13.646 [Notice] TLS write overhead: 9%
janv. 04 10:28:14.646 [Notice] Circuit handshake stats since last time: 3/3 TAP, 0/0 NTor.
janv. 04 11:28:14.120 [Notice] Circuit handshake stats since last time: 0/0 TAP, 0/0 NTor.
janv. 04 12:28:14.739 [Notice] Circuit handshake stats since last time: 2/2 TAP, 0/0 NTor.

2 years ago
It seems I finally have, after a few days online, a lot of traffic coming through my relay. Perfect.

Now I have another problem : when I use utorrent, outside of the tor network, but on the same pc, a lot of trackers become unreachable when acting as a tor relay.

When I shut down Tor, the trackers become reachable again instantly.

What is the problem ? As I am an avid user of utorrent, this problem could prevent me from continuing my tor relay.

Thanks

2 years ago
Maybe limit of open sockets? Or parallel TCP connections?

2 years ago
Thanks.
Yes that's what I had in mind but I have no idea if this is a problem :
- with the router
- with the OS
nor how to check it, how to solve, and what are the cons of opening more sockets or more parallel tcp connections.
If anybody had a clue, that would be great.

Reply

You are not logged in. Login or register to reply on this thread.