Article ID: 120641, created on Mar 20, 2014, last review on Aug 13, 2015

  • Applies to:
  • Operations Automation
  • Panels
  • Virtuozzo containers for Windows

Symptoms

If you manually enabled VPN support for the Parallels Virtuozzo for Windows (PVC) container, you may experience situations when container can suddenly become inaccessible over network.

Error that can be observed on PVC node in \vzlog\YY.MM.DD-vzlog.log for this container:

{0000000078152198}; T=2014.03.03 01:00:40.419; A=VzSrv; P=1824.100016; S=VZSRV; F=build\4.6.490.0\sources\virtuozzo\vzwin\vzmain\vzsrv\redirect.c,StartVPSIpRedirection,347; L=INFO; R=87(135); C=0(0); M=135 []  IP list empty for container '1001', netif1

Upon checking the affected container's configuraiton file on PVC node at %vzroot%\Conf\CT_ID.conf it is visible that the network section is missing NetIf0 adapter, while all the network settings (ip, dns, gateway) are assigned to the VPN interface:

NetIf1.AdapterGuid="{76BC3805-C98C-46AF-8E27-D08FDFE9D8FA}" 
NetIf1.IfName="Vpn" 
NetIf1.IP="192.168.96.17/23" 
NetIf1.IPV6Addr="" 
NetIf1.IPV6DNSservers="" 
NetIf1.MsVpn="1" 

Cause

  1. POA is not intended to manage VPSes that are modified externally by vzctl.

  2. POA does not support VPSes with multiple network interfaces, we are plannig to add this functionality in scope of POA-58063.

Resolution

It is recommended to refrain from enabling VPN support for containers directly on the node for PVC containers that are part of POA environment.

In order to restore the functionality of the broken conatiner it is needed to recreate the network settings from scratch.

The example of commands are below (for the case of host-routed adapter):

C:\Users\psupport>vzctl set 101 --netif_del vpn
Command 'set' is successfully finished

C:\Users\psupport>vzctl set 101 --netif_del venet0
Command 'set' is successfully finished

C:\Users\psupport>vzctl set 101 --netif_add venet0 --nettype routed
Command 'set' is successfully finished

C:\Users\psupport>vzctl set 101 --ipadd 203.0.113.2 --save
Command 'set' is successfully finished

C:\Users\psupport>vzctl set 101 --nameserver 203.0.113.1 --save
Command 'set' is successfully finished

C:\Users\psupport>vzctl set 101 --vpn on --save
Command 'set' is successfully finished

C:\Users\psupport>vzlist 101

    VEID  NPROC  STATUS   IP_ADDR       HOSTNAME
     101     --  stopped  203.0.113.2  s1085574

C:\Users\psupport>vzctl start 101
Starting container ...
Container is mounted
Container was started

C:\Users\psupport>vzlist 101

    VEID  NPROC  STATUS   IP_ADDR       HOSTNAME
     101     46  running  203.0.113.2  s1085574

C:\Users\psupport>vzctl exec 101 ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time<1ms TTL=128
Reply from 8.8.8.8: bytes=32 time<1ms TTL=128
Reply from 8.8.8.8: bytes=32 time<1ms TTL=128
Reply from 8.8.8.8: bytes=32 time<1ms TTL=128

Search Words

Cant connect to vps

IP list empty for container

no ip assigned

IP list empty for container netif1

pvc

PVCfW

Container with VPN enabled lost network interface venet0

no ip

POA

d02f9caf3e11b191a38179103495106f 2897d76d56d2010f4e3a28f864d69223 965b49118115a610e93635d21c5694a8 5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 614fd0b754f34d5efe9627f2057b8642 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF