| network differences between Virtuozzo and OpenVZ [message #38870] |
Sun, 14 February 2010 04:15  |
galaxy
Messages: 11
Registered: January 2006
|
Junior Member |
|
|
I need to move a container from Virtuozzo to OpenVZ. When I moved the container over, all looked well, however I could not reach any IP's of the container on the OpenVZ node, however it works fine with Virtuozzo.
In both cases, the HW (hardware node) only has a private IP address on the physical interface. The containers may have either private, public or both.
Here's the configuration:
Virtuozzo HW:
IP: 10.0.0.21
Gateway: 10.0.0.2
additional static route added in /etc/init.d/network for VPN:
/sbin/route add -net 10.1.2.0 netmask 255.255.255.0 gw 10.0.0.254
Inside Virtuozzo container:
IP: Hundreds of them in public space
GATEWAY="191.255.255.1"
(I'm not sure why the gateway is set to that, but VZ set that up)
On the OpenVZ HW node:
IP: 10.0.0.22
Gateway: 10.0.0.2
same static route above is added
Inside the OpenVZ container:
Same IP's, Gateway seems to be set to 192.0.2.1 (but again I did not set that).
Note that from the hardware node (in both cases), I can ping all the public addresses. But if I go to another host with only public IP's, I can only ping the ones on Virtuozzo, but none of them on OpenVZ.
So what are the differences between networking in Virtuozzo and OpenVZ?
I thought I could just rsync over the VE from /vz/private/root/101 on Virtuozzo (while mounted) to the OpenVZ node to /vz/private/101 and copy the 101.conf file from /etc/sysconfig/vz-scripts/101.conf
What am I missing?
Thanks in advance...
EDIT: One thing I forgot to mention is that this USED to work with an older version of OpenVZ. I just realized that I totally rebuilt the server and put all newer software on it. The prior version that worked was when Fedora Core 1 was out.
[Updated on: Sun, 14 February 2010 20:03] Report message to a moderator |
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
