OpenVZ Forum


Home » General » Support » can only ping locally - not network
Re: can only ping locally - not network [message #32080 is a reply to message #32069] Fri, 18 July 2008 18:09 Go to previous message
john32 is currently offline  john32
Messages: 8
Registered: July 2008
Junior Member
ip rule list
0:	from all lookup local 
32766:	from all lookup main 
32767:	from all lookup default 


ip route list table all
XXX.XXX.XXX.132 dev venet0  scope link 
XXX.XXX.XXX.131 dev venet0  scope link 
XXX.XXX.XXX.130 dev venet0  scope link 
XXX.XXX.XXX.64/26 dev eth3  proto kernel  scope link  src XXX.XXX.XXX.94 
XXX.XXX.XXX.128/26 dev eth3  proto kernel  scope link  src XXX.XXX.XXX.131 
default via XXX.XXX.XXX.65 dev eth3  src XXX.XXX.XXX.130 
default via XXX.XXX.XXX.65 dev eth3  src XXX.XXX.XXX.131 
default via XXX.XXX.XXX.65 dev eth3 
broadcast 127.255.255.255 dev lo  table local  proto kernel  scope link  src 127.0.0.1 
broadcast XXX.XXX.XXX.64 dev eth3  table local  proto kernel  scope link  src XXX.XXX.XXX.94 
local XXX.XXX.XXX.131 dev eth3  table local  proto kernel  scope host  src XXX.XXX.XXX.131 
local XXX.XXX.XXX.130 dev eth3  table local  proto kernel  scope host  src XXX.XXX.XXX.131 
broadcast XXX.XXX.XXX.255 dev eth3  table local  proto kernel  scope link  src XXX.XXX.XXX.94 
broadcast XXX.XXX.XXX.255 dev eth3  table local  proto kernel  scope link  src XXX.XXX.XXX.131 
broadcast XXX.XXX.XXX.127 dev eth3  table local  proto kernel  scope link  src XXX.XXX.XXX.94 
local XXX.XXX.XXX.94 dev eth3  table local  proto kernel  scope host  src XXX.XXX.XXX.94 
broadcast 127.0.0.0 dev lo  table local  proto kernel  scope link  src 127.0.0.1 
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 
local ::1 via :: dev lo  proto none  metric 0  mtu 16436 rtt 9ms rttvar 15ms cwnd 99 advmss 16376 hoplimit 4294967295
local fe80::218:f3ff:feb6:3509 via :: dev lo  proto none  metric 0  mtu 16436 advmss 16376 hoplimit 4294967295
fe80::/64 dev eth3  metric 256  expires 2017154sec mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev eth3  metric 256  expires 2017154sec mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo  proto none  metric -1  error -101 hoplimit 255


132 is the only real VE on that list currently - 130 and 131 are added in the interfaces file on the HN as secondary IPs for eth3.

Also I got a warning (which I've never seen before) when I restarted 132 that proxy_arp was set to 0, so I set all instances of proxy_arp to 1 but that had no effect.

EDIT: somehow since posting on here the ip_forward got turned off (maybe the kernel upgrade you suggested changed my sysctl.conf?)

anyway, after adding these lines to sysctl.conf and rebooting, the VEs work again. Thanks for your help.
net.ipv4.ip_forward=1
net.ipv4.conf.default.proxy_arp=1
net.ipv4.conf.all.proxy_arp=1

[Updated on: Sat, 19 July 2008 06:42]

Report message to a moderator

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Sources for the Debian Packages
Next Topic: openvz and openafs
Goto Forum:
  


Current Time: Fri Nov 08 07:34:53 GMT 2024

Total time taken to generate the page: 0.03422 seconds