Tor Relay problems - v1.11.0

[Armik]

RE: Tor Relay

Hi All,

Just tested Tor Relay with the default configuration. Got the following warnings. Tor Relay worked pretty well during the early days when directory cache was not turned on:

1) OpenSSL version from headers does not match the version we're running with. If you get weird crashes, that might be why. (Compiled with 1000214f: OpenSSL 1.0.2t 10 Sep 2019; running with 1000213f: OpenSSL 1.0.2s 28 May 2019).

2) Being a directory cache (default) with less than DIRCACHE_MIN_MEM_MB MB of memory is not recommended and may consume most of the available resources, consider disabling this functionality by setting the DirCache option to 0.

3) ControlPort is open, but no authentication method has been configured. This means that any program on your computer can reconfigure your Tor. That's bad! You should upgrade your Tor controller as soon as possible.

4) /var/tor/keys is not owned by this user (tor, 52) but by root (0). Perhaps you are running Tor as the wrong user?

5) http status 400 ("Tor version is insecure or unsupported. Please upgrade!") response from dirserver '204.13.164.118:80', '128.31.0.34:9131', '131.188.40.189:80'...... Please correct.

6) Please upgrade! This version of Tor (0.3.2.10) is not recommended, according to the directory authorities. Recommended versions are: 0.2.9.15,0.2.9.16,0.2.9.17,0.3.5.8,0.3.5.9,0.4.0.5,0.4.0.6,0.4.1.2-alpha,0.4.1.3-alpha,0.4.1.4-rc,0.4.1.5,0.4.1.6,0.4.1.7,0.4.2.1-alpha,0.4.2.2-alpha,0.4.2.3-alpha,0.4.2.4-rc,0.4.2.5

7) Your system clock just jumped 224 seconds forward; assuming established circuits no longer work.

Cheers!

here is post above what is at stake

[Armik]

New in 1.12.0:

• External Plugin Root bug fixes (blocks the use of inappropriately formatted drives)
• OpenVPN updated to latest with new ciphers
• OpenVPN bug fixes (subnet routes for clients sometimes missing)
• Restrictions/Whitelist bug fixes (specifying ip ranges now works as intended)
• Webcam Plugin fixed
• Fix setting custom MAC address on WAN for some devices (typically Archers)
• Web Monitoring bug fix (no longer auto enables every sysupgrade)
• QoS bug fixes (no longer auto enables every sysupgrade)
• Fix guest networking on mvebu devices with 88W8964 chips (guest network was not routing packets)
• Fix restrictions/quotas sometimes not adhering to DST
• Fix IMQ crashes in Kernel 4.14 leading to loss of NAT/connectivity
• New DDNS providers (safedns.com, domains.google.com)
• Switch all add/edit GUI windows to modals rather than separate windows
  (much friendlier for mobile users)
• New Plugin: Gargoyle STA Manager. Allows the user to specify multiple upstream wifi networks and connect to them in a specified priority, also ensuring that signal strength is maintained at highest possible levels. This also comes with the added benefit of automatically re-enabling the AP interface in the event that the STA can't connect, so you can still connect to Gargoyle
• Timezone change: Users who were previously using "Central Time" (CST 6 w/ DST) may find that they are now set to Canada (Saskatchewan) time (CST 6 all year). The new Central Time can be selected from the menu
• OpenWrt to 18.06.2 -> 18.06.5 (Kernel 4.9.156 -> 4.9.198, 4.14.99 ->4.14.151)

A new version of firmware was released in early December 2019, but for example, tor package is not updated. For some reason, newer versions of tor are simply not compatible with firmware or are there other reasons.

[Lantis]

Right, so there is an issue with the server configuration, not client. I understand now, thanks for pointing it out in a very loud and unspecific way. Everyone keeps saying "relay". There is a relay configuration in both client and server modes, hence the ambiguity.

Yes, Tor needs an update then.
When will it happen? Sometime in the next 6 months.
Why 6 months?

In general, because there is 1 active developer, and several contributors.
There just isn't the time to keep up to date with every single package.

[Armik]

not only tor but other packages need updating

[Lantis]

Tor has been updated to 0.4.2.7 in both 1.12.x and master. Please feel free to build from there should you require the latest.

[Armik]

Tor has been updated to 0.4.2.7 in both 1.12.x and master. Please feel free to build from there should you require the latest.

Thanks.

[ysy]

Dear Lantis,

Thanks for the replies. Have had chance testing tor server again lately. Some observatoins and feedback.
1) added "--DirCache 0" to "etc/init.d/tor" which eliminated most of the disk i/o activities and RAM consumption on my 128MB router.
2) I am longing for your new releases at: http://lantisproject.com/downloads/garg ... yisail.php Must be busy lately?
3) Confirm that tor 3.2.10 does not work. "Heartbeat: Tor's uptime is 24 hours, with 0 circuits open. "
4) Gargoyle now seats behind another router. Forwarded port 9090 to Gargoyle. May I ask if there is any other port that I have to forward from the edge device? eg 9051?

Cheers

[RomanHK]

2) I am longing for your new releases at: http://lantisproject.com/downloads/garg ... yisail.php Must be busy lately?

You can try my hosting: http://gargoyle.romanhk.cz
Last source: viewtopic.php?f=14&t=12588

[ysy]

Millions of Thanks!

[Lantis]

Does this solve your questions about Tor not working? It is updated in the latest versions yes?