We have a VE on which iptables doesn't start: [root@uk6 ~]# service iptables status Firewall is stopped. [root@uk6 ~]# service iptables start Flushing firewall rules: [ OK ] Setting chains to policy ACCEPT: mangle filter nat [ OK ] [root@uk6 ~]# chkconfig iptables on [root@uk6 ~]# service iptables status Firewall is stopped. [root@uk6 ~]# service iptables restart Flushing firewall rules: [ OK ] Setting chains to policy ACCEPT: mangle filter nat [ OK ] [root@uk6 ~]# service iptables status Firewall is stopped. I have checked other services which seem fine, and even moved the VPS to another node, where the problem persists. The VPS was originally missing BIND, which has now been installed. Any ideas for getting iptables up?
James, I believe it is false alert. iptable modules cannot be loaded inside VE, but if they are loaded on HW node it should be accessible inside all VEs. You can can simple check your iptable rules: iptables -L; iptables -L -t mangle; iptable -t nat -L Therefore it makes sense to trace 'service iptables status' script and look how it tries to recognize the status of this service.