On 10/24/2008 5:24 PM, Joey wrote:
I think with all the times we loaded and unloaded our iptables configs and using the type executed by command line, then through iptables-save etc that we trashed iptables hence it was blocking IP's we weren't expecting. For right now I think the reboot did it....
Ok... If you are comfortable with that, I guess that is ok. I would suggest keeping an eye on things. To me that type of failure is a symptom of an underlying bug. However seeing as how we can't duplicate the problem we can't troubleshoot it, so it may have been the difference between a "-s" and a "-d" in a script that was accidentally created and subsequently corrected. So it is hard to say.
Either way seeing that things are working as expected I'd say you are good to go.
Thanks for all your help!
You are welcome. Grant. . . . -- To unsubscribe from this list: send the line "unsubscribe netfilter" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
