OpenVZ Forum: Support » Multiple IP subnets on one VE/HN. Routing problem?

Home » General » Support » Multiple IP subnets on one VE/HN. Routing problem?

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

Multiple IP subnets on one VE/HN. Routing problem? [message #40787]

Tue, 05 October 2010 05:22

piplite
Messages: 27
Registered: March 2008

Junior Member

So here is a problem im facing first time as im moving some of my VE from one datacenters to another. Like i said, i never experienced anything like it with 2 locations. At this 3rd location i have a /26 (96.1.1.0/26) and a /24 (96.1.2.0/24) ip subnets.
HN is running on IP from /26 subnet and i can easily create VE with IPs from the same /26 subnet. Can access and ping them from any place. But /24 gives me a headache.
Some more information:
HN ifconfig:

eth0      Link encap:Ethernet  HWaddr 00:30:48:BF:F0:4A
          inet addr:96.1.1.2  Bcast:96.1.1.63  Mask:255.255.255.192
          inet6 addr: fe80::230:48ff:febf:f04a/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2083138 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1175033 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:2510400640 (2.3 GiB)  TX bytes:270037165 (257.5 MiB)
          Memory:dc100000-dc120000

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:66 errors:0 dropped:0 overruns:0 frame:0
          TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4660 (4.5 KiB)  TX bytes:4660 (4.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:2360 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2056 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:373021 (364.2 KiB)  TX bytes:254909 (248.9 KiB)

HN route -n

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
96.1.2.3        0.0.0.0         255.255.255.255 UH    0      0        0 venet0
96.1.2.201      0.0.0.0         255.255.255.255 UH    0      0        0 venet0
96.1.1.40       0.0.0.0         255.255.255.255 UH    0      0        0 venet0
96.1.1.0        0.0.0.0         255.255.255.192 U     0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
0.0.0.0         96.1.1.1        0.0.0.0         UG    0      0        0 eth0

96.1.1.40 - pingable and easily accessed.
96.1.2.3 and 96.1.2.201 - can not ping outside and from the inside of container.

Route -n info from 96.1.2.3 (problem VE):

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.0.2.1       0.0.0.0         255.255.255.255 UH    0      0        0 venet0
0.0.0.0         192.0.2.1       0.0.0.0         UG    0      0        0 venet0

What would you recommend as my colo provider keep on telling me to use gateway IP to route IPs.
Is this what i need? http://wiki.openvz.org/Source_based_routing

Thanks in advance.

[Updated on: Tue, 05 October 2010 05:25]

Report message to a moderator