firehol forbids it...

[pelle.k]

The summary says it all. Try starting or restarting firehol results in a "pelle@hemma1:~$ sudo /etc/init.d/firehol restart
Restarting iptables firewall: FireHOL ...Stopping: /etc/default/firehol forbids it.
done"

Sometimes, It reports nothing, iptables show no rules created.

firehol in breezy never did work for me either.

Installing it from official source works though.

[Tero Karvinen (karvinen+launchpad)]

To enable it, user must change in /etc/default/firehol:
START_FIREHOL=YES
and then 'sudo /etc/init.d/firehol restart'

I think it should be changed to YES by default. The default firehol configuration does what a firewall is supposed to do (allow all client access, deny all serves). Other Ubuntu packages are installed to usable state by apt, for example acache2 is started automatically.

If user installs firehol, he probably wants to enable firewall - why would he install firehol otherwise?

[Carthik Sharma (carthik)]

Assigning to MOTU.
Confirmed by another reporter.

[Dave Walker (davewalker)]

Other packages such as LIRC provide a similar method to enable. In this instance it's to ensure that the user has set the relevant rules in place prior to starting firehol to avoid lock outs. However, it should provide a more sane error.

Marking as Invalid.

[Phil Bull (philbull)]

Is this 'enabling' procedure documented?