Use multiple TOR connections simultaneously for redundancy and performance
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Use multiple TOR connections simultaneously for redundancy and performance
TOR is often too slow, this happens when one of the nodes chosen at a time is too slow.
Instead we could imagine using several TOR connections simultaneously and redundantly, ignoring the packets that take too long to be acknowledged so only the fastest connection takes the full load.
How can this be done?
Maybe with virtual machines acting as TOR clients and presenting a network interface each to the host so the host thinks it has 10 network interfaces and is duplicating its packets across them?
Maybe something similar to EOP Xtream, but for linux and open-source and with the connections to different network interfaces gatewayed to TOR clients?
Quote:
there is a theory that opening multiple TCP streams can increase performance in environments where latency is an issue. The advantage comes from the "reliable" nature of TCP, and the fact and senders have to wait for acknowledgement packets, and since TCP window sizes can't be too huge across real world WANs, you can get better performance if you take your TCP stream and slice it into a bunch of parallel streams.
I'm not certain you wouldn't achieve the same efficiency by bonding a pair of NICs and running multi-path.
You're looking for the shortest route between two points, let's hope re-inventing the compass is optional.
Multiple mostly useless requests for the same page in a short time from the same site, across multiple paths of a finite network (TOR)...
That could be construed as a form of DDOS attack in my book!
At best it is wasteful of the target site and TOR network resources, very selfish and inconsiderate! At worst, with multiple clients it would become an anonymized DDOS delivery network in its own right! At worst, if it became the defacto way to use TOR it would leverage the traffic levels by the number of request paths - 10X in your example! A 10X level of traffic on an already slow resource limited network... you see where that goes...
I don't think IP multi-path sends identical requests over multiple paths, it polls for a faster path than it currently routes over and when it locates one, it uses it.
So concerns about it creating accidental ddos attacks are probably misplaced.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.