I have come across a problem with DHCP on my Omada system, when the DHCP Server Service is provided by External Equipment. A diagram of the scenario is shown here

The Omada system handles the DHCP duties for the default subnet (VLAN 1), while a seperate DHCP server (from pfSense here but other Linux variants have also been tested) provides the IP address pools for VLANS 2 and 3. Each VLAN is configured with Legal DHCP Server address set to the eth0.2 or eth0.3 of the DHCP Server

If the computer connect to ports 3, 4 or 5 of the switch, it gets an IP address.

If the computer connects to port 6 and sets the VLAN tag to 2 or 3, it gets an IP address for the corresponding subnet.

If the computer connects to either SSID2 or SSID3 on the access point, no IP address is provided. Some further analysis is provided.

1. With SSID connection, using the packet tracing function on the EAP, we see the DHCPDISCOVER being received from the computer, but no DHCPOFFER - somewhere the offer is lost. 

EAP Wireless side

EAP Wired side

2. When connected to the the Tagged Ethernet switch port we see all the right things (VLANID 1010)

Does anyone know why DHCP over WiFi is failing when the DHCP Server is on a VLAN, but DHCP over Ethernet to the same DHCP Server is OK??