Pyffle Turnkey VMWare Appliance

Pyffle v0.2 – Turnkey VMWare Appliance HOWTO



Unfortunately I was lazy and just used the “Compress File” function in OS X Finder (great dev machine, not sure about Finder) and produced a corrupted ZIP.

The appliance has been repackaged as a .tar.bz2 file and is available below


Download and installation

You can download the system from here:

90659992d77479157e71ca97ea5c1e3d pyffle-turnkey-0.2.tar.bz2
a3d5c2816b0d2d46d4b59fbd06d0aa86 pyffle-turnkey-0.2.ova

To get help:


Note: These instructions are also available in PDF and RTF formats.


This VM contains a basic configuration of Pyffle BBS v0.2, ready to go out of the box (it’s not a VMWare Applicance, I used VMware Fusion to create it but the VMDK and VMX should work on all plaforms).

It’s configured with one CPU, 1 GB of RAM and 10 GB of disk and runs Ubuntu 10 LTS – this should be sufficient for most setups.

This setup is pretty easy to get going but if your Linux/UNIX experince is limited to the console, you’ll have trouble. Seriously.

It WILL work out of the box – you can log in as pyffle, have a look at the board, even send email to the internet via UUCP!

But for production use, please read the instructions below.


Step 0 – Logging in as and getting root

The system is configured with an admin user called ‘pyfadmin’, with the password ‘cafed00d’.

In fact all the passwords are ‘cafed00d’ by default, so you’ll want to change these ASAP (and definitely before exposing the system to the wider Internet).


Step 1 – Securing the system


First of all, you’ll want to change the Unix admin user’s password using the passwd command.

Now we’ll want to change the Postgres passwords:

– Log in as pyfadmin

– Run “sudo su postgres”

– As postgres, run “psql postgres”

– Change the postgres root password with the \password command

– Once that’s done, issue:


You’ll need to tell Pyffle about the new password:

– Exit the su postgres

– Do “sudo su pyffle”

– Edit (with say nano) /pyffle/static (e.g. nano /pyffle/static) and replace:

pyffle.dburl: postgresql://pyffle:cafed00d@localhost/pyffle


pyffle.dburl: postgresql://pyffle:newpassword@localhost/pyffle

(newpassword being the new password you gave the ‘pyffle’ Postgres user above)


Step 2 – Your first log on

Log out as pyfadmin, and log in as pyffle, password pyffle.

Pyffle BBS should now launch.

Log in as “system”, password “cafed00d”

Once at the main prompt, issue USEREDIT SYSTEM and change the system password to something unique.


Step 3 – What’s running, etc.

The system is running telnetd on port 23 and sshd on port 22. Your users will be logging in as the user pyffle (no password) into the Linux VM to launch the BBS.

The VM is configured with NAT’d networking with DHCP enabled – you’ll want to change this to bridged networking for any real work.

To set a static IP, look in /etc/network/interfaces and follow the guidelines for setting a static IP on an Ubuntu 10 system (these guys have a pretty good overview:

Root is running a cronjob ever 5 minutes to poll b4gate via uucico – please see the section below on getting this properly configured.

If you’re going to be running UUCP, you’ll want to edit /etc/hostname and /etc/hosts


Step 4 – Getting connected to UUHECNET

The turnkey system actually is connected to UUHECNET!.

Unfortunately this is using a demo account (turnkey) so you will receive various random stuff addressed to, but it’s good for testing.

Log in as pyfadmin, get root, and type “uucico -s b4gate”

Now run “uulog -10” – you should see entries like:

uucico b4gate - (2013-04-03 06:50:11.47 1643) Calling system b4gate (port TCP)
uucico b4gate - (2013-04-03 06:50:16.09 1643) Login successful
uucico b4gate - (2013-04-03 06:50:18.44 1643) Handshake successful (protocol 't')
uucico b4gate - (2013-04-03 06:50:18.90 1643) Call complete (3 seconds 0 bytes 0 bps)


Try sending an email to the outside world from MAIL, it should get through.

Try replying to this email – if it gets through, you email is being routed through b4gate and the connection is working.


At this point, you will want to email uuhec-reqs (at) and get yourself a UUHECNET node name – tell us you’re using Pyffle and we will send you full instructions on how finalize the configuraton of your system.


This WILL require some understanding of mail and ideally postfix.


Appendix – Weird Ubuntu/VMWare networking problems (i.e. eth0 not showing up):

As root, delete:



Eth0 should now appear.




Leave a Reply

Your email address will not be published. Required fields are marked *