Problem with starting debian network

[lusyen]

Hello,

I Use this debian-7.0-standard_7.0-2_i386.tar.gz on VZ, and after start, container looks like network not up correctly, can not ping in/out.

How can assign this 174.1.1.131 to VZ?

root@node:/etc/network# cat interfaces

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 174.1.1.130
netmask 255.255.255.224
gateway 174.1.1.129


auto eth0:0
iface eth0:0 inet static
address 174.1.1.131
netmask 255.255.255.224
gateway 174.1.1.129

----

root@VZ:/etc/network# cat interfaces
auto lo
iface lo inet loopback
# Auto generated venet0 interface
auto venet0
iface venet0 inet manual
up ifconfig venet0 up
up ifconfig venet0 127.0.0.2
up route add default dev venet0
down route del default dev venet0
down ifconfig venet0 down
iface venet0 inet6 manual
up route -A inet6 add default dev venet0
down route -A inet6 del default dev venet0
auto venet0:0
iface venet0:0 inet static
address 174.1.1.131
netmask 255.255.255.255

 

[Richard]

I Use this debian-7.0-standard_7.0-2_i386.tar.gz on VZ, and after start, container looks like network not up correctly, can not ping in/out.

Remove the following:

auto eth0:0
iface eth0:0 inet static
address 174.1.1.131
netmask 255.255.255.224
gateway 174.1.1.129

 

[lusyen]

thanks, i.ve assignet the ip, but when trying to restart the network from vps, i get this error:

root@VZ:/etc/network# /etc/init.d/networking restart
[....] Running /etc/init.d/networking restart is deprecated because it may not r[warnble some interfaces ... (warning).
[....] Reconfiguring network interfaces...SIOCADDRT: File exists
Failed to bring up venet0.
done.
How can fix?

 

[Richard]

thanks, i.ve assignet the ip, but when trying to restart the network from vps, i get this error:

root@VZ:/etc/network# /etc/init.d/networking restart
[....] Running /etc/init.d/networking restart is deprecated because it may not r[warnble some interfaces ... (warning).
[....] Reconfiguring network interfaces...SIOCADDRT: File exists
Failed to bring up venet0.
done.
How can fix?

Since the change does not affect venet0 directly you can probably ignore this.

In principle: after a change in /etc/interface/networks a reboot is obligatory.