Tallow connects to tor network, but no website loads after pressing the big "Tor"-captioned button about torwall HOT 5 CLOSED

Tallow does not currently support Tor bridges + pluggable transports, so that is likely the problem. The reason is because Tallow attempts to intercept all "non-Tor" traffic, and it considers bridge/pluggable-transport traffic to be "non-Tor", and will attempt to block or divert it via the "real" Tor network -- which just break things.

I have some plans to fix this. It involves making the traffic that Tallow intercepts to be configurable, allowing for certain traffic types to be ignored by Tallow.

from torwall.

I have some plans to fix this. It involves making the traffic that Tallow intercepts to be configurable, allowing for certain traffic types to be ignored by Tallow.

That's just about the best Christmas present I might have ever received! Tor is the only way we can connect to the internet through, and I have actually filed this issue on behalf of a whole neighbourhood. Thank you for everything; please feel free to close this issue whenever you find fit.

from torwall.

OK I updated Tallow so that it only diverts traffic as specified by the new traffic.divert file. Thus, if you want, you can modify traffic.divert to ignore certain traffic types, such as traffic to/from a specific IP address and/or port (see the documentation in the file itself). This should allow you to configure Tallow to use Tor bridges/pluggable-transports. Although this is a low-level solution, at least it should now be possible to do, rather than not supported at all.

Note that if you want to use this you'll need to either compile Tallow yourself, or wait until the next release. I am hoping to release a new version once the new WinDivert is ready, which hopefully should be within a month or so.

from torwall.

Regarding the timeouts -- it appears that the Tor network has changed somewhat since the Tallow tool was first created. Previously, most nodes listen on port 9001, whereas now a substantial number of nodes listen on port 443, presumably because the main Tor ports are blocked in many places. But this leads also leads to Tallow blocking its own Tor traffic.

A quick fix is to update the torrc file with the following options:

FascistFirewall 1
FirewallPorts 9001,9030

After adding these options and restarting Tallow, the tool works much better. Although, this does mean that Tallow is limiting the number of Tor nodes it will connect to, which isn't ideal.

Longer term, I need to add a better way of ignoring Tor traffic other than by port number.

from torwall.

New release is available: https://github.com/basil00/TorWall/releases

from torwall.