BleepingComputer.com: Firestarter fails to load on startup

Hello,

I'm using Ubuntu 8.04 and recently a new thing has been happening on my computer. When I boot into Ubuntu the splash screen shows and the progress bar advances across the screen until it is about 95% done.

At this point the splash screen disappears and a text screen appears. This is new behavior. On this text screen is a list of loading modules, and near the top Firestarter is listed and in the right hand column the word FAIL appears.

I take this to mean that my firewall is failing to load at startup. I can manually start it from the menu within Ubuntu and it runs normally.

Should I be concerned about it failing to load at startup? Is there a way to fix this problem?

Thanks for any help you can be.

Later, Ray Parrish

Hello,

Well, it seems like no one knows...

That's OK as I've noticed that if I start Firestarter from the menu after I've been surfing and reading email for a while, that Firestarter is aware of the amount of traffic I've already had so it must be on in the background.

Later, Ray Parrish

From the little research I did on this it seems that Firestarter does
not like being started as a "service". Something along the lines of
the service trying to start before eth0 is actually up.
Starting it after the system is up seems to be the solution.

I tried Firestarter some time back and just had fits. For some reason it blocked
my CUPS server and my machine would just hang. Don't know if it's available
for Ubuntu, but I use ShoreWall.
Newbie Tip: ShoreWall is not easy to use. No point/click GUI and requires some
knowledge of iptables.