Bridge fills with MAC of physical NIC

J

JohnC

New Member
Dec 2, 2017
2
0
1
54
HP server with a 4 port Broadcom Limited NetXtreme BCM5719 [14e4:1657]

I had a problem on a new install of proxmox, couldn't push any traffic to/from any VM's:
no DHCP
no reaching out, in

verified firewall was off, no iptables rules
ran tcpdump on the bridge and saw nothing

At this point, I figured that it was a relatively new install with some configuration changes made, so I clean installed it, reconfigured and had the same problem. Checked the (3) bridges and they were full of the NICs MACs that were joined to the bridges. I reinstalled and did:

Proxmox 5.1-35 - clean install (left the stock vmbr0 with eno1, with IP set on the bridge (from installer))

logged into web interface and:
add 10.1.1.3/24 to eno4
add vmbr1 with port interface eno2 (no IP on either)
reboot

log into web interface, shell and:
check bridge macs:
brctl showmacs vmbr0 -> looks fine
brctl showmacs vmbr1 -> mac table filled with over 4000 entries of same mac (that of eno2)
NO other configuration changes were made

Am I missing something here?

FYI:
pveversion -v

proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-35 (running version: 5.1-35/722cc488)
pve-kernel-4.13.4-1-pve: 4.13.4-25
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90
 
UPDATE:


After boot, I pulled the physical interface from the bridge and added it back. Without a reboot, it seemed to stop the behavior from happening. I assume (hope) it will stay that way. I would not call this solved, but this is a workaround:

in /etc/init.d/

created file: bridgefix:

#!/bin/sh

### BEGIN INIT INFO
# Provides: bridgefix
# Required-Start: $remote_fs $network
# Required-Stop: $remote_fs $network
# Default-Start: 2 3 4 5
# Default-Stop: 0 1 6
# Short-Description: remove and add interfaces to bridge
### END INIT INFO

#This script removes and adds the physical interfaces to the bridges to prevent excessive
#mac duplication
DESC="Refresh the bridge(s)"
echo "Refreshing bridge..."

brctl delif vmbr1 eno2
sleep 1
brctl addif vmbr1 eno2
touch /root/bridge_refresh


made it executable, added it to start:
chmod +x bridgefix
update-rc.d bridgefix defaults

rebooted and :)
 
Hi

I just detected the same issue but without Traffic issues.
Code: 
root@proxmox4:~# brctl showmacs vmbr0 | wc -l
4151
all of them are local HW Mac's

I tough it was a loop, LACP or QinQ config issue but it also appears in a minimum setup on two different machines.

a)pve-manager/4.4-18/ef2610e8 (running kernel: 4.4.83-1-pve)
Code: 
iface bond0 inet manual
    slaves eth0 eth1
    bond_mode 802.3ad
    bond_miimon 100
    bond-lacp-rate 1
    mtu 9000

iface vmbr0 inet manual
    bridge_ports bond0
    bridge_stp off
    bridge_fd 0
    bridge_vlan_aware yes



b) pve-manager/5.1-36/131401db (running kernel: 4.13.4-1-pve)
Code: 
iface vmbr666 inet6 static
    address  2a00:xxx
    netmask  64
    gateway  2a00:xxx
    bridge_ports enp2s0f0.666
    bridge_stp on
    bridge_fd 0

auto vmbr0
iface vmbr0 inet manual
    bridge_ports enp2s0f0
    bridge_stp on
    bridge_fd 0
    bridge_vlan_aware yes


both have a intel 82599ES Chip with ixgbe Driver.

Code: 
brctl delif vmbr0 enp2s0f0; brctl addif vmbr0 enp2s0f0
is a good workaround. I hope it doesn't appear again after a while...

Bug?
 
You must log in or register to reply here.
Top Bottom