- tor-relays - lists.torproject.org

Notice
by emmanuel ogbokhun 07 Apr '15

07 Apr '15

Do you need a loan or investment?. Apply for your reliable loan today at 3% interest rate with EXPO 2020 special offer, kindly contact us if you have a reliable and lucrative business that requires financing. MAK Global Investment P.O. Box 471471 105B Salahuddin St Ras Al Khaimah United Arab Emirates mak.global(a)accountant.com

5 5

what I'm doing
by impex＠mail2tor.com 07 Apr '15

07 Apr '15

African business man receiving ilegale cars from europe and USA for seeling, and trading gold of Africa to Europe and USA, looking for people who can make best African fake money like (Franc CFA) doing an import-export of different product between Africa-Europe-America ask me what you want or propose me what you have for sell or trade best regard

2 1

Re: [tor-relays] strange consensus messages in log
by starlight.2015q2＠binnacle.cx 06 Apr '15

06 Apr '15

Generally openssl security fixes do not change API/ABIs. In this case I built the newer release without export ciphers, thought that seems an unlikely cause. Perhaps it was memory corruption. Relay is running on non-ECC CPU, though the system has never exhibited any problems related to memory corruption in the past. Network equipment unlikely--Intel server-grade NIC. Has been running fine since the restart so I'll have to let it go unless it comes back at a future date.

1 0

strange consensus messages in log
by starlight.2015q2＠binnacle.cx 06 Apr '15

06 Apr '15

Does anyone have any idea what this is about? Is it serious?

2 3

Re: [tor-relays] Unreachable ORPort - Potential ISP block?
by teor 06 Apr '15

06 Apr '15

> Date: Sun, 05 Apr 2015 17:27:38 -0400 > From: starlight.2015q2(a)binnacle.cx ... > > Can you connect locally with nc/netcat/ncat? > You should run 'netstat -nt' to check whether > you get ESTABLISHED since netcat won't > say anything if it's timing-out or > connected. > > As you are behind a NAT you need the > > Address > > configuration parameter in `torrc` to > tell outside systems the public IP. The Address configuration parameter is only necessary if tor can't auto-detect its own external IP. When tor downloads the directory, it uses the external IP that the authority / mirror supplies as its external IP. Does your tor instance download the directory, and correctly guess the external IP? teor teor2345 at gmail dot com pgp 0xABFED1AC https://gist.github.com/teor2345/d033b8ce0a99adbc89c5 teor at blah dot im OTR C3C57B23 349825DE 929A1DEF C3531C25 A32287ED

2 1

Unreachable ORPort - Potential ISP block?
by CJ Barlow 05 Apr '15

05 Apr '15

I'm attempting to run a Relay but I haven't been able to get it the ORPort to be confirm as reachable. I've tried lots of things but I'm hoping there is something I haven't thought of yet that can make this work! I've got a 50Mbps symmetrical connection (without data caps) that I would love to have the Tor network utilize. Hardware info: - Asus RT-N66U running DD-WRT - Raspberry Pi 2 running Raspbian - SanDisk MicroSDHC UHS-I 16GB Here are all the steps I've taken: - Formatted the MicroSDHC with Win32DiskImager. - Followed the Instructables Raspberry Pi Tor Relay configuration guide. - Port forwarded via NAT/QoS then Port Forwarding. Protocol is set to TCP, double-checked IP is what is assigned to Raspberry Pi 2 and enable box is checked. - ORPort set to 9001. Also changed ORPort to 443, did "sudo service tor reload" and changed the port in the forwarding section of my router. - Tried router DMZ for Raspberry Pi LAN IP. I would really like to get this to work, if possible. I can't run an Exit node on my connection but since my connection sits unused for most of the day it should be put to good relay use.

5 6

Re: [tor-relays] Unreachable ORPort - Potential ISP block?
by CJ Barlow 05 Apr '15

05 Apr '15

Just to update, I got it to work! :-) I added a Dynamic DNS to the router and once it was established I reloaded Tor. It immediately found the ORPort and then did the bandwidth self-test. ("Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.") I haven't seen anything else in the log, yet.

1 0

Re: [tor-relays] Unreachable ORPort - Potential ISP block?
by starlight.2015q2＠binnacle.cx 05 Apr '15

05 Apr '15

At 13:56 4/5/2015 -0600, you wrote: TSLAGrin D0BA 2462 E224 2DE9 7F6F 7837 8F58 E63B AD51 88F8 Right answer, wrong question. Your relay is not yet published so it cannot be viewed in https://atlas.torproject.org Can you connect locally with nc/netcat/ncat? You should run 'netstat -nt' to check whether you get ESTABLISHED since netcat won't say anything if it's timing-out or connected. As you are behind a NAT you need the Address configuration parameter in `torrc` to tell outside systems the public IP.

1 0

Re: [tor-relays] Unreachable ORPort - Potential ISP block?
by CJ Barlow 05 Apr '15

05 Apr '15

Sorry I fat-fingered part of it. That should read: TSLAGrin D0BA 2462 E224 2DE9 7F6F 7837 8F*58 *E63B AD51 88F8

1 0

Re: [tor-relays] Unreachable ORPort - Potential ISP block?
by CJ Barlow 05 Apr '15

05 Apr '15

My relay fingerprint is: TSLAGrin D0BA 2462 E224 2DE9 7F6F 7837 8F25 E63B AD51 88F8

1 0