OpenVZ Forum: Support » *SOLVED* Static ARP setting in VM

Home » General » Support » *SOLVED* Static ARP setting in VM

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

*SOLVED* Static ARP setting in VM [message #13209]

Wed, 23 May 2007 12:27

HRogge
Messages: 16
Registered: April 2007

Junior Member

I'm trying to set a fixed ARP cache entry inside a VM, but I always get an error.

vn101:/# arp -s 10.0.0.101 00:11:22:33:44:55
SIOCSARP: Operation not permitted

[Updated on: Fri, 25 May 2007 10:41] by Moderator

Report message to a moderator

Re: Static ARP setting in VM [message #13211 is a reply to message #13209]

Wed, 23 May 2007 12:37

kir
Messages: 1645
Registered: August 2005
Location: Moscow, Russia

Senior Member

In case you are using venet networking for a VE (venet is default), host system acts as a router, and VE has a macless venet device -- so there is no arp and you can not add arp entries.

I'm not sure what you try to achieve, but you can either add arp entry on the host system, or try using veth (see http://wiki.openvz.org/Veth), which is brigded (as opposed to routed) networking for a VE with a mac address.

Last way is to use real ethernet device (vzctl set --netdev_add)

Kir Kolyshkin

http://static.openvz.org/userbars/openvz-developer.png

Report message to a moderator

Re: Static ARP setting in VM [message #13221 is a reply to message #13209]

Wed, 23 May 2007 12:54

HRogge
Messages: 16
Registered: April 2007

Junior Member

I think this should be the relevant part of my /etc/vz/conf/101.conf:

NETIF="ifname=eth0,mac=00:00:00:00:02:01,host_ifname=veth101.0,host_mac=00:00:00
:00:01:01;ifname=eth1,mac=00:00:00:00:04:01,host_ifname=veth101.1,host_mac=00:00
:00:00:03:01"

I would like to achive that the VM does not have to ask for the MAC address of it's communication partner by an ARP packet (there is a fixed number of MACs/IPs).

Report message to a moderator

Re: Static ARP setting in VM [message #13372 is a reply to message #13221]

Fri, 25 May 2007 10:40

Vasily Tarasov
Messages: 1345
Registered: January 2006

Senior Member

Hello,

Thank you for the report, I attach the path that fixes your problem. It probably will be included in next OVZ kernel release.

Thanks,
Vasily.