Forums/
Gateways
a week ago
@Paul_Higgs I will give that a try over the weekend however, as previously noted, I believe the problem is more with the TP-Link switches or router than the AP as a) a third party AP connected to the...
0HELPFULS
Forums/
Gateways
a week ago
@D-C I did not provision the 201 VLAN in any of the Omada devices. I guess next step will be to define VLAN 201 in Omada but only allow it in the switch that pfSense connects to then try also with...
0HELPFULS
Forums/
Gateways
a week ago
@Paul_Higgs Just to determine if this is a TP-Link/Omada issue of a pfSense/DHCP server issue, I added a non-TPLink VLAN aware switch between the TPLink switch and pfSense and an non-TPLink VLAN...
0HELPFULS
Forums/
Gateways
2025-12-12 10:14:10
@GRL I agree that this is very strange. I decomissioned the VLANS and SSIDs and built up completely new ones with different VLAN tags, SSIDs and IP addresses (in the DHCP server - there is no IP...
0HELPFULS
Forums/
Gateways
2025-12-12 06:21:07
@D-C the VLAN configurations of port 8 and port 6 are the same, so there was no change when moving the AP to port 6. I tried adding another AP with just those two VLANS to the same switch that has...
0HELPFULS
Forums/
Gateways
2025-12-11 10:29:41
@GRL I don't have DHCP relay configured. The Omada domain doesn't even have an IP address for VLANS 2 or 3 since it should only operate in the switching domain. I tried both with and without "Legal...
0HELPFULS
