OpenVZ Forum


Home » General » Support » vServer sets venet although it shouldn't
Re: vServer sets venet although it shouldn't [message #35616 is a reply to message #35613] Wed, 08 April 2009 14:05 Go to previous messageGo to previous message
divB is currently offline  divB
Messages: 79
Registered: April 2009
Member
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?!

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.

This is the file OpenVZ obviously created inside the VE (I even do not understand where the 192.0.2.x come from):

# This configuration file is auto-generated.
# WARNING: Do not edit this file, otherwise your changes will be lost.
# Please edit template /etc/network/interfaces.template instead.


# Auto generated interfaces
auto lo
iface lo inet loopback

auto venet0
iface venet0 inet static
	address 127.0.0.1
	netmask 255.255.255.255
	broadcast 0.0.0.0
	up route add -net 192.0.2.1 netmask 255.255.255.255 dev venet0
	up route add default gw 192.0.2.1
auto venet0:0
iface venet0:0 inet static
	address 192.168.200.112
	netmask 255.255.255.255
	broadcast 0.0.0.0


Regards,
divB

 
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:
  


Current Time: Thu Oct 17 10:40:53 GMT 2024

Total time taken to generate the page: 0.05203 seconds