From my experiments in 1) I concluded that the firewall startup-scripts only work if a connection via, say, ppp was already established. So what about my dial-up connection. I boot my machine and during that process the firewall starts to build-up, BUT since I am not connected yet, since I only want to surf or read emails for a short time, the firewall isn't
Hi, thanks to the hints on this list it wasn't a problem at all to install the new firewall scripts from Marc. I still have 2 questions: 1) If I start the firewall as root with /sbin/SuSEfirewall everything works just fine if there is a ppp connection to my provider to which I dial-up from time to time. BUT, I like to use the program 'kppp' for dialing since it gives me good accounting information is easy to use and so on... So, I prefer this solution instead of wvdial. THE PROBLEM is that the firewall gets only started with the ip-up script which is executed by wvdial BUT NOT by kppp, since kppp manages everything itself. If I want to call SuSEfirewall as a normal user it doesn't work, of course... 2) properly installed... Maybe these questions are stupid, especially the latter (I am quite sure that I didn't understand the functionality of those init scripts), but I hope someone could help me! Should be a common problem though. Regards, Marko -- O _ O 0 0 ------------------m-\o/-m------------------------------------------ Dr. Marko K"aning Tel/Fax: +49-3834 554 442 / -3834 554 301 INP Greifswald email : kaening@inp-greifswald.de