OpenVZ Forum: Support » ARP problem on openvz venet.

Home » General » Support » ARP problem on openvz venet.

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

ARP problem on openvz venet. [message #35611]

Wed, 08 April 2009 13:26

pug123
Messages: 22
Registered: July 2008

Junior Member

Hello,

Some of our ips stopped working becouse datacenter changed network equipment and advised us that the problem is becouse venet device has NOARP and it should send ARP. Is it true? Does it mean we should enable proxy arp?

Please clarify these things as I'd like to know how it is working with NOARP. How IP becomes visible then?

Thank you in advance

Report message to a moderator

Re: ARP problem on openvz venet. [message #35633 is a reply to message #35611]

Thu, 09 April 2009 16:50

maratrus
Messages: 1495
Registered: August 2007
Location: Moscow

Senior Member

Hi,

Quote:

and advised us that the problem is becouse venet device has NOARP and it should send ARP. Is it true?

No, it's not.

Quote:

Does it mean we should enable proxy arp?

It's not required in case of venet.

Quote:

Please clarify these things as I'd like to know how it is working with NOARP. How IP becomes visible then?

Assigning ip address in case of venet contains of three phases:
- assigning ip address inside VE on venet0 interface
- adding route on the HN (ip r l - to show routes)
- adding information about VE into arp table (arp -n - to show the table)

Every time an arp-request (which contains VEs ip address) comes to HN from physical interface, HN determines that the packet should proceed to VE through venet0 interface and that's why HN is ready to send arp-reply, and the packet is really sent because of the information in the arp-table on the HN.

Report message to a moderator

Previous Topic:	SOLVED openvz and trixbox
Next Topic:	How to add entry in /vz/root/

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Jul 14 16:53:42 GMT 2024

Total time taken to generate the page: 0.02605 seconds