Results 26 to 32 of 32
-
01-21-2014, 04:08 PM #26Mostly Retired!
- Join Date
- Nov 2002
- Location
- Portland, Oregon
- Posts
- 2,992
That could definitely make a difference. Keep us posted if you can.
-
01-21-2014, 05:58 PM #27Newbie
- Join Date
- Jul 2013
- Posts
- 26
Tell me what IP do you have on the host?
Can you ping container from the host? Host from the container? Default gateway (95.211.148.190) from the container?
-
01-22-2014, 01:24 AM #28WHT Addict
- Join Date
- May 2007
- Posts
- 149
Hi, Pinging the container from the main host, it automatically changes to gateway.
Main Host is : 95.211.148.177
Conatainer IP : 95.211.148.160
Code:[root@hosted-by ~]# ping -b 95.211.148.160 WARNING: pinging broadcast address PING 95.211.148.160 (95.211.148.160) 56(84) bytes of data. 64 bytes from 95.211.148.190: icmp_seq=1 ttl=64 time=0.404 ms 64 bytes from 95.211.148.190: icmp_seq=2 ttl=64 time=0.425 ms 64 bytes from 95.211.148.190: icmp_seq=3 ttl=64 time=0.417 ms 64 bytes from 95.211.148.190: icmp_seq=4 ttl=64 time=0.430 ms 64 bytes from 95.211.148.190: icmp_seq=5 ttl=64 time=0.463 ms 64 bytes from 95.211.148.190: icmp_seq=6 ttl=64 time=0.429 ms ç64 bytes from 95.211.148.190: icmp_seq=7 ttl=64 time=0.424 ms 64 bytes from 95.211.148.190: icmp_seq=8 ttl=64 time=0.448 ms --- 95.211.148.160 ping statistics --- 8 packets transmitted, 8 received, 0% packet loss, time 7730ms rtt min/avg/max/mdev = 0.404/0.430/0.463/0.017 ms [root@hosted-by ~]# ping -b 95.211.148.190 PING 95.211.148.190 (95.211.148.190) 56(84) bytes of data. 64 bytes from 95.211.148.190: icmp_seq=1 ttl=64 time=0.679 ms 64 bytes from 95.211.148.190: icmp_seq=2 ttl=64 time=0.438 ms 64 bytes from 95.211.148.190: icmp_seq=3 ttl=64 time=0.428 ms 64 bytes from 95.211.148.190: icmp_seq=4 ttl=64 time=0.442 ms ç64 bytes from 95.211.148.190: icmp_seq=5 ttl=64 time=0.435 ms 64 bytes from 95.211.148.190: icmp_seq=6 ttl=64 time=0.421 ms --- 95.211.148.190 ping statistics --- 6 packets transmitted, 6 received, 0% packet loss, time 5282ms rtt min/avg/max/mdev = 0.421/0.473/0.679/0.096 ms [root@hosted-by ~]# vzctl enter 101 entered into CT 101 [root@ww /]# ping -b 95.211.148.177 PING 95.211.148.177 (95.211.148.177) 56(84) bytes of data. --- 95.211.148.177 ping statistics --- 7 packets transmitted, 0 received, 100% packet loss, time 6011ms [root@ww /]# ping -b 95.211.148.190 PING 95.211.148.190 (95.211.148.190) 56(84) bytes of data. --- 95.211.148.190 ping statistics --- 7 packets transmitted, 0 received, 100% packet loss, time 6420ms [root@ww /]#
-
01-22-2014, 02:10 AM #29Newbie
- Join Date
- Jul 2013
- Posts
- 26
Oh this is easy. Given your network of 95.211.148.160/27, the address 95.211.148.160 is not a host address, but a network address (i.e. the one to address the whole network, and this is why ping tells you to use -b which you d).
Therefore, you CAN NOT use 95.211.148.160 for container. The first address you can use is 95.211.148.161. So, do this:
Code:vzctl set $CTID --ipdel all --ipadd 95.211.148.161/27 --save
As for /27, it is 255.255.255.224, I took it from route -n output you posted before.
-
01-22-2014, 05:37 AM #30WHT Addict
- Join Date
- May 2007
- Posts
- 149
-
01-22-2014, 04:02 PM #31Newbie
- Join Date
- Jul 2013
- Posts
- 26
Given this netmask (/27 aka 255.255.255.224), 95.211.148.160 is network address not a host address. So, either your netmask or that IP is wrong, you should ask your DC about it.
-
01-23-2014, 12:24 AM #32WHT Addict
- Join Date
- May 2007
- Posts
- 149
Similar Threads
-
ULOG on OpenVZ container
By Onur in forum Dedicated ServerReplies: 1Last Post: 03-11-2012, 07:17 PM -
all openvz container down
By CoolMike in forum Hosting Security and TechnologyReplies: 1Last Post: 12-03-2011, 03:25 AM -
About quotas in an OpenVZ container
By Onur in forum Dedicated ServerReplies: 10Last Post: 08-23-2011, 06:49 PM -
change veid of container Openvz
By Hillockhosting in forum Hosting Security and TechnologyReplies: 2Last Post: 08-23-2010, 10:38 AM -
Can't enter OpenVZ container
By Exabytes in forum Dedicated ServerReplies: 6Last Post: 07-14-2010, 12:53 AM