{"id":38174,"date":"2019-10-31T22:22:05","date_gmt":"2019-10-31T19:22:05","guid":{"rendered":"https:\/\/prohoster.info\/blog\/izderzhki-tor-relay\/"},"modified":"2019-10-31T22:22:05","modified_gmt":"2019-10-31T19:22:05","slug":"izderzhki-tor-relay","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/administrirovanie\/izderzhki-tor-relay","title":{"rendered":"Costs of tor-relay","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"

About what happens if you keep an intermediary Tor node on your IP address and how long it takes to 'clean up' from it afterward.
\n<\/a><\/noindex>
\nSince the caring Roskomnadzor began to shield us from undesirable information, various methods for bypassing this 'protection' have been used. Primarily the Tor browser, but visiting trackers is somewhat inconvenient \u2014 you always have to enter a password, first, and then launch it, waiting for it to connect, which adds extra steps. <\/p>\n

Given that a home file-sharing torrent downloader on FreeBSD has always existed, as soon as the internet stopped being dial-up, a solution was implemented with automatic proxy address distribution via DHCP, using Squid + Privoxy + Tor.server<\/a> Tor was configured as a relay with a restriction against being an Exit node. Everything works perfectly.<\/p>\n

There were some oddities:<\/p>\n

jd.ru does not open until unbound starts making all requests not directly to the root servers and down the chain, but, say, to 8.8.8.8. I thought something was wrong with the settings, although I googled a couple of times and couldn't find anything wrong. <\/p>\n