The headline is completely inaccurate, and demonstrates the submitter didn't understand the article. Namank, please flog yourself before ever submitting again.

The headline is completely inaccurate, and demonstrates the submitter didn't understand the article. Namank, please flog yourself before ever submitting again. I used to have a crazy setup that caused network traffic of my criteria to be pulled off the wire and sent over Tor. It used iptables' MARK target and source routing to select the PPP interface. The pppd talked to a slirp (http://slirp.sourceforge.net/ http://slirp.sourceforge.net/); Slirp takes TCP packets and attempts to emulate their effect using regular UNIX socket calls. Slirp being wrapped in tsocks and Tor, resulted in the desired TCP connections actually occurring over Tor. As for DNS, that could be handled transparently using the same approach, although I never got around to this. This was all totally transparent to any machines living behind the router. While a bit contrived, this setup could easily be replicated on either a OpenWRT router, or possibly even a new style of Tor client program, which acted more like a real network interface on the user's machine. A client configuration like that wouldn't suffer from the problem described in this article.