Building Tahoe-LAFS in pfSense

[dshafirov]

Our group is exploring setups for Tahoe-LAFS grids on private OpenVPN networks. I've found pfSense to be an excellent OpenVPN router. It just doesn't give up keeping VPNs connected. And so I'm curious about the possibility of running Tahoe-LAFS on pfSense, with local xfs storage.

Is that a dumb idea?

To do that, I need to build Tahoe-LAFS. I see from http://forum.pfsense.org/index.php/topic,39738.0.html that I should install the pfSense development builder VM from http://cvs.pfsense.org/~sullrich/pfSenseDevBuilder/pfSense.ova in VirtualBox, and then move output to pfSense. Is that VM for pfSense 2.1?

Also, if I need to add other FreeBSD packages, what repository should I use for the current pfSense development builder VM?

Thanks.

[marcelloc]

The best way to build package is:

• Download freebsd 8.1 i386 and x64

• Create two virtual machines to install freebsd

• After install, on console (or ssh)

• freebsd-update fetch && freebsd-update install

• reboot

• portsnap-fetch && portsnap extract

• using ports build your packages with make config && make package

• send tbz files to a webserver or local pfsense and then to a pkg_add

[dshafirov]

Thank you, marcelloc.  I now have Tahoe-LAFS built and working on FreeBSD 8.1 x64.  As root, I added packages python, py26-setuptools, py26-twisted and py26-sqlite3 (plus wget and unzip for convenience).  Then I built Tahoe-LAFS as user, and verified that it works.

The rest "make config && make package" is unknown territory.  And I'm reading the man pages and googling.  Any further hints would be appreciated.

[marcelloc]

@dshafirov:

The rest "make config && make package" is unknown territory.  And I'm reading the man pages and googling.  Any further hints would be appreciated.

This is used only when compiling packages from ports.