Well, of course, Firestarter is not the firewall, iptables is. I do not
see how to check whether iptables is running - maybe it runs all the
time as much of it is in the kernel and running Firestarter merely
updates the configuration. However, it can clearly be in a stopped
condition.
Anyway, as I wrote, the boot sequence ran /etc/init.d/firestarter. This
in turn ran /etc/firestarter/firestarter.sh . This, I have discovered,
bombed out at line 33 with
External network device $IF is not ready. Aborting..
Apparently before it does much at all.
So there does not seem to be any point in having it run on boot
and I have removed it from the sequence using sysv-rc-conf . That gets
rid of the failure message on start up and Firestarter starts as before
using the GUI interface, which needs the root password to start it.
It seems that there is a bug in the configuration that includes
Firestarter in the boot sequence even though it is configured to start
on dialup.
Now, how to get the ifup script to start Firestarter automatically.
John Talbut
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
