|
Re: Add an private IP address into a CT [message #52462 is a reply to message #52423] |
Tue, 12 July 2016 17:01 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
![](https://forum.openvz.org/images/custom_avatars/125.jpg) |
dowdle
Messages: 261 Registered: December 2005 Location: Bozeman, Montana
|
Senior Member |
|
|
OpenVZ Legacy provides two types of network interfaces, venet (the default) and veth. For info on how they differ see:
https://openvz.org/Differences_between_venet_and_veth
Unless you have a need for layer 2 (MAC) services and paid more for it, it is likely you have a venet device... and such devices are controlled and managed by the system administrator of the host node. Even if you got it configured correctly in your container's configuration, it would be reset upon container restart. That's just how venet devices work. It is also possible, if you manually alter the container network config enough to confuse the IP address injection code in vzctl, you could completely break your networking... so manually editing your network configuration is not recommended.
The proper solution to your issue requires you contacting the support services for your hosting provider and telling them what you want... and them assisting you.
--
TYL, Scott Dowdle
Belgrade, Montana, USA
|
|
|
|