Package: firestarter
Version: 1.0.3-8
Priority: important
Tags: patch

Firestarter sets up two scripts in if-down.d and if-up.d which have
the same content and restart the firewall whenever an interface is
configure or unconfigured.

Since firestarter might be configured (through the wizard) to use a
defined external and internal interface, it will emit all kind of
errors if the interface that is being configured (up or down) is not
relevant for firestarter and the interface that it uses (for example,
a dialup connection) is not available.

For example, I get the following errors when starting up a Wireless
interface when a 3G USB modem is not plugged on (device ppp0), with
Firestarter configured to use the ppp0 interface:

-------------------------------------------------------------------------------------------------
$ sudo ifup eth1=wifi
Stopping the Firestarter firewall...ppp0: error fetching interface
information: Device not found
ppp0: error fetching interface information: Device not found
ppp0: error fetching interface information: Device not found
.
Starting the Firestarter firewall...ppp0: error fetching interface
information: Device not found
ppp0: error fetching interface information: Device not found
ppp0: error fetching interface information: Device not found
 failed!
invoke-rc.d: initscript firestarter, action "restart" failed.
run-parts: /etc/network/if-up.d/50firestarter exited with return code 2
-------------------------------------------------------------------------------------------------

The attached alternative script should be used to replace the
50firestarter script currently being used. This script will:

- check if the interface that is being operated is not 'lo'
- check if firestarter is properly configured with an internal an
external interface
- check if the interface being restarted is the same as the one
configured in firestarter

If these checks are OK  firestarter will be restarted. The script will
just exit otherwise.

This prevents the errors above as well as some other errors that might
show up when firestarter is not properly configured and an interface
is ifuped/ifdowned.

Please use this script in the package.

Regards

Javier

Attachment: 50firestarter
Description: Binary data

Reply via email to