OpenVZ Forum


Home » General » Support » VE IP address stops working after several hours
Re: VE IP address stops working after several hours [message #33027 is a reply to message #33024] Thu, 18 September 2008 10:05 Go to previous messageGo to previous message
fatbrother
Messages: 12
Registered: September 2008
Location: Novosibirsk, Russia
Junior Member
maratrus wrote on Thu, 18 September 2008 15:32

Hello,
it's a strange situation.

Cool
maratrus

Could you possibly show a little bit more information.

1. # ip rule list

0: from all lookup 255
32764: from real_ip_network/28 lookup Real
32765: from real_ip1 lookup Real
32766: from all lookup main
32767: from all lookup default
maratrus

2. # ip route list table all

default via real_ip_router dev eth0.425 table Real
real_ip2 dev venet0 scope link
10.4.0.106 dev venet0 scope link
10.4.0.104 dev venet0 scope link
10.4.0.105 dev venet0 scope link
10.4.0.102 dev venet0 scope link
10.4.0.103 dev venet0 scope link
10.4.0.101 dev venet0 scope link
real_network/28 dev eth0.425 proto kernel scope link src real_ip1
10.4.0.96/27 dev eth0 proto kernel scope link src 10.4.0.97
default via 10.4.0.126 dev eth0
broadcast real_ip_network dev eth0.425 table 255 proto kernel scope link src real_ip1
broadcast 10.4.0.127 dev eth0 table 255 proto kernel scope link src 10.4.0.97
broadcast 127.255.255.255 dev lo table 255 proto kernel scope link src 127.0.0.1
local real_ip1 dev eth0.425 table 255 proto kernel scope host src real_ip1
broadcast real_broadcast dev eth0.425 table 255 proto kernel scope link src real_ip1
broadcast 10.4.0.96 dev eth0 table 255 proto kernel scope link src 10.4.0.97
broadcast 127.0.0.0 dev lo table 255 proto kernel scope link src 127.0.0.1
local 10.4.0.97 dev eth0 table 255 proto kernel scope host src 10.4.0.97
local 127.0.0.1 dev lo table 255 proto kernel scope host src 127.0.0.1
local 127.0.0.0/8 dev lo table 255 proto kernel scope host src 127.0.0.1
(IPv6 stuff skipped)
unreachable default dev lo proto none metric -1 error -101 hoplimit 255
maratrus

3. # sysctl -a | grep arp_filter

error: "Operation not permitted" reading key "net.ipv6.route.flush"
net.ipv4.conf.venet0.arp_filter = 0
net.ipv4.conf.eth0/425.arp_filter = 0
net.ipv4.conf.eth0.arp_filter = 0
net.ipv4.conf.lo.arp_filter = 0
net.ipv4.conf.default.arp_filter = 0
net.ipv4.conf.all.arp_filter = 0
error: "Operation not permitted" reading key "net.ipv4.route.flush"
maratrus

4. # sysctl -a | grep proxy_arp

error: "Operation not permitted" reading key "net.ipv6.route.flush"
net.ipv4.conf.venet0.proxy_arp = 0
net.ipv4.conf.eth0/425.proxy_arp = 0
net.ipv4.conf.eth0.proxy_arp = 0
net.ipv4.conf.lo.proxy_arp = 0
net.ipv4.conf.default.proxy_arp = 0
net.ipv4.conf.all.proxy_arp = 0
error: "Operation not permitted" reading key "net.ipv4.route.flush"
maratrus

And does the following helps:
# ip neigh del proxy real_ip2 dev eth0.425
# ip neigh add proxy real_ip2 dev eth0.425
?


I'll try it next time it fails again.

maratrus

Does "arp -n" output differs before and after the real_ip2 is broken down? (I mean only that records that concerns with VE ip addresses).

No. That's most confusing. I tried manipulating real_ip2 record via arp -i eth0.425 ... pub, but that does not seem to work.

Today it failed three times: at 06:20, at 10:31 and between 14:22 and 14:55 (i wrote a script that pings the real_ip2 every 100 secunds and does vzctl set --ipdel, vzctl set --ipadd when ping fails). Looks like it fails every 4 hours 11 minutes +-100 seconds (however I need several more datapoints to tell for sure). Does this time interval mean something to you?
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Can't start networking on a fedora-9-i386-default-20080913 VE
Next Topic: Creation of VE private area failed
Goto Forum:
  


Current Time: Sun Sep 07 00:19:11 GMT 2025

Total time taken to generate the page: 0.19799 seconds