On Thu, Nov 11, 2010 at 12:35 PM, Eric Shubert <[email protected]> wrote:
> On 11/11/2010 11:13 AM, Scott Hughes wrote: > >> On Thu, Nov 11, 2010 at 11:34 AM, Scott Hughes <[email protected] >> <mailto:[email protected]>> wrote: >> >> On Thu, Nov 11, 2010 at 11:21 AM, Eric Shubert <[email protected] >> <mailto:[email protected]>> wrote: >> >> On 11/11/2010 09:40 AM, Scott Hughes wrote: >> >> All, >> >> I continue to have strange firewall issues. The iptables >> firewall is >> acting normal EXCEPT when the system gets restarted. Then >> it is like it >> goes back to some default setting and I have log into the >> console and >> manually run the firewall.sh script. The script >> automatically saves the >> settings with 'service iptables save' and I have run this >> manually as >> well. Still having the same issue. >> >> Anyone out there have any ideas that might save my firewall >> settings >> though restarts/reboots? >> >> Thanks, >> Scott >> >> >> That's peculiar. I expect that something else in your boot >> process is setting the firewall. >> >> After reboot, does the /etc/sysconfig/iptables file contain the >> settings from firewall.sh script or something else? That's the >> file that's normally used to start/restart iptables. >> >> -- >> -Eric 'shubes' >> >> >> I'll have to check that when I can take the server down for a few. >> I know that the when I checked the /etc/sysconfig/iptables file >> AFTER I ran the firewall.sh script, it contained the correct >> information. >> >> Scott >> >> >> After rebooting a new non-production QMT server I checked the >> /etc/sysconfig/iptables file and it looks like it is correct. I was not >> able to SSH into the box until after I run the firewall.sh script (I >> have it set up so that SSH is on a different port). >> >> Once I run the firewall.sh script, I can SSH just like normal. >> >> I've been running Google searches, but they so far have not helped. They >> give me the same commands (service iptables save or >> /etc/init.d/iptables save). Any advice on this one? >> >> Thanks, >> Scott >> >> > Something's changing iptables. If it's not changing the > /etc/sysconfig/iptables file, then it must be changing iptables on the fly, > after init starts iptables (which uses the /etc/sysconfig/iptables file). > Anything in rc.local? > > > -- > -Eric 'shubes' > I think you may have found the issue. Here is what is in rc.local ## Bring up firewall /sbin/iptables-restore < /etc/rc.d/firewall.ruleset I think that is what is causing my issue. Would it be okay to change the /etc/rc.d/firewall.ruleset to /etc/sysconfig/iptables ?? Thanks again, Scott
