@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.
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.
So looking at the new 5.11.10 release, looks like they have added ipv6?
from 5.11.5 in the release notes?
Add subnet for IPv6 networks in Networks Table.
I am currently running 5.10.21 which is not viable direct upgrade.. So can not test for sure until I get on 5.11.10, but you might want to try 5.11.10 if you want ipv6 with guest policy enable. But not captive portal.
Everything depends on your setup. Would need more details. Post a network map. Are your VLANs terminated on PFsense or your switch?
Post your server1.conf
What are the IP's in the VLAN you're trying to access?
What do the rules look like on your LAN and OpenVPN tab?
@jafr said in DHCP failing when moving between AP's:
Quick look shows that that switch can do dhcp snooping since I see in the manual dhcp snooping events for snmp.. So you need to look at the configuration of that switch or the port your AP is connected to.
If pfsense does not see the discover for dhcp then no it would never offer an IP..