We could, but that restricts us if we want to move to VLANs on vport0 in future. In the event that VLANs are passing through vmbr0, I would hope that it doesn't respond to ARP for the VLANs at least.
More than anything, I'm wondering if people have seen similar behaviour. We have our...
A similar issue, but without Openvswitch or Proxmox
https://serverfault.com/questions/206316/linux-bridge-responding-to-arp-on-wrong-interface
Now that I can post links...
The mirror is done using OVS Mirrors.
ovs-vsctl -- set Bridge vmbr0 mirrors=@m \
-- --id=@vm-01 get Port tap102i0 \
-- --id=@vm-02 get Port tap158i0 \
-- --id=@dest get Port eno2 \
-- --id=@m create Mirror name=mirrorport select-src-port=@vm-01,@vm-02 output-port=@dest
ovs-vsctl list...
We may have worked around this, using the following sysctl option
net.ipv4.conf.vmbr0.arp_ignore=2
So far all is good. If this is the case, it would seem prudent for this to be part of the default Proxmox install I would have thought
Hi all,
We appear to be hitting an issue with duplicate ARP entries being generated by multiple Proxmox hosts. These are being generated for the management IP of the hosts.
The running version of each component is listed below: -
pveversion -v
proxmox-ve: 5.4-1 (running kernel...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.