[SOLVED] BUG: ARP not being assigned for 2nd /29 subnets on the same gateway.

xcooling

New Member
May 24, 2012
28
0
1
www.eXtremeSHOK.com
2 subnets with the same gateway ( 45.67.66.1)

ranges 45.67.66.0/29 AND 45.67.66.8/29

45.67.66.6 and 45.67.66.5 are both able to ping yahoo.com, be accessed via the internet and can be pinged.

45.67.66.12, 45.67.66.13, 45.67.66.14 can not ping yahoo, can not be accessed via the internet and can not be pinged.

OpenVz containers with venet. (containers: various (debian, centos, turnkey) all affected).

Code:
root@prox:~# vzlist -o uptime,ctid,status,ip
UPTIME CTID STATUS IP_ADDR
000d00h:00m:35s 112 running 45.67.66.14
000d01h:04m:11s 113 running 45.67.66.13 45.67.66.5 45.67.66.12
000d01h:04m:10s 114 running 45.67.66.6

Code:
root@prox:~# arp
Address HWtype HWaddress Flags Mask Iface
45.67.66.1 ether 00:0b:fc:7a:44:ca C vmbr0
45.67.66.6 * <from_interface> MP vmbr0
45.67.66.5 * <from_interface> MP vmbr0

-----------------

if I manually create the ARP request, the container can ping yahoo, access the internet and aswell as be pinged.

Code:
root@prox:~# arp -i vmbr0 -Ds 45.67.66.12 vmbr0 pub
root@prox:~# arp -i vmbr0 -Ds 45.67.66.13 vmbr0 pub
root@prox:~# arp -i vmbr0 -Ds 45.67.66.14 vmbr0 pub

Code:
root@prox:~# arp
Address                  HWtype  HWaddress           Flags Mask            Iface
45.67.66.1              ether   00:0b:fc:7a:44:ca   C                     vmbr0
45.67.66.6              *       <from_interface>    MP                    vmbr0
45.67.66.5              *       <from_interface>    MP                    vmbr0
45.67.66.12             *       <from_interface>    MP                    vmbr0
45.67.66.13             *       <from_interface>    MP                    vmbr0
45.67.66.14             *       <from_interface>    MP                    vmbr0

-----------------

It would appear that the openvz host is not creating/assigning the arp requests correctly for the venets'

-----------------

Makes no difference if we restart the host, containers, networking.
 
Last edited:
Fixed:

The following is important if the IP addresses of your virtual machines are from a different subnet than the host system's IP address. If you don't do this, networking will not work in the virtual machines!

Edit /etc/vz/vz.conf

Code:
NEIGHBOUR_DEVS=detect
-->
Code:
NEIGHBOUR_DEVS=all

Even though there is only 1 interface.

Afterwards reboot the machine.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!