The costs of tor-relay
About what will happen if you keep an intermediate Tor-node on your IP address and how long to "wash off" from it.
Since caring ILV began to protect us from information that was not pleasing to him, he used various means of circumventing “care”. First of all, a Tor browser, but for visiting trackers this is somewhat inconvenient - every time you need to enter a password, first of all, run it and wait until it connects, and generally unnecessary actions.
Due to the fact that the home file-torrent download on FreeBSD was always available as soon as the Internet was no longer dial-up, a solution was implemented with automatic distribution of the proxy server address via DHCP, Squid + Privoxy + Tor itself.
Tor was configured by a relay with a ban on being an Exit-node. Everything works fine.
There were some oddities:
If the problem with jd was not acute at all, then with Sberbank it was solved by juggling the session with a different address. At Rostelecom, although opt82, the new address was easily obtained by changing the poppy to poppy + 1 on the network card in ifconfig. Or the problem was solved by switching to mobile Internet.
And then I changed the provider, which gives subscribers both white and gray, and in view of the fact that white is needed, and the static costs only 50 rubles, I took it. And then the question arose with Sberbank - it again stopped working. The jerk of the technical support of the provider resulted in a new address. Sber worked and died again. Banks.ru has a review that confirmed my hunch. Sber indiscriminately blocks all addresses that appear in Tor, even if it is an intermediate node.
For the sake of laughter, I tried a dozen more banks directly from the Tor browser - everyone worked, only Sberia had paranoia. But again, mobile operators came to the rescue, although there was some inconvenience.
The letter to the mail in the otzovik remained unanswered about what kind of activity there was from my address. As well as a letter to the address Emex.
So Emex became the reason for the node being transferred to the non-public side, to check suppliers of auto parts from a mobile phone, to compare prices with competitors, and even when there are a lot of analogs from the phone, it is generally inconvenient to the extreme.
I did not want to break the scheme with transparent proxying of objectionable sites at all. Non-publicity resulted in a strong drop in traffic through it (look at mid-July):
The otzovik came back to life faster than all, did not follow jd, sber it about a month later, and emex almost a year and a half after the address disappeared from all tor lists, although it was most needed than all.
PS: hide a node from all Tor lists = become Bridge
One bit in the config: BridgeRelay 1
Since caring ILV began to protect us from information that was not pleasing to him, he used various means of circumventing “care”. First of all, a Tor browser, but for visiting trackers this is somewhat inconvenient - every time you need to enter a password, first of all, run it and wait until it connects, and generally unnecessary actions.
Due to the fact that the home file-torrent download on FreeBSD was always available as soon as the Internet was no longer dial-up, a solution was implemented with automatic distribution of the proxy server address via DHCP, Squid + Privoxy + Tor itself.
Tor was configured by a relay with a ban on being an Exit-node. Everything works fine.
There were some oddities:
- jd.ru does not open until unbound begins to make all requests not directly to the root servers and further down the chain, but, say, to 8.8.8.8. I thought something was wrong with the setting, although I sat on Google a couple of times and found nothing mine to find out what was wrong.
- Sberbank, neither the application, nor the site, and, accordingly, the Internet browser, did not work regularly. The IP address was dynamic, you never know what the client has screwed up, or the provider itself.
- Most often I couldn’t get to otzovik.ru, I complained about incorrect activity from my address.
If the problem with jd was not acute at all, then with Sberbank it was solved by juggling the session with a different address. At Rostelecom, although opt82, the new address was easily obtained by changing the poppy to poppy + 1 on the network card in ifconfig. Or the problem was solved by switching to mobile Internet.
And then I changed the provider, which gives subscribers both white and gray, and in view of the fact that white is needed, and the static costs only 50 rubles, I took it. And then the question arose with Sberbank - it again stopped working. The jerk of the technical support of the provider resulted in a new address. Sber worked and died again. Banks.ru has a review that confirmed my hunch. Sber indiscriminately blocks all addresses that appear in Tor, even if it is an intermediate node.
For the sake of laughter, I tried a dozen more banks directly from the Tor browser - everyone worked, only Sberia had paranoia. But again, mobile operators came to the rescue, although there was some inconvenience.
The letter to the mail in the otzovik remained unanswered about what kind of activity there was from my address. As well as a letter to the address Emex.
So Emex became the reason for the node being transferred to the non-public side, to check suppliers of auto parts from a mobile phone, to compare prices with competitors, and even when there are a lot of analogs from the phone, it is generally inconvenient to the extreme.
I did not want to break the scheme with transparent proxying of objectionable sites at all. Non-publicity resulted in a strong drop in traffic through it (look at mid-July):
The otzovik came back to life faster than all, did not follow jd, sber it about a month later, and emex almost a year and a half after the address disappeared from all tor lists, although it was most needed than all.
PS: hide a node from all Tor lists = become Bridge
One bit in the config: BridgeRelay 1
All Articles