OpenVZ Forum


Home » General » Support » vServer sets venet although it shouldn't
Re: vServer sets venet although it shouldn't [message #35623 is a reply to message #35616] Thu, 09 April 2009 06:07 Go to previous message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Hello,

Quote:


I think I have found it. It's rather set inside the networking config in the VE itself (and not the host!).

But I do not understand this: Normally the the VE should not be able to assign itself an IP address if it is not set by the host?! This would mean I could just do an "ifconfig venet0:0 192.168.200.113 netmask 255.255.255.0 up" inside my VE and have another IP address?!


No, this configuration file is generated every time VE is starting.
Quote:


WARNING: Do not edit this file, otherwise your changes will be lost.



So, if you bump into the problem described in bug #478 try to start VE and then remove that ip address.
So, in case of venet0 interface you are not permitted to make permanent changes. During the next start process, information will be read from VEs configuration file.

Quote:


And what is exactly the loopback interface inside a VE? Is it lo or is it "venet0"? I ask because venet0 is assigned 127.0.0.1.


Loopback is a loopback interface and venet0 is a venet interface Smile
Assigning 127.0.0.1 to venet0 interface is just a convenient way to treat with networking inside VE. Don't worry, it doesn't break anything.

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: How to rebuild a openvz kernel in linux kernel with version 2.6.24.7 ?
Next Topic: kernel 2.6.27-openvz fails to compile
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sat Sep 05 02:28:47 GMT 2026

Total time taken to generate the page: 0.05495 seconds
Powered by FUDforum Powered by Virtuozzo Containers