- tor-relays - lists.torproject.org

Running an exit node behind NAT?
by Isaac Grover, Aileron I.T. 24 Sep '18

24 Sep '18

Good afternoon fellow exit node operators, I'm trying to run an exit node for specific ports on a reserved IP address from a VM behind NAT. Based on old how-to's and resolving errors in syslog, this is where I've settled for the torrc after installing the instances via ansible and relayor (thanks nusenu!); however, I'm not seeing the traffic counters update much at all and the exit node isn't showing up in consensus. What needs to be changed? OutboundBindAddress (internal IP) ORPort (internal IP):9000 DirPort (internal IP):80 DirPort (external IP) NoListen DirPort (internal IP) NoAdvertise Make your day great, Isaac Grover, Senior I.T. Consultant Aileron I.T. - "Practical & Proactive I.T. Solutions" O: 715-377-0440<tel:715-425-0440>, F:715-690-1029<tel:715-690-1029>, W: www.aileronit.com<http://www.aileronit.com/> LinkedIn: https://www.linkedin.com/in/IsaacGrover/ YouTube: https://www.youtube.com/channel/UCqrwZNFKdR-guKtuQzFPObQ

3 2

Reminder: Meeting in #tor-relays
by Colin Childs 24 Sep '18

24 Sep '18

Hi everyone, This is a reminder email that we will be holding a relay operator meeting on IRC this Tuesday, September 25th @ 19:00 UTC. You can confirm your local date / time by visiting the following page, and selecting your timezone from the dropdown menu: https://www.worldtimeserver.com/convert_time_in_UTC.aspx?y=2018&mo=9&d=25&h… When: September 25th @ 19:00 UTC Where: irc.oftc.net @ #tor-relays

1 0

Willing to be FallbackDir
by Quake 23 Sep '18

23 Sep '18

Hello, I'm interested on being a FallbackDir. Relay details: Nick: Quake Fingerprint: 490FB3FAAF8837407D94CA7E1DEF025DEF0F3516 Dir address: 178.175.139.122:80 A few restarts here and there but downtimes so far have been just few minutes max. I tend to run the latest Tor unstable versions and update as fast as possible when a new version comes out. If you feel like the relay's eligible to be added as a FallbackDir then by all means, feel free to add it to the source code.

1 0

Re: [tor-relays] Help! TOR Relat dead after upgrading Ubuntu to 18.04
by Ben Riley 23 Sep '18

23 Sep '18

I'm back in business!!!! THANK YOU!! So I changed a couple of ports and also opened those on my router. Previously I only had 9030 & 9001. I've added DirPort on 9051, Socks on 9050. I've actually got 4 ports open on the router for TOR - 9001, 9030, 9050 & 9051. I set 9030 as my control port in torrc - does that port need to be open on the router? Or can I remove that port forward? I have one of the authentication methods unhashed, so I believe that protects that somewhat. netstat -tlpn returns the following: Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:9051 0.0.0.0:* LISTEN 9531/tor tcp 0 0 127.0.0.1:9030 0.0.0.0:* LISTEN 9531/tor tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 9531/tor tcp 0 0 127.0.0.1:5939 0.0.0.0:* LISTEN 1342/teamviewerd tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 747/systemd-resolve tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 6055/cupsd tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN 9531/tor tcp6 0 0 ::1:631 :::* LISTEN 6055/cupsd nyx appears to be running fine now. I can see the graph and log messages like previously. It pulled my previous Nickname, but I currently have no flags, so I'm guessing that will update later. I've got the exit policy set to reject *:* however, as I don't want to blow my ISP off. Is that about it? Can anyone think of anything else I need to check? Thank you to everyone who offered solutions! On Thu, Sep 20, 2018 at 4:19 AM Chad MILLER <chad(a)cornsilk.net> wrote: > I maintain the tor-middle-relay Snap package. It listens on system-chosen, > arbitrary ports. May be useful to you, itself, or to steal ideas from. > > $ sudo snap install tor-middle-relay > > > > > On Wed, Sep 19, 2018, 04:56 Ben Riley <blades1000(a)gmail.com> wrote: > >> First off, will outline that I am very much a newbie, but was able to get >> a relay up and running on a Ubuntu machine. It was running fine for maybe >> 12 months (MelbTorBox), with a few resets and software updates along the >> way. >> >> Just doing my bit to help the network. >> >> Anyway, after the Ubuntu upgrade, I had to re-install TOR and I believed >> I did it basically the same way. >> >> Unfortunately, that appears not to be the case. >> I've posted the error messages on the Ubuntu forum hoping to get >> assistance, but no joy: >> >> https://askubuntu.com/questions/1070469/18-04-tor-relay-error-could-not-bin… >> >> I'm now coming to the experts to see if I can resurrect relay before I >> pull the pin on the idea. >> >> I have BASIC Unix knowledge (I can type commands and that's about it). I >> think I might have a couple of copies installed in different places and I >> know I have the TOR browser installed (it works fine). >> >> When I type 'nyx' it replies with: >> Unable to connect to tor. Maybe it's running without a ControlPort? >> >> So I type 'tor' and get >> Sep 19 21:34:24.819 [notice] Tor 0.3.4.8 (git-5da0e95e4871a0a1) running >> on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.0g, Zlib 1.2.11, Liblzma >> 5.2.2, and Libzstd 1.3.3. >> Sep 19 21:34:24.819 [notice] Tor can't help you if you use it wrong! >> Learn how to be safe at >> https://www.torproject.org/download/download#warning >> Sep 19 21:34:24.819 [notice] Read configuration file "/etc/tor/torrc". >> Sep 19 21:34:24.823 [notice] Based on detected system memory, >> MaxMemInQueues is set to 2862 MB. You can override this by setting >> MaxMemInQueues by hand. >> Sep 19 21:34:24.824 [notice] Scheduler type KIST has been enabled. >> Sep 19 21:34:24.824 [notice] Opening Socks listener on 127.0.0.1:9050 >> Sep 19 21:34:24.824 [notice] Opening Control listener on 127.0.0.1:9051 >> Sep 19 21:34:24.824 [notice] Opening OR listener on 0.0.0.0:9001 >> Sep 19 21:34:24.824 [notice] Opening Directory listener on 0.0.0.0:9050 >> Sep 19 21:34:24.824 [warn] Could not bind to 0.0.0.0:9050: Address >> already in use. Is Tor already running? >> Sep 19 21:34:24.824 [notice] Closing partially-constructed Socks listener >> on 127.0.0.1:9050 >> Sep 19 21:34:24.824 [notice] Closing partially-constructed Control >> listener on 127.0.0.1:9051 >> Sep 19 21:34:24.824 [notice] Closing partially-constructed OR listener on >> 0.0.0.0:9001 >> Sep 19 21:34:24.824 [warn] Failed to parse/validate config: Failed to >> bind one of the listener ports. >> Sep 19 21:34:24.824 [err] Reading config failed--see warnings above. >> >> I 'think' my original torrc file may have somehow survived the Ubuntu >> upgrade, but I don't know how as I did a wipe and re-install of Ubuntu. >> But when I edited it, there were my contact details sitting there. >> >> Very appreciative of any help! >> >> Thanks >> Ben. >> > _______________________________________________ >> tor-relays mailing list >> tor-relays(a)lists.torproject.org >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays >> >

2 2

Relay out of consensus after node migration
by T0r-n0d3 21 Sep '18

21 Sep '18

Hi, I recently migrated my tor node to new hardware: t0rnod3 5582BBEC12380E34D7DFB8C237939A0B317B205E Copying the /var/lib/tor/keys/ folder on the process. Now my node do not handles circuits, nor it's shown in atlas and I see the following on the logs: [notice] Heartbeat: It seems like we are not in the cached consensus. Kind regards Sent with [ProtonMail](https://protonmail.com) Secure Email.

3 4

Mexico City operator meetup (October 2nd)
by Colin Childs 21 Sep '18

21 Sep '18

Hello tor-relays, At 6:30PM on October 2nd, the Tor Project will be hosting a relay operator meetup in Mexico City, at the Sheraton Maria Isabel[1][2]. Come along and meet other relay operators and hear the latest news from Tor — we’ll also have T-shirts and stickers to kit out your devices. If you don’t run a relay but would like to know more, there will be lots of people at the meetup happy to help you. I also encourage you to read the complete blog post on the Tor Meeting Open Days linked below[1]. There are multiple other events happening around the meeting that relay operators may be interested in. We would love to see you there, thank you all for being part of the relay operator community! [1]: https://blog.torproject.org/hack-us-mexico-city-hackea-con-tor-en-mexico [2]: Paseo de la Reforma 325, Cuauhtémoc, 06500 Ciudad de México, CDMX, Mexico

1 0

Tor Relay Software Warns When Current Running Version Of Tor Is No Longer Recommended, But Not When A Newer Version Is Available?
by Keifer Bly 21 Sep '18

21 Sep '18

Hello, A few days ago, I upgraded my version of tor from 0.3.3.9 to tor 0.3.4.8. I noticed, however, that tor does not tell me when a new version is available. But in the past when I was a few versions behind, it popped up with a message saying “WARNING: this version of tor is out of date or no longer recommended.” So, I am just wondering, why is it that the tor software warns when the current version is “no longer recommended” but does not warn when an update is available? Thanks.

3 6

IPv6 on DSL
by Paul 20 Sep '18

20 Sep '18

Can Tor cope with a daily changing IPv6 Address? If so, are there any additional inputs in torrc to be made as "ip addr|grep inet6|grep global" is not giving a fix value (global noprefixroute dynamic ) Thanks Paul

3 3

More IPv6 questions
by Paul 20 Sep '18

20 Sep '18

https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#Parttwo:technic… uses "ORPort [IPv6-address]:9001" - so can i use the same port number for IPv4 and IPv6? If I run more than one instance on the same machine, can i use the same IPv6 address like in the first instance - as i can do in IPv4? "ip addr|grep inet6|grep global" doesn't give an answer on every server - what to do instead please to fill the square brackets? Thanks Paul

2 1

Help! TOR Relat dead after upgrading Ubuntu to 18.04
by Ben Riley 19 Sep '18

19 Sep '18

First off, will outline that I am very much a newbie, but was able to get a relay up and running on a Ubuntu machine. It was running fine for maybe 12 months (MelbTorBox), with a few resets and software updates along the way. Just doing my bit to help the network. Anyway, after the Ubuntu upgrade, I had to re-install TOR and I believed I did it basically the same way. Unfortunately, that appears not to be the case. I've posted the error messages on the Ubuntu forum hoping to get assistance, but no joy: https://askubuntu.com/questions/1070469/18-04-tor-relay-error-could-not-bin… I'm now coming to the experts to see if I can resurrect relay before I pull the pin on the idea. I have BASIC Unix knowledge (I can type commands and that's about it). I think I might have a couple of copies installed in different places and I know I have the TOR browser installed (it works fine). When I type 'nyx' it replies with: Unable to connect to tor. Maybe it's running without a ControlPort? So I type 'tor' and get Sep 19 21:34:24.819 [notice] Tor 0.3.4.8 (git-5da0e95e4871a0a1) running on Linux with Libevent 2.1.8-stable, OpenSSL 1.1.0g, Zlib 1.2.11, Liblzma 5.2.2, and Libzstd 1.3.3. Sep 19 21:34:24.819 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://www.torproject.org/download/download#warning Sep 19 21:34:24.819 [notice] Read configuration file "/etc/tor/torrc". Sep 19 21:34:24.823 [notice] Based on detected system memory, MaxMemInQueues is set to 2862 MB. You can override this by setting MaxMemInQueues by hand. Sep 19 21:34:24.824 [notice] Scheduler type KIST has been enabled. Sep 19 21:34:24.824 [notice] Opening Socks listener on 127.0.0.1:9050 Sep 19 21:34:24.824 [notice] Opening Control listener on 127.0.0.1:9051 Sep 19 21:34:24.824 [notice] Opening OR listener on 0.0.0.0:9001 Sep 19 21:34:24.824 [notice] Opening Directory listener on 0.0.0.0:9050 Sep 19 21:34:24.824 [warn] Could not bind to 0.0.0.0:9050: Address already in use. Is Tor already running? Sep 19 21:34:24.824 [notice] Closing partially-constructed Socks listener on 127.0.0.1:9050 Sep 19 21:34:24.824 [notice] Closing partially-constructed Control listener on 127.0.0.1:9051 Sep 19 21:34:24.824 [notice] Closing partially-constructed OR listener on 0.0.0.0:9001 Sep 19 21:34:24.824 [warn] Failed to parse/validate config: Failed to bind one of the listener ports. Sep 19 21:34:24.824 [err] Reading config failed--see warnings above. I 'think' my original torrc file may have somehow survived the Ubuntu upgrade, but I don't know how as I did a wipe and re-install of Ubuntu. But when I edited it, there were my contact details sitting there. Very appreciative of any help! Thanks Ben.

4 4