OpenVZ Forum


Home » General » Support » Assigning IPs (IPs are never public Facing)
Assigning IPs [message #40650] Sat, 11 September 2010 22:04
PsyberMind is currently offline  PsyberMind
Messages: 1
Registered: September 2010
Junior Member
I have a rather serious issue, and I'm not sure how to fix this one

I have a server, with a /27 the problem is, They all seem to be tied to the HN.

I can assign an IP to the container with no problem. I can enter the container, I can PING the IP from within the HN.

When I ssh into the container, my root PW will NOT work. The only way it will work is if I use the root pw for the HN. It's like every IP I have is tied to the HN, and I can't for the life of me figure out why.

I've asked the DC to move the IPs into the vLan, but they are telling me they don't support OpenVZ in any way shape or form, so I'm on my own.

Until I can get this figured out, I am at a standstill


[root@ord-1 ~]# ip r l
unreachable 255.255.255.255
173.236.95.192/28 dev eth0 proto kernel scope link src 173.236.95.194
184.154.11.224/27 dev venet0 proto kernel scope link src 184.154.11.226
unreachable 224.0.0.0/24
184.154.0.0/16 dev venet0 proto kernel scope link src 184.154.11.226
169.254.0.0/16 dev eth0 scope link
default via 173.236.95.193 dev eth0
[root@ord-1 ~]# vzctl enter
CT ID missing
[root@ord-1 ~]# vzctl enter 200
entered into CT 200
[root@vpsctl /]# ip r l
192.0.2.0/24 dev venet0 scope host
169.254.0.0/16 dev venet0 scope link
default via 192.0.2.1 dev venet0
[root@vpsctl /]#


[root@ord-1 ~]# ifconfig;route -n;vzlist -a
eth0 Link encap:Ethernet HWaddr 00:30:48:FC:B4:18
inet addr:173.236.95.194 Bcast:173.236.95.207 Mask:255.255.255.240
inet6 addr: fe80::230:48ff:fefc:b418/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:192074 errors:0 dropped:0 overruns:0 frame:0
TX packets:112012 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:257858784 (245.9 MiB) TX bytes:10188969 (9.7 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:702 errors:0 dropped:0 overruns:0 frame:0
TX packets:702 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:78588 (76.7 KiB) TX bytes:78588 (76.7 KiB)

venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:184.154.11.226 P-t-P:184.154.11.226 Bcast:184.154.255.255 Mask:255.255.0.0
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:166 errors:0 dropped:0 overruns:0 frame:0
TX packets:242 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:19246 (18.7 KiB) TX bytes:19680 (19.2 KiB)

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
255.255.255.255 - 255.255.255.255 !H 0 - 0 -
173.236.95.192 0.0.0.0 255.255.255.240 U 0 0 0 eth0
184.154.11.224 0.0.0.0 255.255.255.224 U 0 0 0 venet0
224.0.0.0 - 255.255.255.0 ! 0 - 0 -
184.154.0.0 0.0.0.0 255.255.0.0 U 0 0 0 venet0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 173.236.95.193 0.0.0.0 UG 0 0 0 eth0
CTID NPROC STATUS IP_ADDR HOSTNAME
200 16 running 184.154.11.226 vpsctl.xxxxxxx.org
[root@ord-1 ~]#

[Updated on: Sat, 11 September 2010 22:56]

Report message to a moderator

Previous Topic: NAT issue
Next Topic: iptables-modules inside ve?!?!? (statistic and marking)
Goto Forum:
  


Current Time: Fri Aug 16 18:19:21 GMT 2024

Total time taken to generate the page: 0.02954 seconds