Would this one work ok ? Hi Robert, http://www.jungcom.de/Linux/downloads/firewall.rc.config Would the above rc.firewall.config work ok on my setup where currently 192.168.0.1 is my windows 2000 box with a dialup and 192.168.0.2 and 192.168.0.3 (linux boxes). Once the linux box (192.168.0.2) boots up ok I will move it to dialing out on my linux box. all boxes have eth0 and 192.168.0.1 has the modem on. I connect to an ISP with a dynamic IP address and gateway address too. (I normaly set my boxes to 0.0.0.0 also). Regards Matt -----Original Message----- From: Robert Davies [mailto:Rob_Davies@NTLWorld.Com] Sent: 28 May 2001 15:51 To: Matt; suse-security@suse.com Subject: Re: [suse-security] Orginal firewall.rc.config file ?
Now that I am having all these problems with firewalls etc and maybe messed up my orginal firewall.rc.config file does any one have an orginal one that I could use as a template please ?
You have it already to extract it look at rpm(8), this will get you on the right track, it goes something like the following : rpm -qf /etc/rc.config.d/firewall.rc.config Tells you which rpm package the file belongs to, you can confirm with, rpm -ql <package>. To see what files have been altered, use the verify option. rpm --verify <package> Perhaps you want to compare with the CD-ROM of installation? rpm -Vp /cdrom/suse/<packet>/<rpmfile> You can reinstall, and you can also extract the RPM to a different root directory, avoiding updating the machine rpm database. Another good option with many files, is to install the source rpm, and find the configuration file in their, and then diff. I like to use rcs(1) to have version control on these files, which allows me to record reasons for, and to easily back out changes with ci(1) and co(1). rcsdiff(1) is also very useful! Install the package from the development packets and then create an RCS directory in /etc. Remember to 'ci -u' to get an unlocked readable copy of the file, when you have made changes, you can see files status with $Id$ and the log in the file, with the $Log$ flag. Rob --------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com