OpenVZ Forum


Home » General » Support » why i can't ping vps from the host? (why i can't ping vps from the host?)
why i can't ping vps from the host? [message #40339] Thu, 12 August 2010 07:14 Go to next message
greenflying2010 is currently offline  greenflying2010
Messages: 4
Registered: August 2010
Junior Member
I create a vps on openvz. This vps has two network interfaces, one is venet0 ,venet0:0 and the other is eth0. The ipaddr of venet0:0 is 192.168.255.2, and the eth0 ipaddr is 10.202.0.242. The ipaddr of the openvz host is 192.168.255.254. From the host, i can ping the venet0:0 192.168.255.2, but why i can't ping the eth0 of vps 10.202.0.242????
I have start the ipv4 forwarding in vps and closed the firewall.
when i try the following command:
ping -I venet0 10.202.0.242
it appears an error like: ping: sendmsg: operation not permitted.
What's the problem??

thanks
b.guo
Re: why i can't ping vps from the host? [message #40343 is a reply to message #40339] Fri, 13 August 2010 11:35 Go to previous messageGo to next message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Most probably, there is something wrong with the routes.
Try to find out where the packet goes from the HN
("ip r l" should help you to answer this question).
I suppose the packet goes outside the HN and it is
dropped on the nearest switch. The problem is that
10.202.0.242 belongs to subnet that differs from
192.168.255.2.
Re: why i can't ping vps from the host? [message #40432 is a reply to message #40343] Wed, 18 August 2010 01:52 Go to previous message
greenflying2010 is currently offline  greenflying2010
Messages: 4
Registered: August 2010
Junior Member
Thanks for you reply!
I have set the default gateway of HN to be 192.168.255.2, when i ping 10.202.0.242, the icmp request packets must be send to 192.168.255.2. I have set the ve's ipv4 routing, but why i can't ping 10.202.0.242?? The icmp request isn't sent to 10.202.0.242. Even in ve i can't get icmp request packets at the network interface venet0 using tcpdump. I know 10.202.0.242 belongs to subnet that differs from 192.168.255.2. But, it is easy to achieve using vmware in this case.
The matter most unblievable is that i can get icmp request packets (to 10.202.0.242) in HN but i can't get in ve using tcpdump. So i wonder if there are some problems about the gw 192.0.2.1 set by openvz??
Previous Topic: OpenVZ Crashing
Next Topic: VE cann't start after system upgrade
Goto Forum:
  


Current Time: Thu Dec 12 21:35:30 GMT 2024

Total time taken to generate the page: 0.02695 seconds