Tor is unusable [SOLVED]

Started by Tigger, October 20, 2017, 07:12:14 PM

Previous topic - Next topic
October 20, 2017, 07:12:14 PM Last Edit: October 23, 2017, 03:09:20 PM by Tigger
Well, i installed the plugin, rebooted, assigned interfaces like it was said in howto, enabled service, and... "root: /usr/local/etc/rc.d/tor: WARNING: failed to start tor". I don't have a clue what i should to to make it start. I can't even find it's logs.

Please advise.

October 20, 2017, 07:36:25 PM #1 Last Edit: October 23, 2017, 03:09:03 PM by Tigger
Sorry. It had started after second reboot. But now i can't use it. I've created an ACL for my LAN network, Configured browser to use GW address with port 9050 as proxy, but it's not working. I've got only timeouts.

Sorry, i'm stupid. But also, that's an unfinished feature from developer side.

Well, tor binds to interface main address, but not to virtual ip. While i have a HA config with CARP, i tried to use a CARP ip, so i subsequently got nothing.

Due to this i've got a feature request: please make tor bindable to virtual IPs.

Hi Tigger,

I took a closer look since our Tor maintainer is currently not able to program. It's not your fault, it seems tor requires a reboot, because the directory structure is not created properly.

this is the fix coming to the next Tor plugin version: https://github.com/opnsense/plugins/commit/19043bb2

(as it moves files, it should not be used with opnsense-patch)


Cheers,
Franco


Yay, we'll ship this fix and the VIP one in plugin version 1.1 with 17.7.7.


Cheers,
Franco