OpenVZ Forum


Home » General » Support » CT Ip address aims to Node IP address (Can't get an IP forwared to the CT)
CT Ip address aims to Node IP address [message #50480] Sun, 01 September 2013 17:00 Go to next message
aetchegoyen is currently offline  aetchegoyen
Messages: 2
Registered: September 2013
Location: Argentina
Junior Member

Hi! I've just done a clean CentOS 6.4 install on an iWeb dedicated server and installed OpenVZ and OpenVZ Control Panel.

I created a CT and assigned it an IP, and nameserver, but when I try to ssh that IP it sends me to the Host node instead of the CT (I know that because with the CT root password it says access denied, but with the node password it enters fine for example)

What can I do? I've followed these guides:
openvz dot org/Quick_installation
howtoforge dot com/installing-and-using-openvz-on-centos-6.4

I have 5 IPs in the host machine

Here's the output for "ifconfig" (last ip number masked by me)
Quote:

eth0 Link encap:Ethernet HWaddr 00:1E:67:8B:F1:3B
inet addr:67.205.85.xxx Bcast:67.205.85.xxx Mask:255.255.255.224
inet6 addr: fe80::21e:67ff:fe8b:f13b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:18956 errors:0 dropped:0 overruns:0 frame:0
TX packets:3706 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1982661 (1.8 MiB) TX bytes:638942 (623.9 KiB)
Interrupt:19 Memory:c1b00000-c1b20000

eth0:0 Link encap:Ethernet HWaddr 00:1E:67:8B:F1:3B
inet addr:184.107.74.xx0 Bcast:184.107.74.xx0 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:19 Memory:c1b00000-c1b20000

eth0:1 Link encap:Ethernet HWaddr 00:1E:67:8B:F1:3B
inet addr:184.107.74.xx1 Bcast:184.107.74.xx1 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:19 Memory:c1b00000-c1b20000

eth0:2 Link encap:Ethernet HWaddr 00:1E:67:8B:F1:3B
inet addr:184.107.74.xx2 Bcast:184.107.74.xx2 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:19 Memory:c1b00000-c1b20000

eth0:3 Link encap:Ethernet HWaddr 00:1E:67:8B:F1:3B
inet addr:184.107.74.xx3 Bcast:184.107.74.xx3 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:19 Memory:c1b00000-c1b20000

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:25680 errors:0 dropped:0 overruns:0 frame:0
TX packets:25680 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3822835 (3.6 MiB) TX bytes:3822835 (3.6 MiB)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::1/128 Scope:Link
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

veth102.0 Link encap:Ethernet HWaddr 00:18:51:46:86:EF
inet6 addr: fe80::218:51ff:fe46:86ef/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:4 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


Here's the output for "ip route list table all"
Quote:

184.107.74.xx0 dev venet0 scope link
67.205.85.xx8/27 dev eth0 proto kernel scope link src 67.205.85.xx3
169.254.0.0/16 dev eth0 scope link metric 1002
default via 67.205.85.xx9 dev eth0
broadcast 67.205.85.xx9 dev eth0 table local proto kernel scope link src 67.205.85.xx3
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
local 184.107.74.103 dev eth0 table local proto kernel scope host src 184.107.74.xx3
broadcast 184.107.74.xx3 dev eth0 table local proto kernel scope link src 184.107.74.xx3
local 184.107.74.xx2 dev eth0 table local proto kernel scope host src 184.107.74.xx2
broadcast 184.107.74.xx2 dev eth0 table local proto kernel scope link src 184.107.74.xx2
local 184.107.74.xx1 dev eth0 table local proto kernel scope host src 184.107.74.xx1
broadcast 184.107.74.xx1 dev eth0 table local proto kernel scope link src 184.107.74.xx1
local 67.205.85.xx3 dev eth0 table local proto kernel scope host src 67.205.85.xx3
local 184.107.74.xx0 dev eth0 table local proto kernel scope host src 184.107.74.xx0
broadcast 184.107.74.xx0 dev eth0 table local proto kernel scope link src 184.107.74.xx0
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
broadcast 67.205.85.128 dev eth0 table local proto kernel scope link src 67.205.85.xx3
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
unreachable ::/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:a00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:7f00::/24 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:a9fe::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:ac10::/28 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:c0a8::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:e000::/19 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 3ffe:ffff::/32 dev lo metric 1024 error -101 mtu 16436 advmss 16376 hoplimit 4294967295
fe80::1 dev venet0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev venet0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev veth102.0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo table unspec proto kernel metric -1 error -101 hoplimit 255
local ::1 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80:: via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80:: via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::1 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::218:51ff:fe46:86ef via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::21e:67ff:fe8b:f13b via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
ff00::/8 dev eth0 table local metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev venet0 table local metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev veth102.0 table local metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo table unspec proto kernel metric -1 error -101 hoplimit 255


Here's the output for "iptables -t nat -L && iptables -t filter -L && iptables -t mangle -L"
Quote:

L
Chain PREROUTING (policy ACCEPT)
target prot opt source destination

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
Chain PREROUTING (policy ACCEPT)
target prot opt source destination

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

Chain POSTROUTING (policy ACCEPT)
target prot opt source destination


Re: CT Ip address aims to Node IP address [message #50481 is a reply to message #50480] Mon, 02 September 2013 06:01 Go to previous messageGo to next message
Ales is currently offline  Ales
Messages: 330
Registered: May 2009
Senior Member
I see you have IPs on two different subnets?

Start by detaching all IPs you plan to use for VMs from eth0, except for eth0:0 (for now).

So, you should have no eth0:1, eth0:2, eth0:3. Then simply assign the IP that used to be eth0:1 to your VM and it will work.

In the mean time, search for cases of having IPs from different subnets and go from there - you'll understand why I advised you to keep eth0:0 for now.
icon7.gif  Re: CT Ip address aims to Node IP address [message #50558 is a reply to message #50481] Tue, 10 September 2013 16:40 Go to previous message
aetchegoyen is currently offline  aetchegoyen
Messages: 2
Registered: September 2013
Location: Argentina
Junior Member

Thanks!! Detaching the IP adresses from eth0 worked perfectly!
Previous Topic: Rebasing to 3.10 question
Next Topic: Openvz on HP PROLIANT DL360 G3?
Goto Forum:
  


Current Time: Sat Mar 02 12:28:47 GMT 2024

Total time taken to generate the page: 0.03373 seconds