Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

In iptables INPUT, FORWARD and OUTPUT chains, should nova-compute rules come first or linuxbri rules?

I am having issues pining my VMs on an internal network from outside the network as well as from the router connecting the network to the outside world. This works intermittently. I have installed openstack grizzly on a single node and I am trying to install cloudfoundry on top of that. What I have noticed is that if in the rules, nova-compute comes before linuxbri, everything works fine because I have the rules set up as such for the compute. But every time cloudfoundry tried to instantiate a new VM, the order of the nova-compute and linuxbri rules get flipped and i can no longer ping the VMs. Here is an output of the working case of iptables (just the top section which is the only difference)

NOT Working Case :

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
quantum-linuxbri-INPUT  all  --  anywhere             anywhere
nova-compute-INPUT  all  --  anywhere             anywhere
nova-api-INPUT  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
quantum-filter-top  all  --  anywhere             anywhere
quantum-linuxbri-FORWARD  all  --  anywhere             anywhere
nova-filter-top  all  --  anywhere             anywhere
nova-compute-FORWARD  all  --  anywhere             anywhere
nova-api-FORWARD  all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
quantum-filter-top  all  --  anywhere             anywhere
quantum-linuxbri-OUTPUT  all  --  anywhere             anywhere
nova-filter-top  all  --  anywhere             anywhere
nova-compute-OUTPUT  all  --  anywhere             anywhere
nova-api-OUTPUT  all  --  anywhere             anywhere

WORKING CASE:

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
nova-compute-INPUT  all  --  anywhere             anywhere
quantum-linuxbri-INPUT  all  --  anywhere             anywhere
nova-api-INPUT  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
nova-filter-top  all  --  anywhere             anywhere
nova-compute-FORWARD  all  --  anywhere             anywhere
quantum-filter-top  all  --  anywhere             anywhere
quantum-linuxbri-FORWARD  all  --  anywhere             anywhere
nova-api-FORWARD  all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
nova-filter-top  all  --  anywhere             anywhere
nova-compute-OUTPUT  all  --  anywhere             anywhere
quantum-filter-top  all  --  anywhere             anywhere
quantum-linuxbri-OUTPUT  all  --  anywhere             anywhere
nova-api-OUTPUT  all  --  anywhere             anywhere

Any help is appreciated!

In iptables INPUT, FORWARD and OUTPUT chains, should nova-compute rules come first or linuxbri rules?

I am having issues pining my VMs on an internal network from outside the network as well as from the router connecting the network to the outside world. This works intermittently. I have installed openstack grizzly on a single node and I am trying to install cloudfoundry on top of that. What I have noticed is that if in the rules, nova-compute comes before linuxbri, everything works fine because I have the rules set up as such for the compute. But every time cloudfoundry tried to instantiate a new VM, the order of the nova-compute and linuxbri rules get flipped and i can no longer ping the VMs. Here is an output of the working case of iptables (just the top section which is the only difference)

NOT Working Case :

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
quantum-linuxbri-INPUT  all  --  anywhere             anywhere
nova-compute-INPUT  all  --  anywhere             anywhere
nova-api-INPUT  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
quantum-filter-top  all  --  anywhere             anywhere
quantum-linuxbri-FORWARD  all  --  anywhere             anywhere
nova-filter-top  all  --  anywhere             anywhere
nova-compute-FORWARD  all  --  anywhere             anywhere
nova-api-FORWARD  all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
quantum-filter-top  all  --  anywhere             anywhere
quantum-linuxbri-OUTPUT  all  --  anywhere             anywhere
nova-filter-top  all  --  anywhere             anywhere
nova-compute-OUTPUT  all  --  anywhere             anywhere
nova-api-OUTPUT  all  --  anywhere             anywhere

WORKING CASE:

Chain INPUT (policy ACCEPT)
target     prot opt source               destination
nova-compute-INPUT  all  --  anywhere             anywhere
quantum-linuxbri-INPUT  all  --  anywhere             anywhere
nova-api-INPUT  all  --  anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
nova-filter-top  all  --  anywhere             anywhere
nova-compute-FORWARD  all  --  anywhere             anywhere
quantum-filter-top  all  --  anywhere             anywhere
quantum-linuxbri-FORWARD  all  --  anywhere             anywhere
nova-api-FORWARD  all  --  anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
nova-filter-top  all  --  anywhere             anywhere
nova-compute-OUTPUT  all  --  anywhere             anywhere
quantum-filter-top  all  --  anywhere             anywhere
quantum-linuxbri-OUTPUT  all  --  anywhere             anywhere
nova-api-OUTPUT  all  --  anywhere             anywhere

Any help is appreciated!