@charles_moody said in Trunk/LAGG problem / pfSense UniFi 24-250W PoE Switch and VLANs: Can anyone tell me how to get the switch to adopt So this is crux of your issue? That has nothing to do with pfsense.. Your controller and switch need to be on the same L2 network for adoption... Or you need to use L3 adoption.. This has everything to do with unifi, and not related to pfsense at all. https://help.ui.com/hc/en-us/articles/204909754-UniFi-Device-Adoption-Methods-for-Remote-UniFi-Controllers behind that about 10 smart-managed Netgear switches This seems nuts - are they all in closets somewhere.. How big is this house? If you were running cable - why would all your cables not just home run back to your core switching area? Curious where exactly all these switches are? want LAN just for troubleshooting and because it’s often stated that LAN will strip of the VLAN tags from the traffic Huh? You can run vlans on lan just like any other interface.. So not sure what your thinking with this statement... Sure you can use lan interface as your management interface.. But it can run vlans on it as well if you want.

I figured it out, I forgot some settings elsewhere

@Asamat: Your 'this Bug' URL is this thread here. -Rico

OK then the MAC address should be spoofed. The MAC address on the LAGG should also be the spoofed MAC. That is exactly what would be expected.

The copy jobs will be between nas to vsphere and external. Probably it will be smb3, i did not decide yet. After removing the whole lagg config on pfsense and switch it works! I can work with that but i'm still interested why it did not work with lag...