Cannot avoid rogue ExitNodes
I am trying to avoid certain Nodes and ExitNodes which seem to be hijacking traffic and forcing an exit.
This really raises my suspicions.
For example, I have noticed that the node:
126.96.36.199 (resolves to selectresponse.com.9.249.66.in-addr.arpa.)
will force itself to be an exit node, despite my attempts to ban it in my configuration file. I have tried using the ExcludeExitNodes and even ExcludeNodes directives, reloading the configuration of course.
I do not understand the way that circuits are built well enough to know if this is something that the client has any control over, both at the time of building the circuit or and after the circuit is built.
I have had noticed this phenomenon with a handful of other ExitNodes as well, and it obviously opens all sorts of problems if these are bad actors.
I have verified this behavior with tor clients (stable and unstable) up to version 0.2.2.25 in both linux and windows.