Article ID: 118836, created on Nov 24, 2013, last review on Sep 25, 2014

  • Applies to:
  • Virtuozzo
  • Virtuozzo containers for Linux
  • Virtuozzo hypervisor

Symptoms

A container is not accessible on the network:

  • ping attempt from a Windows machine returns request timed out

  • ping attempt from the node or another Linux host does not return anything and reports 100% packet loss

Cause

iptables are incorrectly configured inside the container.

Resolution

Check the configuration of iptables inside the problematic container.

An example of a problem - wrongly set default policies of all chains:

[root@vz ~]# vzctl exec $CTID iptables -S
-P INPUT DROP
-P FORWARD DROP
-P OUTPUT DROP

Here, any traffic received in the container is getting silently dropped.

If the DROP policy has not been configured intentionally, change the policy for the necessary chains by executing the following commands inside the container:

[root@vz ~]# vzctl exec $CTID iptables --policy INPUT ACCEPT
[root@vz ~]# vzctl exec $CTID iptables --policy OUTPUT ACCEPT
[root@vz ~]# vzctl exec $CTID iptables --policy FORWARD ACCEPT

Search Words

request timed out

policy ACCEPT

container does not answer pings

vps cannot be pinged

container cannot be pinged

network

network down after migration

vps does not answer pings

policy DROP

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f e8e50b42231236b82df27684e7ec0beb 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF