Received packet with own address

I just installed an i350 t4 with all 4 ports connected to a crappy little switch (tl-sg105e) in a loadbalance lagg as the switch doesn’t support lacp. Everything works fine but as soon as I try to add a bridge to it using the lagg as the only member my console immediately starts getting spammed with

br0: received packet on bond0 with own address as source address (addr:[mac])

messages. I read that this happens when bridge members have an ip so I got rid of the one on the bond but I still get the message, I even went so far as to completely disable ipv6 using

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1

as both the bridge and the bond kept auto assigning themselves v6 addresses even with both v4 and v6 dhcp off. Even still I kept getting these messages, I even got rid of the v4 ip on the bridge so there are 0 addresses on the whole system and reset the server and router in case there was some table that needed to be cleared, yet STILL it keeps happening. I’m not entirely sure what I’m doing wrong and/or what’s going wrong here.

Is the switch at the far end configured for a LAGG of these 4 ports?

Do the LAGG parameters match what is set in TrueNAS?

The “crappy switch” is extremely basic so really the only lagg options it has are if it is enabled or disabled and which ports to bond, but as far as I can tell everything is kosher between truenas and the switch as lan, wan, dchp (from the upstream router, switch dhcp server is disabled), etc all work perfectly fine, and from the switch it’s just a single gbe line to the router.
it’s only once trying to add the bond into a bridge for vm usage that I start having this issue. Everything still works too, I can still access the webui and truenas can still go online, but it just keeps spamming the console like I said.

The error message

Is pretty clearly saying the problem is with the other end of the LAGG and the SOURCE address of the packet. Have you tried using tcpdump (and Wireshark to analyze the output from tcpdump) to look at the traffic and especially the packets with the incorrect source address? That may give you a clue to the source of the problem.

I haven’t, I’ll have to do that when I get home. Or maybe I’ll just say screw it and run All of the connections individually, or bridge them all or something since I’m mostly just doing this for funsies but it’s not very funsie when everything just wants to be difficult.

i screwed around with it for a bit to no avail, so i went ahead and just did a reinstall which seems to have completely fixed all of my problems (knock on wood).