OpenVZ Forum: Support » IP pooling on new dedicated server

Home » General » Support » IP pooling on new dedicated server

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

IP pooling on new dedicated server [message #40834]

Fri, 08 October 2010 21:39

lucianors
Messages: 1
Registered: October 2010
Location: Brazil

Junior Member

Hello guys.

I am so sorry if this is a recurrent topic.

I bought a new Debian dedicated server and i received 5 real ip addresses:

66.198.237.165-169

netmask 255.255.255.248
broadcast 66.198.237.175
network 66.198.237.160
gateway 66.198.237.161

I am running a openvz enabled kernel, and i got the proper tools installed and have setted the sysctl.conf variables.

this is the host's ifconfig output

eth0      Link encap:Ethernet  HWaddr 00:27:0e:01:db:e1
          inet addr:66.198.237.165  Bcast:66.198.237.175  Mask:255.255.255.248
          inet6 addr: fe80::227:eff:fe02:dbe1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:244980 errors:0 dropped:0 overruns:0 frame:0
          TX packets:244481 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:19434946 (18.5 MiB)  TX bytes:19933167 (19.0 MiB)
          Memory:d0600000-d0620000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:324 errors:0 dropped:0 overruns:0 frame:0
          TX packets:324 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:43617 (42.5 KiB)  TX bytes:43617 (42.5 KiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:44664 errors:0 dropped:0 overruns:0 frame:0
          TX packets:41445 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:8111594 (7.7 MiB)  TX bytes:5382169 (5.1 MiB)

I want to allocate the other ips (66.198.237.166-169) to vz machines. I created two VZ containers using OpenVz Web Panel.
I configured each of then with the same network config of the host (gateway, broadcast, ...).

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00                                                             -00
          inet addr:127.0.0.1  P-t-P:127.0.0.1  Bcast:0.0.0.0  Mask:255.255.255.                                                             255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:5713 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5977 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

venet0:0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00                                                             -00
          inet addr:66.198.237.167  P-t-P:66.198.237.167  Bcast:66.198.237.175                                                               Mask:255.255.255.248
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1

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 66.198.237.167
        netmask 255.255.255.248
        broadcast 66.198.237.175
        network 66.198.237.160
        gateway 66.198.237.161

The problem is that this configuration is very unstable so far. At first, when i created the vz containers i couldn't ping the assignated ip from outside, then i have to reboot the container twice to get it working. I keep loosing them times to times. They get lost when i reboot the host machine too.

I would appreciate any help.

Thank you

Report message to a moderator