Article ID: 120640, created on Mar 20, 2014, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo 6.0
  • Virtual Automation 6.0


  1. The container is not reachable on the newly assigned IP address.
  2. The container uses Bridged networking mode.
  3. The new IP address was assigned to container either from PVA Management node or using vzctl set command.
  4. The interface has "configure=all" in the "NETIF" veriable in the container's configuration file.

The problem is solved after the container is restarted.


Starting with PCS 6.0, the Dispatcher process configures Ethernet bridges filtering rules for containers in the bridged mode to protect other environments from IP spoofing. vzctl does not send notifications to Dispatcher on adding a new IP address to a container in the bridged mode.

The issue is recognized as a product bug with the internal ID PSBM-24952.


The fix is included in Parallels Cloud Server 6.0 Update 6 (6.0.6-1992).

In case the node cannot be updated right away, there is a number of workarounds to try:

  1. Re-assign the new IP address with prlctl utility:

    ~# vzctl set CTID --ifname eth0 --ipdel xx.xx.xx.xx
    ~# prlctl set CTID --device-set net0 --ipadd xx.xx.xx.xx/mask

    Note: use the proper interface name for vzctl set - this is the Ethernet interface name in the container as returned by ip link; use the network interface for prlctl set as it is shown by prlctl list CTID -i.

  2. If the IP address has already been assigned from PVA or via vzctl, it's possible to modify ebtables rules accordingly. Real-life example:

    [root@vz ~]# vzlist 821 -Ho ip
    [root@vz ~]# vzctl set 821 --ifname eth0 --ipadd --save
    Configure virtual adapters: veth821.0
    Saved parameters for Container 821
    [root@vz ~]# ebtables-save | grep
    -A ip-filter-veth821-0 --among-src 0:18:51:5f:f9:4f=, -j ACCEPT
    [root@vz ~]# ebtables -D ip-filter-veth821-0 --among-src 0:18:51:5f:f9:4f=, -j ACCEPT
    [root@vz ~]# ebtables -A ip-filter-veth821-0 --among-src 0:18:51:5f:f9:4f=,0:18:51:5f:f9:4f=, -j ACCEPT
  3. Restart the container.

Search Words

container cannot be reached on new IP




virtual ip container

add an ip address and cannot ping afterwards

ebtables rules are not updated

container IP is not added to ebtables

ebtables are not updated with container's IP

319940068c5fa20655215d590b7be29b 2897d76d56d2010f4e3a28f864d69223 c62e8726973f80975db0531f1ed5c6a2 0dd5b9380c7d4884d77587f3eb0fa8ef 0889ab60fa6494de107aa7338c3c38b6

Email subscription for changes to this article
Save as PDF