
Until then, how is the multi-machine arrangement set up? Right now, my arrangement is like this: In System -> Routing -> Routes it looks like it might be possible to configure the LAN to connect to Tor, and maybe the WAN to correct to Tor too, but I have no idea exactly what should be done to set that up, if it is indeed possible. Although that gadget is probably quite handy like any other portable device might be, pfSense is still the right tool for the job, and I'm sure it can easily be packaged in a similar hardware form - perhaps even the exact same form. Once again, the wheel has been reinvented. On top of that, it's very difficult to make a multi-machine setup that can work for people who want to use it in a portable arrangement. If I can get Tor and Squid to work with multiple machines, I can use that temporarily, but that setup can't be accepted as the "solution" because it's wasteful both for the hardware and the power used to run it (probably also if it's a virtual machine too). Because of that, I haven't yet tried it on another machine. It seemed to be connecting, but it always times out.

I tried disabling Squid's transparent proxy, and then pointing my web browser's proxy configuration to the Tor instance on the pfSense machine, at 192.168.1.1:9050, but it didn't work. Likewise, more tips on using Squid to facilitate it are welcome, since I have no idea what I'm doing yet, and I'll probably need advice. If you or anyone else thinks up a better way, please post. I think it's probably not the "right" way to do this, so I'm guessing there's some sort of fundamental routing configuration that can do this. I'm going to see what happens with it now. I think pfSense is the right tool for the job, and I'm hoping I can get it working well enough to perhaps guide some enhancements to the upcoming Tor package for pfSense to achieve the same goals. The one thing they all have in common is they each tried to reinvent the wheel to build upon their own platforms. There are many similar efforts, and many are now defunct. The Whonix system was created to serve this need, and I think pfSense can provide a better platform. Once it's available, I hope it will be inviting for people to add features to it, like hidden services and forced-Tor routing. I just installed the Squid package, and I'll see what happens when I follow your suggestions.Ī member of the New York York *BSD User Group is working on a package for Tor. Tor supports any TCP port or protocol (it might be possible to tunnel UDP), but I think using Squid as a facilitator would restrict usage to only HTTP ports, right? That might not matter much, at least for the purpose of getting something to work soon.


I had a similar half-baked idea that involved using a VPN, but I never came up with anything that would work.
