Is there a good explanation why in a Debian VE (may be other distro's too?) a venet0 and venet0:0 present? Or is it just that this is more easily created by the script if there are more than one IP-addresses needed? I have created a simpler script which adds just a venet0 if there is need for one IP-address and a venet0:1 and so further if more than one is needed. It seems to work exactly the same, only the ifconfig output and /etc/network/interfaces in the VE just looks nicer and to mee also more logical. I have attached the new debian-add_ip.sh for who is interested...
I don't mean to dig up an old thread, but did you ever figure this out? It appears that this only occurs on Debian based distros.
I've never further investigated why this is happening. On three different OpenVZ servers I now use my own adaptation and never run into a problem which could be attributed to this change. So I think it is safe to strip the venet0:0...
Hi, I haven't been testing a lot of time but let's assume that we add two ip (with --ipadd parameter) to our VPS and then decide to remove the first ip (with --ipdel parameter). Does this operation process correctly?
There is a bug filed for this case: http://bugzilla.openvz.org/883 hvdkamer, can you please add yourself into Cc for this bug so we can move the discussion there?
How can I apply this script to a centos machine? I checked the script and it modifies locations debian specific "debian-add_ip.sh". I love your script!
You mus create a centos-add_ip.sh script with code that creates the correct files in your centos template. I don't know anything about centos, so I can't help there. In the meanwhile I did something similar for Arch Linux which had also the strange and unnecessary venet0:0. After creating the script, you change the centos.conf to use your new script. At the moment it points to a Red Hat script: ADD_IP=redhat-add_ip.sh