<!DOCTYPE html>
<html>
<head>
<title></title>
<style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style>
</head>
<body><div><br></div>
<div>I posted the below message some days ago and got no response. Since then I tried again, and managed to figure out a way -- if not THE way -- to fix. I had previously installed the Tor package using Plinth and the web interface, but my Tor ports were not reachable from the outside. Tried a lot of things (in my naive way), no luck, gave up, started over with a totally fresh OS installation, hoping to wipe the slate clean.<br></div>
<div><br></div>
<div>Next, I simply installed with `apt install tor`. Again, port not reachable errors. Finally I figured out firewall-cmd enough to open the ports manually (so to speak), with `firewall-cmd --permanent --add-port=9001/tcp --zone=internal`, and again for port 9030. Now my life is happy.<br></div>
<div><br></div>
<div>But that raises the question of whether the UI for Tor installation and setup has an issue in Plinth. I am not sure, that's why I ask, but I would have thought Plinth would have automatically done the firewall config for me. So I looked for a bug report at <a href="https://salsa.debian.org/freedombox-team/plinth/issues">https://salsa.debian.org/freedombox-team/plinth/issues</a> and could not find anything relevant when filtering for "tor".<br></div>
<div><br></div>
<div>Any thoughts as to how to figure out whether there's an issue to report?<br></div>
<div><br></div>
<div>---<br></div>
<div>David Mintz<br></div>
<div>https://davidmintz.org<br></div>
<div>Capitalism has failed. https://wsws.org<br></div>
<div><br></div>
<div>On Tue, Jan 29, 2019, at 10:02 AM, David Mintz wrote:<br></div>
<div>><br></div>
<div>> I've been happily running a Tor relay node -- the publicly published,<br></div>
<div>> non-exit kind -- on a desktop machine, and decided it would be nice to<br></div>
<div>> use FreedomBox on a SBC for that instead, to avoid the need to keep the<br></div>
<div>> desktop powered up 24x7 just for the sake of the Tor node. So I got a<br></div>
<div>> Raspberry Pi 3 B+ and installed FreedomBox per the instructions -- so<br></div>
<div>> far so good. This is behind a Verizon router with port forwarding<br></div>
<div>> configured appropriately.<br></div>
<div>><br></div>
<div>> Then I tried installing Tor on the Raspberry through plinth, and<br></div>
<div>> updating the port forwarding accordingly (i.e., disabled the rule that<br></div>
<div>> forwarded to the desktop box and added one to forward to the FreedomBox;<br></div>
<div>> I'm confident I got my IP addresses and port numbers right.) I got<br></div>
<div>> errors to the effect that my Tor was not reachable from the outside. I<br></div>
<div>> tried all kinds of fiddling with systemd configs, with tor config files,<br></div>
<div>> etc., to no avail.<br></div>
<div>><br></div>
<div>> Please forgive me for the sin of not providing actual error output,<br></div>
<div>> configurations, a detailed narrative of what I did, etc. I got impatient<br></div>
<div>> and re-installed everything, and went back to running Tor on my desktop<br></div>
<div>> for now, and all that information is unavailable. I just want to ask as<br></div>
<div>> a general question whether I should expect the following alternative<br></div>
<div>> strategy to work:<br></div>
<div>><br></div>
<div>> (1) disable Tor on the desktop and remove port forwarding rules.<br></div>
<div>><br></div>
<div>> (2) enable port forwarding to the FreedomBox, consistent with the ORPort<br></div>
<div>> and DirPort numbers set in the tor config<br></div>
<div>><br></div>
<div>> (3) install tor from the command line according to<br></div>
<div>> https://www.torproject.org/docs/debian.html.en<br></div>
<div>><br></div>
<div>> (4) copy my torrc file over from the desktop and restart the service<br></div>
<div>><br></div>
<div><br></div>
</body>
</html>