[Users] ARP queris being ignored

2008-04-23 Thread chris
Hi All,

I have been using OpenVZ for a few months now, and I've been having a
problem with VE's running for longer then a few days - the hardware
node ignores ARP queries for VE's that are running on it.  The VE has
IP 192.168.0.105.

When things are working, I see a line from 'arp -a' for the 192.168.0.105
host:
  [EMAIL PROTECTED] ~]# arp -a
  ? (192.168.0.160) at 00:07:E9:5F:BA:60 [ether] on eth0
  ? (192.168.0.253) at 00:1B:2B:2C:C3:4D [ether] on eth0
  ? (192.168.0.105) at * PERM PUP on eth0

When things stop working, the 192.168.0.105 disappears from the output
of 'arp -a'.  An entry for 192.168.0.105 stops appearing in
/proc/net/arp as well.

A tcpdump show the arp query arriving on the hardware node.
  [EMAIL PROTECTED] ~]# tcpdump -nni any arp
  tcpdump: WARNING: Promiscuous mode not supported on the any device
  tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
  listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
  15:30:19.964806 arp who-has 192.168.0.105 tell 192.168.0.253
  15:30:21.973385 arp who-has 192.168.0.105 tell 192.168.0.253
  15:30:23.973453 arp who-has 192.168.0.105 tell 192.168.0.253
  15:30:25.976838 arp who-has 192.168.0.105 tell 192.168.0.253

Further info:
 - VE is running with ip 192.168.0.105
[EMAIL PROTECTED] ~]# vzlist |grep 192.168.0.105
   105125 running 192.168.0.105   zimbra-ose.cgb1911.mine.nu
  

 - Centos 5 with a OpenVZ kernel from the yum repo
[EMAIL PROTECTED] ~]# cat /etc/redhat-release 
CentOS release 5 (Final)
[EMAIL PROTECTED] ~]# uname -a
Linux sonata.cgb1911.mine.nu 2.6.18-53.1.13.el5.028stab053.10 #1 SMP Tue 
Apr 1 14:58:47 MSD 2008 i686 i686 i386 GNU/Linux

Anyone have any idea what is going on?  Is there something further I
can do to debug this?  

Thanks in advance for any responses,

Chris Bennett (cgb)
___
Users mailing list
Users@openvz.org
https://openvz.org/mailman/listinfo/users


Re: [Users] ARP queris being ignored

2008-04-23 Thread Denis V. Lunev
On Wed, 2008-04-23 at 15:37 +0930, [EMAIL PROTECTED] wrote:
 Hi All,
 
 I have been using OpenVZ for a few months now, and I've been having a
 problem with VE's running for longer then a few days - the hardware
 node ignores ARP queries for VE's that are running on it.  The VE has
 IP 192.168.0.105.
 
 When things are working, I see a line from 'arp -a' for the 192.168.0.105
 host:
   [EMAIL PROTECTED] ~]# arp -a
   ? (192.168.0.160) at 00:07:E9:5F:BA:60 [ether] on eth0
   ? (192.168.0.253) at 00:1B:2B:2C:C3:4D [ether] on eth0
   ? (192.168.0.105) at * PERM PUP on eth0
 
 When things stop working, the 192.168.0.105 disappears from the output
 of 'arp -a'.  An entry for 192.168.0.105 stops appearing in
 /proc/net/arp as well.
 
 A tcpdump show the arp query arriving on the hardware node.
   [EMAIL PROTECTED] ~]# tcpdump -nni any arp
   tcpdump: WARNING: Promiscuous mode not supported on the any device
   tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
   listening on any, link-type LINUX_SLL (Linux cooked), capture size 96 bytes
   15:30:19.964806 arp who-has 192.168.0.105 tell 192.168.0.253
   15:30:21.973385 arp who-has 192.168.0.105 tell 192.168.0.253
   15:30:23.973453 arp who-has 192.168.0.105 tell 192.168.0.253
   15:30:25.976838 arp who-has 192.168.0.105 tell 192.168.0.253

you'll have arp replay iff on the _target_ node/VE
ip route get 192.168.0.105 from 192.168.0.253 iif incoming_device
will return either a local route or route to a device other than
incoming.

Regards,
Den

___
Users mailing list
Users@openvz.org
https://openvz.org/mailman/listinfo/users


Re: [Users] ARP queris being ignored

2008-04-23 Thread chris
Hi Den,

Thanks for your reply.

 you'll have arp replay iff on the _target_ node/VE
 ip route get 192.168.0.105 from 192.168.0.253 iif incoming_device
 will return either a local route or route to a device other than
 incoming.
 
I don't really get you on this, are you able to elaborate?

Also, if it helps, here's the output of command you suggested above:

Working:
  [EMAIL PROTECTED] ~]# ip route get 192.168.0.105
  192.168.0.105 dev venet0  src 192.168.0.224 
  cache  mtu 1500 advmss 1460 hoplimit 64

Not working:
  [EMAIL PROTECTED] ~]# ip route get 192.168.0.105
  192.168.0.105 dev venet0  src 192.168.0.224 
  cache  mtu 1500 advmss 1460 hoplimit 64

That is, they are exactly the same.

Regards,

Chris Bennett (cgb)
___
Users mailing list
Users@openvz.org
https://openvz.org/mailman/listinfo/users


Re: [Users] ARP queris being ignored

2008-04-23 Thread Denis V. Lunev
On Wed, 2008-04-23 at 22:48 +0930, [EMAIL PROTECTED] wrote:
 Hi Den,
 
 Thanks for your reply.
 
  you'll have arp replay iff on the _target_ node/VE
  ip route get 192.168.0.105 from 192.168.0.253 iif incoming_device
  will return either a local route or route to a device other than
  incoming.
  
 I don't really get you on this, are you able to elaborate?
 
 Also, if it helps, here's the output of command you suggested above:
 
 Working:
   [EMAIL PROTECTED] ~]# ip route get 192.168.0.105
   192.168.0.105 dev venet0  src 192.168.0.224 
   cache  mtu 1500 advmss 1460 hoplimit 64
 
 Not working:
   [EMAIL PROTECTED] ~]# ip route get 192.168.0.105
   192.168.0.105 dev venet0  src 192.168.0.224 
   cache  mtu 1500 advmss 1460 hoplimit 64

You are using a wrong command. If you are using venet0 you should
execute the command _exactly_ in the form I ask, with from and iif,
in VE0.

There should be a difference.

Regards,
Den

___
Users mailing list
Users@openvz.org
https://openvz.org/mailman/listinfo/users


Re: [Users] ARP queris being ignored

2008-04-23 Thread chris
Hi Again,

 You are using a wrong command. If you are using venet0 you should
 execute the command _exactly_ in the form I ask, with from and iif,
 in VE0.

Ok, I understand you on this now..   I wasn't cloear on what is the
incoming_device, (eth0 or venet0) so I provided both:

eth0 working:
  [EMAIL PROTECTED] ~]# ip route get 192.168.0.105 from 192.168.0.253/24 iif 
eth0
  192.168.0.105 from 192.168.0.253 dev venet0  src 192.168.0.224 
  cache src-direct  mtu 1500 advmss 1460 hoplimit 64 iif eth0

eth0 not working:
  [EMAIL PROTECTED] ~]# ip route get 192.168.0.105 from 192.168.0.253/24 iif 
eth0
  192.168.0.105 from 192.168.0.253 dev venet0  src 192.168.0.224 
  cache src-direct  mtu 1500 advmss 1460 hoplimit 64 iif eth0


venet0 working:
  [EMAIL PROTECTED] ~]# ip route get 192.168.0.105 from 192.168.0.253/24 iif 
venet0
  192.168.0.105 from 192.168.0.253 dev venet0  src 192.168.0.224 
  cache  mtu 1500 advmss 1460 hoplimit 64 iif venet0

venet0 not working:
  [EMAIL PROTECTED] ~]# ip route get 192.168.0.105 from 192.168.0.253/24 iif 
venet0
  192.168.0.105 from 192.168.0.253 dev venet0  src 192.168.0.224 
  cache  mtu 1500 advmss 1460 hoplimit 64 iif venet0

 There should be a difference.

In both cases, they are the same.  I don't think I mentioned it in the
first email - restarting the VE fixes the problem.

Is there anything else you can suggest I try?

Regards,

Chris Bennett (cgb)
___
Users mailing list
Users@openvz.org
https://openvz.org/mailman/listinfo/users