Blocks all traffic after disable testing mode
Posted: 19 Apr 2014, 02:30
I'm also experiencing this issue, although this is my own server in my own datacenter.
Installed minimal install of CentOS 6.5, then continued by installing OpenVZ. Created a container, installed cPanel, followed by csf. All default settings, no changes. Tried this on 2 separate servers, both with the same result. All that I changed was disabling testing mode.
CSF does work, but blocks ALL traffic. Not sure how to fix it. Basically, if you add an IP to csf.allow, it is allowed through.
I've tried all of the help listed in the sticky posts, one particular one has 3 broken links in it for VPS providers but can't get to the info.
One thing I did notice however, is that if you don't disable OR flush & save iptables rules before booting into OpenVZ kernel after installation, you won't get access to your box afterwards. Had to go to DC and disable iptables on the HW node to regain access.
Also tried setting various settings in /etc/csf/csf.conf such as directed by several sites while searching through Google, such as the ETH device to venet+, setting conntrack mode to 1, adding inital rules in csfpre or csfpost...
Any help on this would be greatly appreciated, very difficult to get a new server going, I don't remember it being this difficult on the 30+ other servers I've configured in the past.
No fatal errors in csftest:
Installed minimal install of CentOS 6.5, then continued by installing OpenVZ. Created a container, installed cPanel, followed by csf. All default settings, no changes. Tried this on 2 separate servers, both with the same result. All that I changed was disabling testing mode.
CSF does work, but blocks ALL traffic. Not sure how to fix it. Basically, if you add an IP to csf.allow, it is allowed through.
I've tried all of the help listed in the sticky posts, one particular one has 3 broken links in it for VPS providers but can't get to the info.
One thing I did notice however, is that if you don't disable OR flush & save iptables rules before booting into OpenVZ kernel after installation, you won't get access to your box afterwards. Had to go to DC and disable iptables on the HW node to regain access.
Also tried setting various settings in /etc/csf/csf.conf such as directed by several sites while searching through Google, such as the ETH device to venet+, setting conntrack mode to 1, adding inital rules in csfpre or csfpost...
Any help on this would be greatly appreciated, very difficult to get a new server going, I don't remember it being this difficult on the 30+ other servers I've configured in the past.
No fatal errors in csftest:
Testing ip_tables/iptable_filter...OK
Testing ipt_LOG...OK
Testing ipt_multiport/xt_multiport...OK
Testing ipt_REJECT...OK
Testing ipt_state/xt_state...OK
Testing ipt_limit/xt_limit...OK
Testing ipt_recent...OK
Testing xt_connlimit...OK
Testing ipt_owner/xt_owner...OK
Testing iptable_nat/ipt_REDIRECT...FAILED [Error: FATAL: Module ip_tables not found.] - Required for MESSENGER feature
Testing iptable_nat/ipt_DNAT...FAILED [Error: FATAL: Module ip_tables not found.] - Required for csf.redirect feature
RESULT: csf will function on this server but some features will not work due to some missing iptables modules [2]
