My choice for a "personal" firewall on older systems is Firestarter.
It has always failed to start on boot up. (Debian wheezy and prior)

I don't care that it doesn't autostart on boot up.
(Found a work around)
However constantly seeing the error message is annoying.

Running 0dns-down to make sure resolv.conf is ok...done.
Starting the Firestarter firewall...^[[?25l^[[?1c^[7^[[1G[^[[31mFAIL^[[39;49m^[8^[[?25h^[[?0c ^[[31mfailed!^[[39;49m

Setting console screen modes.

Setting sensors limits^[[?25l^[[?1c^[7^[[1G[^[[32m ok
[....] startpar: service(s) returned failure: firestarter ...^[[?25l^[[?1c^[7^[[1G[^[[31mFAIL^[[39;49m^[8^[[?25h^[[?0c ^[[31mfailed!^[[39;49m
Sun Feb 1 08:41:28 2015: INIT: Entering runlevel: 5


What process is be used to start Firestarter at bootup?
It's not being done from any of the run level init dirs.

Thank you advance for any advice or suggestions.

Tom

Firestarter is not a firewall; it is a GUI frontend for configuring iptables. Once you have iptables configured, you don't need to run Firestarter unless you wish to change your configuration.

You can check your firewall configuration with the command

I understand that Firestarter has ceased development. An excellent GUI replacement is gufw.