All ports are closed after rebooting
Matt Randolph <[email protected]>
| Newsgroups | gmane.network.guarddog |
|---|---|
| Message-ID | <[email protected]> |
I'm using Guarddog 2.4.0 on Gentoo. All of my ports are closed after a reboot unless I manually run Guarddog and click OK or Apply. When I do run Guarddog, the appropriate ports are opened and I can use the web, etc. The first time I rebooted after installing and configuring Guarddog, iptables failed to load because it couldn't find a configuration file. I believe the error message was: Not starting iptables. First create some rules then run: /etc/init.d/iptables save I ran Guarddog and then did `/etc/init.d/iptables save` and iptables loaded succesfully on my next reboot. Nonetheless, all of my ports continue to be closed upon rebooting. I still have to explicitly run Guarddog to get any ports to open. I have tried to find out just what it is that changes when I run Guarddog. One thing that does change is that the ip_conntrack_ftp module gets loaded by Guarddog. I have tried loading this module manually instead of running Guarddog, but it doesn't solve the problem. As a side note, if I build ip_conntrack_ftp into the kernel instead of as a module, Guarddog reports that the module is missing in the form of a fatal error. I'd be happy to post my configuration files or that error message if that would be helpful. I can also list the relevant lines of my kernel configuration. I'm getting by with the workaround for now, but I really hope to find out what the solution is. Thanks. ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf